AutoRABIT ARM (Automated Release Management)

I use AutoRABIT Automated Release Management (ARM) mainly for RBC; as an nCino developer, I use it for RBC migration, deploying RBC from one sandbox to another sandbox, and we also handle prod deployments through AutoRABIT Automated Release Management (ARM). We also use the deployment part of it for metadata deployments and for committing our changes to Git branch; I use mainly these three parts.

We don't use a complete CI/CD pipeline with AutoRABIT Automated Release Management (ARM), but we have integrated it with Bitbucket and GitHub; we use the branching strategy without using complete YAML files and Jenkins.

On a scale of 1 to 10, I would rate AutoRABIT Automated Release Management (ARM) as an eight or nine.

I appreciate the part of AutoRABIT Automated Release Management (ARM) where I don't have to do different commits on Git; if I'm deploying anything from one org to another org, I can just deploy it to a branch as well, so I value that feature, as we don't have to do any extra deployments for that.

Because of AutoRABIT Automated Release Management (ARM), we don't have to do anything extra for audit purposes; we have a few audit requirements where they want to see everything deployed in one sprint, and since we set it as yes, which deploys to branch, it takes care of that whole part, and we don't have to do anything extra for that, which was beneficial for us.

AutoRABIT Automated Release Management (ARM) helps with real-time analytics; there are a few things such as profile comparison and org comparison that help us a lot, particularly if we have any permission issues, so those things are very useful to us.

Everything is in one place with AutoRABIT Automated Release Management (ARM), which we love; we don't have to use Inspector for data migration, and it's not that we have to use multiple tools; it's everything in one tool, which is our most used, go-to solution. For Git and Bitbucket, we don't even have to go to those orgs specifically; we can set it up through AutoRABIT Automated Release Management (ARM) and don't have to open it at all, and one license covers everything, which I appreciate. AutoRABIT Automated Release Management (ARM) also has data management features, so I value those as well; if we have any major data manipulations, we can do data uploads and other things through AutoRABIT Automated Release Management (ARM), and we don't have to do anything extra.

I am using the automated backup feature of AutoRABIT Automated Release Management (ARM) as well, and we are using it within one sandbox where we are taking backups.

Merging scenarios in AutoRABIT Automated Release Management (ARM) could be better; also, a few things which could improve include nCino RBC configuration, as sometimes if we have any extra lookup fields which are not configured by nCino, AutoRABIT Automated Release Management (ARM) sometimes misses those lookups to create the records or fetch those objects from our previous org to the next org, so I would feel more comfortable for RBC if AutoRABIT Automated Release Management (ARM) takes care of that too.

I haven't seen anything enhanced in AutoRABIT Automated Release Management (ARM) such as the ability to take a backup of RBC migrations as well, so how it works for metadata, deploying it from one org to another and deploying the same thing to the branch, I would like to see if we can do the same with RBCs also.

I have been using AutoRABIT Automated Release Management (ARM) for the last five years, for deployments and all other purposes.

We had a few issues with AutoRABIT Automated Release Management (ARM) where it started taking too much time to deploy things, but we found out they had some server issues at that particular time; AutoRABIT informed us to wait a while, and after restarting the whole system, it started working again, and other than that, we don't face many major downtime issues.

AutoRABIT Automated Release Management (ARM) is scalable, and we can scale it however we want to.

The initial setup of AutoRABIT Automated Release Management (ARM) was easy and much easier than expected; even when we faced some issues, we had an AutoRABIT support person who was there in the call and showed us if we were missing anything, so he was there to help us out.

I've used different products such as the normal Jenkins pipeline and data workbench; for data updates, we used Salesforce Inspector, so we used many tools, but once we got introduced to AutoRABIT Automated Release Management (ARM), we stuck to that.

The initial setup of AutoRABIT Automated Release Management (ARM) was easy and much easier than expected; even when we faced some issues, we had an AutoRABIT support person who was there in the call and showed us if we were missing anything, so he was there to help us out.

On a scale of 1 to 10, I would rate AutoRABIT tech support as an eight, or even a nine.

We did evaluate another solution, Copado, but it was not giving us anything specific to nCino; when we adopted AutoRABIT Automated Release Management (ARM), it provided us with a special, specific package for nCino, and it was a good demo as well, with the assurance that the whole RBC's part would be covered, so we didn't have to worry about that.

I'm quite confident with AutoRABIT Automated Release Management (ARM) regarding data integrity; I don't feel there's any mishap with it, and I feel comfortable working with AutoRABIT Automated Release Management (ARM).

I would say that if organizations are using nCino and developing anything on nCino, then they should go for AutoRABIT Automated Release Management (ARM) without any second thoughts; that's my recommendation, as it takes care of everything, and I feel more comfortable using AutoRABIT Automated Release Management (ARM) compared to any other tool when developing anything related to nCino.

I haven't used data masking yet. I would rate this review an overall 8 out of 10.

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.

My main use case for AutoRABIT Automated Release Management (ARM) is deploying or merging changes on a day-to-day basis with the help of this tool.

A specific example of a deployment or merge I have done recently using AutoRABIT Automated Release Management (ARM) involves all developers working on different environments. Whenever we work on a functionality, we compare the changes we have made to a component, and with the help of AutoRABIT Automated Release Management (ARM), we deploy the changes to the higher orgs. For example, we created a portal recently where the UI was worked on by me and there were other changes done by other developers.

I have been automating from one of the orgs that directly deploy the changes to the higher org once the deployment is successfully completed in one of the lower orgs.

The best features AutoRABIT Automated Release Management (ARM) offers include my work on two different kinds of packages, one being Salesforce components and the other being OmniStudio components. We separated both deployments so that the deployment should not be blocked if there are issues and both can be taken care of separately.

AutoRABIT Automated Release Management (ARM) has positively impacted my organization because earlier, we used to compare changes via Notepad and then merge our changes manually. With the help of AutoRABIT Automated Release Management (ARM), these tasks are now automated.

AutoRABIT Automated Release Management (ARM) could be improved by offering the feature where I can deploy both OmniStudio and Salesforce components together.

I would also mention that the UI should be more user-friendly. Rather than displaying all code, it should have a better user interface.

I have been using AutoRABIT Automated Release Management (ARM) as a deployment tool for three-plus years.

We have previously used Copado before switching to AutoRABIT Automated Release Management (ARM).

I would rate AutoRABIT Automated Release Management (ARM) an eight out of ten.

I chose an eight because, as I mentioned, the UI needs to be improved, and it should allow me to deploy multiple different types of components at a time.

Regarding AutoRABIT Automated Release Management (ARM)'s AI capabilities, I have not encountered any issues with respect to security, so I believe it is good. I think the AI capabilities are still in the learning phase, and I still see challenges that can be improved.

My overall rating for AutoRABIT Automated Release Management (ARM) is eight out of ten.

My main use case for AutoRABIT Automated Release Management (ARM) is that it makes the work easier and helps to handle a large amount of data. During our refresh time for data merging, we used AutoRABIT Automated Release Management (ARM) data tool for the data migration, which also helped me significantly.

A quick specific example of how I use AutoRABIT Automated Release Management (ARM) for data migration involves setting the branches and the pipelines and ensuring that the test class coverage is covered as per the required standards from the Salesforce side for each class and trigger. Apart from this, I can say the data migration part with the org connection being seamless from one end to another. The initial step of AutoRABIT Automated Release Management (ARM) connecting with Salesforce through Git makes it much easier. Connecting Git, creating a pipeline, and authorizing them, and on the other end, authorizing an org helps it to be seamless.

The best features AutoRABIT Automated Release Management (ARM) offers are the automation validation, automation testing, approval, and the deployment process. If there is anything, we can roll back. The easy pipelines, sandbox management, the integrations, the version controls, and the feature updates are the ones I appreciate most.

Out of all those features, I can say the deployment automation and the rollback have made the biggest difference for my team because they reduce the failures and production risk. Second, the version control integration tracks every metadata change and supports team collaboration, where the versions have been updated recently. These are the things that I highly use. Additionally, Data Loader Pro supports data migrations across all the environments, which is also very helpful on our side when doing data migration activities.

For the release management, I could say that AutoRABIT Automated Release Management (ARM) has positively impacted my organization.

I would say syncing up with Jira for AutoRABIT Automated Release Management (ARM) could be improved. We have the stories and are picking the PR links directly from Jira. We tried this in our project, but it was not seamless connectivity, so we were not able to implement it fully. It would be helpful to have some customization after the PR is taken from Jira and deployed through AutoRABIT Automated Release Management (ARM). For example, automatically updating the status back to Jira would be beneficial. We need some customized statuses, which would be helpful for us.

I can say there are some other opportunities where AutoRABIT Automated Release Management (ARM) could improve. I need to explore where we can make further use of it. Due to that, I have given that score.

I have been working in the current field for three years.

AutoRABIT Automated Release Management (ARM) is stable.

AutoRABIT Automated Release Management (ARM) is very scalable. There are many options available, though I need to explore them further.

The customer support for AutoRABIT Automated Release Management (ARM) is good. They are patient and able to see what the requirement is from our side based on the tickets, and they help us solve it.

I have seen a return on investment with AutoRABIT Automated Release Management (ARM), and it is time-saving.

I have been using AutoRABIT Automated Release Management (ARM) for three years.

I am not much familiar with the AI capabilities of AutoRABIT Automated Release Management (ARM) regarding its governance and security.

I am not much familiar with the AI capabilities of AutoRABIT Automated Release Management (ARM) regarding its accuracy and reliability of output.

I can say some features, such as pipelines, are seamless compared to other pipelines such as Jenkins, where those are manual things that need to be done. We need to set the validation criteria.

I give this review a rating of nine.

The main use case for AutoRABIT Automated Release Management (ARM) when I was using it was for release management, as we were having different sandboxes, so the code is released from one org to another, all the way to production.

AutoRABIT Automated Release Management (ARM) was especially helpful because production used to have the code for two different releases, so using AutoRABIT Automated Release Management (ARM), we could have multiple monthly branches, and any codes, hotfixes, or bug fixes could be handled smoothly.

AutoRABIT Automated Release Management (ARM) made my day-to-day work easier with around 30 developers, as it helped in release management very effectively because there would be some automated processes as well as different code bases, helping in managing conflicts and release time.

AutoRABIT Automated Release Management (ARM) has positively impacted my organization by helping in handling release timelines as well as ensuring that hotfixes are handled properly. While not dramatic, it represents the bare minimum in improvements, and the results are excellent.

The best features that AutoRABIT Automated Release Management (ARM) offers include conflict resolution, multiple branches resolution, determining which code should go in which branch, as well as the capability to have org data deployed using AutoRABIT Automated Release Management (ARM), which makes it an additional tool that helps in the deployment of data as well as metadata.

The org data deployment feature was helpful for my team in Salesforce, for example, as we used to deploy products as well as rules, such as matrix rules. AutoRABIT Automated Release Management (ARM) was a very good help in this regard, which allowed developers to deploy directly without manual steps and handle it without going into a call with DevOps, as long as they have the access.

To improve AutoRABIT Automated Release Management (ARM), I suggest adding components such as managed packages and velocity components, which could also be deployed, and it could connect with multiple orgs using SFDX metadata instead of the old metadata, which would be helpful for Salesforce development.

I have been using AutoRABIT Automated Release Management (ARM) for around three years.

I have used AutoRABIT Automated Release Management (ARM) for three years, and we are currently using a different tool.

AutoRABIT Automated Release Management (ARM) helped with release timelines and hotfixes by providing smart conflict management and information about expected issues, such as if the code base is not available in the higher org, which informs the developer before submitting instead of finding the issue afterwards. The automation part also helped in running automated test cases, so it was quite helpful.

Regarding AutoRABIT Automated Release Management (ARM)'s AI capabilities, I find that its governance and security are decent, and while AI governance security is improving, the company states that it is secure and client data is secure, so I have not thought about it in depth.

Concerning AutoRABIT Automated Release Management (ARM)'s AI capabilities, I find its accuracy and reliability of output to be decent as it could improve more. It currently provides all the help tools, and if it does not have the information, it refers to the help documents, which is quite good.

For others looking into using AutoRABIT Automated Release Management (ARM), I say it is a great tool for automation. It could improve on some parts, but if you do not mind having robotic automation, AutoRABIT Automated Release Management (ARM) is the place to go, as it performs quite well in what it does. I have rated this review as a seven out of ten.