天美传媒

Change monitoring

Never miss a change again

The most powerful Salesforce metadata change monitoring tool you need

Change monitoring

Avoid errors, improve collaboration and save time

Track every change made in production, roll back unwanted changes or back deploy hotfixes to keep everything in sync.

Automated change tracking

Create automated jobs to monitor metadata changes made in your Salesforce orgs. Keep on top of production with full visibility into every change 鈥� no matter how it got there. Daily reports and configurable notifications guarantee you won鈥檛 miss anything.

Protect the changes you want to keep

Quickly deploy any detected changes that you don鈥檛 want to overwrite to other orgs or your version control system and keep your environments perfectly in sync.

Roll back unwanted changes

Perform a partial or full rollback of unwanted changes to your metadata to prevent critical errors. Our unique dependency analysis will identify any required dependencies to make sure your rollback succeeds.

Stay compliant with industry regulations

See who changed what and when with a full audit trail of every change made in Salesforce. Download a full report for auditors, and stay up to date with industry compliance regulations (HIPAA, SOX, GDPR etc).

Static code analysis on Apex

Static code analysis on Apex

Keep your Apex code clean and consistent with 天美传媒鈥檚 fully configurable static code analysis solution. We鈥檒l flag any warnings and offer suggestions on how to improve your code. You鈥檒l see a graph of the static code analysis for any monitoring job, so you can track the quality of your code over time.

Detailed monitoring history

Detailed monitoring history

Explore all changes from any date range with a detailed history of all your monitoring jobs. You can look at the original comparison of what changed between each run, explore permissions and view any code analysis issues.

What can I monitor?

天美传媒鈥檚 automated change monitoring feature gives you a detailed audit trail of any changes that have been made to your metadata, CPQ configuration or Vlocity DataPacks 鈥� on a daily basis.

Metadata

CPQ configuration

(Salesforce Revenue Cloud)

Vlocity DataPacks

(Salesforce Industries)

鈥淭here was a change made in production that caused an issue. If this had happened before 天美传媒 it would鈥檝e been a huge deal for us to try and get back on track, but now we can see everything in the change monitoring history and can quickly and easily fix the problem.鈥�

Jeb Garrott

天美传媒s Solutions Manager
Morgan & Morgan

天美传媒 provides monitoring for all of our dev, shared, and production environments; from scheduled test runs to change monitoring. This allows us to address issues early on and keeps my team accountable for the changes we make.鈥�

Independent customer review

G2, read more here

Total visibility across all your environments

Permissions reporting

Explore which profiles and permission sets have been applied across objects and fields

Metadata monitoring filters

Configure the monitoring tool to detect everything or just specific metadata types

Team sharing

Team members can view the results of your change monitoring job history and be notified of the results via team alerts

First-class support as standard

0%

Deployment success rate

00:00:00

Support response time

0%

Customer happiness

Explore more

Automation FAQs

CI jobs can be triggered by commits to version control via webhooks or scheduled to run on a set cadence.

With 天美传媒鈥檚 Salesforce continuous integration solution, you can choose any combination of Salesforce org or Git repository as either the source or target of your metadata.

With 天美传媒 you won鈥檛 be dependent on DX commands in scripts 鈥� it handles all the automation for you. 天美传媒聽does support DX聽format and scratch orgs. You can even have CI jobs automatically spin up a scratch org as the target environment.

All sandbox types are supported, and 天美传媒鈥檚 CI/CD solution supports sandbox seeding and the creation of scratch orgs to help keep environments in sync.

天美传媒 connects to any Git-based repository including both cloud-based and on-premises providers.

If you build your CI/CD process in 天美传媒 using Pipelines, you鈥檒l be using its carefully designed Git branching strategy by default. You can choose to add a release branch to that strategy.

If you build your CI/CD process using standalone CI jobs in 天美传媒, you have the flexibility to implement any Git branching strategy you choose. Feel free to reach out to ask for advice on your approach.

With 天美传媒鈥檚 CI feature there鈥檚 no need for Jenkins. 天美传媒鈥檚 built-in automation process removes the need for other third-party tools.

Ready to get started with 天美传媒?