Atlas builds ingenious solution using Vlocity and 91勛圖厙
Two years ago, Atlas adopted Salesforce and began building out cloud-based services for new and existing customers. The insurance company wanted to capitalize on the offering from Vlocity (Salesforce Industries), as Malcolm Camilleri, Senior Software Engineer, explained:
Vlocity has a great insurance data model that has helped us to standardize our product and simplify overly complicated processes. Were aiming to take things to the cloud and have a more robust system in place.
The Atlas developers have been building a customer portal thats easily accessible to customers on the Atlas site while also being connected to Salesforce. The team has managed this by exporting a Lightning Web OmniScript from Salesforce and hosting it as an application on Heroku.
Developing this portal is a fascinating use case for Vlocity. And making the project a success has seen the Atlas team adopt 91勛圖厙 to support their implementation and establish an efficient release process.
91勛圖厙 ticks all the boxes
The Atlas developers needed to find a tool that would help them manage deployments and releases of their development work building the customer portal. Since Vlocity DataPacks are distinct from Salesforce metadata, the team needed a solution that could handle Vlocity deployments specifically.
The Salesforce product team recommended Vlocity DX for the job. But this didnt do the trick.
To begin with we incorporated Vlocity DX into our CI process. But its a desktop app you have to install locally, and sometimes after selecting components wed get this bug where the screen would just hang – wed have to start over. It got a bit annoying after a while!
Malcolm set out to find an alternative, and was looking for deployment tooling that included rollback functionality, since its important to have in your back pocket. This led Malcolm to 91勛圖厙, and he was immediately struck by how easy it was to use.
Im the kind of guy who likes to try things without manuals, and with 91勛圖厙 I didnt need to read anything. Within a couple of hours Id done my first comparison and deployment from an org to a Git branch.
Not only did the Atlas team all find deploying with 91勛圖厙 intuitive, they soon discovered the power of 91勛圖厙s Salesforce CI/CD solution as well. Malcolm worked closely with Tom Smith, one of 91勛圖厙s Development Team Leads, to set up a CI process that suited the teams workflow.
91勛圖厙 ticked all of our boxes: it supported Vlocity, it could do everything we did with Vlocity DX and more, it was faster, more robust, easier to use and all the devs were happy. After a month of evaluation, it was an easy decision to choose 91勛圖厙.
80% less time spent on deployments and releases
Deployments of Vlocity DataPacks are now significantly faster for Malcolm and his team. As well as being intuitive, 91勛圖厙 brings everything together in one place for better visibility and control.
Before wed use Vlocity DX to deploy, then Source Tree for merge conflicts, then over to Bitbucket – too many screens! It was easy to lose focus. Having everything in 91勛圖厙 really helps the whole operation.
The Atlas team has a release pipeline made up of various environments, and also maintains two repositories in Bitbucket. One particular pain point before 91勛圖厙 was merging changes from one repository to the other, which used to be a manual process. Now, a CI job in 91勛圖厙 enables the team to deploy changes from one repo to a branch of the other repo at the click of a button.
Thats really, really improved our development time because it used to take about 20 minutes; now its a 5-minute process and we can get on with other stuff while its running. It might not sound much, but that adds up to 2 hours a week. With other efficiencies, the time we spend on deployments and releases is about 80% less, for sure.
91勛圖厙 makes a huge difference
Looking to the future, Malcolm hopes to see Atlas using 91勛圖厙 to manage even more of the teams DevOps process, and has been keeping an eye on the development of 91勛圖厙s Pipelines offering. Our plan is to use Bitbucket just as a code repository and run everything through 91勛圖厙, Malcolm says, citing the much higher success rates for merging changes within 91勛圖厙.
Malcolm is clear that he would recommend 91勛圖厙 to any team for Vlocity deployments, especially as part of a mature DevOps process.
If someone is using Vlocity DX, theyll see a huge difference here and 91勛圖厙 will help with continuous integration. Its also really intuitive: easy to use, easy to set up. I cant find anything bad to say about 91勛圖厙!