The main use case for AutoRABIT Automated Release Management (ARM) is to deploy components across various sandboxes from developer sandbox to QA sandbox, then UAT, and then to production. This allows us to automate a lot of the deployment process in Salesforce. We can also specify all of the other artifacts and, for test classes, we can increase the test case scenario beyond 75% for our own purposes.
Many customizations can be done using AutoRABIT Automated Release Management (ARM) for specific use cases of the company.
The best features that AutoRABIT Automated Release Management (ARM) offers are resolving merge conflicts and the configuration capabilities. The UI makes it very easy to see the changes and get those resolved. There is a lot of detailing about the configuration we can do in Salesforce, which is very valuable. Integrating with Git or Bitbucket is something really useful for version control as well.
Regarding the merge conflict resolution feature of AutoRABIT Automated Release Management (ARM), it has positively impacted my team's workflow and productivity by making it easier for even junior developers to see what incoming changes are there. Previously, some of the junior developers were hesitant about how to handle merge conflicts, but once they started using AutoRABIT Automated Release Management (ARM)'s merge conflict resolution, it became easier to see what incoming changes are present. Even if they are not sure how to proceed, they can perform the manual merge as well, which is very handy.
AutoRABIT Automated Release Management (ARM) has impacted my organization positively by fostering trust and reliability. It is able to perform a lot of commits and changes at scale. Even if we have many commits happening and many changes going through, it is able to perform those at scale, which is a good thing.
AutoRABIT Automated Release Management (ARM) can be improved in terms of the UI. There are some competitors, such as Copado, which offer a Salesforce native UI. Something similar to a Salesforce native interface so that people do not have to learn how to navigate the UI again would be beneficial.
I started using AutoRABIT Automated Release Management (ARM) in 2021.
Regarding AutoRABIT Automated Release Management (ARM)'s accuracy, I would rate it very high, about nine out of ten. The reliability is also good. Sometimes we have issues with AutoRABIT Automated Release Management (ARM)'s new releases where some things do not work, but those issues get fixed once someone addresses them. Overall, everything is good.
The specific outcomes in terms of numbers since using AutoRABIT Automated Release Management (ARM) include increasing people's productivity because they are not concerned about overwriting someone's changes. Everything is transparent. In terms of productivity, it initially takes some time to understand the process for a couple of weeks, but once the process is understood, it saves approximately 30 minutes per story compared to traditional deployment methods. If there are many developers that are added to AutoRABIT Automated Release Management (ARM), scalability becomes easier.
Governance and security with AutoRABIT Automated Release Management (ARM) is pretty robust. It is able to handle all of the Salesforce security components that are part of code or metadata. We can configure all of those things using AutoRABIT Automated Release Management (ARM), which we can specify based on the company's needs. It is pretty robust. I would rate this review an 8 out of 10.
