AutoRABIT plus Perforce Software
August 7, 2017

A Powerful “Early Warning” System for Salesforce Developers with AutoRABIT and Perforce

Application Lifecycle Management
Version Control

by Niranjan Gattupalli – Sr. Director of Customer Success

Many industries use Salesforce for customer relationship management. It can be customized to a company’s individual requirements. And it gives a 360-degree view of customers.

There's an increase in demand for Salesforce. And that's led to an increase in need for rapid delivery of software releases.

So, developers need to create and deploy applications faster. And those applications need to be high quality to meet business expectations.

The Role of Salesforce Release Management

AutoRABIT is a release management solution for Salesforce applications.

It includes:

Release Management and Version Control

Here are the major challenges of Salesforce teams while trying to achieve CI with version control:

  • Lack of knowledge about using version control along with best practices for the teams coming from a “point-and-click” environment like Salesforce.
  • Delayed releases due to deployment failures caused by missing dependencies as well as code coverage issues.
  • Salesforce complex metadata structure that causes issues with profiles and custom labels.

Using AutoRABIT and Perforce

Perforce offers version control and ALM tools that work alongside AutoRABIT. 

So, you get what you really need.

Integrated ALM

Connect items across your project lifecycle.

Fast and Scalable, Everywhere

Support thousands of global users and millions of daily transactions.

Single Source of Truth

Keep contributions from all teams in one spot.

Security and Compliance

Protect your IP. And comply with industry standards. 

AutoRABIT Check-in Editor for Helix Core

AutoRABIT has a powerful check-in editor which is unique for Salesforce developers to check in code/configurations to Helix Core repos effortlessly.

The key features of check-in editor include:

Ability to Understand Salesforce Metadata

The editor understands the Salesforce metadata structure. It can fetch the changes done by a user (up to the child metadata level) along with dependencies. And the developer can push the changes to Helix Core.

For example, a user modifies a custom field. And AutoRABIT allows the user to only check in the custom field irrespective of other changes done in the custom object in the Sandbox.

Smart Profile Check-Ins

60-70 percent of Salesforce teams who use version control and CI don't include profiles in version control and CI deployments.

Check in code a smarter way. And avoid pushing unwanted permissions modified in the Org that cause inconsistencies when the profiles are deployed to other environments.

AutoRABIT checks in a profile along with other metadata. This ensures that only the permissions of respective metadata are checked in.

Tag Check-Ins to Helix ALM Work Items

The developer can check in changes to Helix Core. And they can associate the check-ins to Helix ALM work items. This gives them a higher degree of traceability and collaboration for the work items.

AutoRABIT Check-In Gate for Helix Core

Make sure developers only check in high-quality code.

AutoRABIT and Helix Core make offer two features that maintain code quality:

Validation Reports

With AutoRABIT check-in gate, Salesforce developers can verify if:

  • The code is deployable.
  • The code has not introduced any new coding violations.
  • The code meets the code-coverage benchmarks.

And they can do all of this before checking in code.

Approval Process

The validation reports send notifications to reviewers. They approve or reject the check-in. And the developer can push the changes to version control.

“No Deployment Strategy” for Helix ALM Work Items

AutoRABIT has powerful deployment capabilities. You can deploy metadata changes from version control repos. Or you can deploy changes from a Salesforce Sandbox to a destination Salesforce environment.

So, you can deploy changes from Helix Core repos into Salesforce based on Helix ALM work item status.

For example, an AutoRABIT CI job can continuously deploy all the Helix ALM work items that are “ready for QA” into QA environment.

It is effectively a “No Deployment for Release Managers”. AutoRABIT can track the user story/work item status. And it can deploy the changes automatically into Salesforce environments based on the workflows defined in Helix ALM.

The check-in editor reduces the complexity of code check-ins. And it offers continuous validation of check-ins.

So, AutoRABIT and Helix product development ensure code quality and reduce deployment failures. And that accelerates developer productivity and release velocity.

A Salesforce Early Warning System

AutoRABIT check-in gate is a Salesforce early warning system. It enables Salesforce developers to check in quality code that meets enterprise coding standards.

Code changes deploy from Helix Core, either from a stream or from a Helix ALM work item. So, Salesforce release management teams can experience continuous delivery of their applications.

Explore Helix Core  Explore Helix ALM