Is your production refresh to Dev, Integration and other release environments happened a few months ago and there have been changes both in production [ in the form of some urgent fixes , or some configuration changes ] as well as in your Dev environment [ as part of working on your new features ] – then we all know the problem we are talking about.
For enterprise Salesforce Orgs with longer release and refresh cycles as well as environments where Production Org can be updated from multiple disparate sources – the biggest challenge teams face today is with synchronizing the Salesforce environments .
For teams to operate at a higher level of maturity by achieving continuous integration and Continuous Delivery for Salesforce Applications – synchronizing Salesforce Orgs is the one of the foremost steps for CI/ CD enablement .
At AutoRABIT we continuously research , talk to clients and innovate features that are sensible and empower Salesforce development teams to achieve higher release velocity . Synchronize Salesforce Orgs is one such feature arising out of client interactions and customer pain points and is currently given as a “Beta” Release to select customers. The feature is slated to be generally available on AutoRABIT 3.4.1 on 15th of May .
Here, you can see the list of metadata members which are in Source Sandbox alone , which are in destination Sandbox alone and metadata members available in both.
There is also a provision to delete a particular metadata item from the Source Salesforce Org / add the same to a destination Salesforce Org there by achieving the synchronization of the Sandboxes.
With this feature AutoRABIT can enable CI as well as drive the CI adoption and better release management for Salesforce teams empowering them to reach the goal of higher release velocity powered by automation .