Release Notes

We received reports of users unable to edit their credentials in the Credential Manager if the password contains a “_” or “.”. This has now been addressed.

Created/Edited a new role and it wasn’t saving properly? If so, this is fixed, and all roles will save appropriately.

7/6/2018

New Features

Added a new value called “Replace Single” for Configuration For recordTypes picklistValues option under My Account in the Admin module. Further details can be found on our support site.

Bug Fixes

When selecting the Choose file from source option in our Merge editor, conflicts were still coming through for the user to select. This has now been addressed and conflicts will automatically be resolved from the source when this option is selected.

Made some architectural changes for the reports functionality to read from our database rather than XML.

6/27/2018

Bug Fixes

Someone found a magic trick within our deployments feature where opening and closing the difference report multiple times duplicated the report on-screen. This has now been fixed.

Release labels were not showing up under CI jobs for automated merges. We have addressed this, and it should now be visible.

You can now use the underscore (_) character in deployments without it resulting in an error

6/22/2018

Bug Fixes

We have fixed an error when selecting enabling masking rules as part of your Data Loader process.

Deployments is now working as expected and only showing you the items selected rather than other random components.

We received reports of a mysterious option in the Admin module called Mail server Settings. We have since removed this option as its not for our SaaS customers!

6/15/2018

Bug Fixes

Masking rules were automatically being selected when running a dataloader process and caused errors. Now you can migrate your data error free with or without masking rules.

Can’t find reports or dashboards when deploying through revisions? We have fixed this issue and now these metadata types will be retrieved from source control.

We reminded AutoRABIT where the SSH private key is stored so the repository can be authenticated.

6/4/2018

Bug Fixes

Updated framework for the PermissionSet metadata type to not perform a delta comparison as this is not needed from Salesforce API 40.0 and up.

Data Masking – Data administrators can now mask sensitive data records before it is loaded onto a destination. There are no restrictions on the number of fields you can invoke masking on. There will be three masking styles available:

Prefix – Enter a value which will be added as a prefix to the existing data value

Suffix – Enter a value which will be added as a suffix to the existing data value

Replace – Enter a value which will completely replace the existing data value

CSV as Source – This new feature will remove the restriction of using a Salesforce sandbox as Source. Users will be able to input a CSV file with hierarchy relations. AutoRABIT will read the parent-child relationships and auto-map your fields. The other good stuff in Dataloader Pro follows this new feature [Disable validation rules, workflow rules, inserting null values, etc.]

5.Credential Manager

Multiple systems, one access point

An encrypted “digital locker” feature that enables a user to store Authentication information for multiple endpoints. Users can define, if a “credential” is global or private, depending on which other users will be able to use the access. These credentials are used by AutoRABIT to access your ALM, your Source Control, your PMD tools, etc.; the tools that you access every day quickly and efficiently.

6. Global Setting to Grant/Revoke permissions

The new way to manage permissions

An automated way to manage permissions across multiple metadata members in an agile way.

Let us suppose that in a sprint there are a few Profiles/Permission sets for which access must be granted and a few where access needs to be removed. Now, users can configure these Profile/Permission Sets in an umbrella such that each time a metadata member is committed via AutoRABIT, the respective Profile/Permission Set will be modified as per setting.

A new grid-based selection for the type of Salesforce ‘CI Job’ that you want to create.

An enhanced singular screen interface divided by sections to help you define a CI Job much more effective.

No more typing of email addresses! Yay! You can check and notify the list of AutoRABIT users on a success/ failure events.

Set your CI Job rotation policy.

9.Ability to Abort CI Jobs

Stop and Go at Will

With a robust CI platform, we realized that many a time, there would be a need to kill a CI job. The reasons could be many; Example – A user forgot to add a dependency but kicked off the automation, only to realize that he made a boo-boo. Now, instead of waiting for the entire automation cycles to be completed and losing expensive release minutes, he can terminate the previous process at will.

10. Compounded Commit Labels

Users can now create a Commit Label (think of it as a Change Set) in EZ-Commits

These Commit Labels are to be used to tag multiple commits to the same label. The label can be used as a definition of change/sprint/story based your requirement.

The same Commit Labels can be used to Merge across different branches OR promoted into different environments as needed.

11. Environment Provisioning

A robust pre/post deployment framework.

Ability to migrate Custom Settings data as a Post migration step as part of Continuous Integration (CI Jobs).

Ability to use and tag AutoRABIT’s pre-loaded pre/post deployment scripts to automate “unsupported metadata” as part of Continuous Integration (CI Jobs).

Ability to invoke your own custom scripts as part of CI Jobs.

12. Code Coverage Reporting

Be notified

Now, users who request code coverage reports will be notified via an email with the results of a Code Coverage run on a specific Salesforce Org.

No limit on the number of code coverage runs requested.

Improvements made after 4.1.1. until 4.2 General Availability release – A Snapshot

EZ-Commits

A configurable option for “non-admin” users to use Compare and Commit

The option to see Code Level Differences in Validate and Commit is defaulted to True.

Selected Additional Metadata can now be seen on the EZ-Commit screen with an option to deselect.

‘Fetch Changes’ will now show the Last Modified By user

Users now have an option to remove System Permission and IP login ranges while committing a Profile/ Permission set

Create a Validate and Commit request after a Compare and Commit (Code Comparison)

An enhanced option commit Field Level Security for standard fields

AutoRABIT Merge

Offline Merge v1.0 – Support for the user to download a conflicted file, resolve it locally and upload it back into the application

Continuous Integration

Performance and stability improvements

Auto-refresh CI logs for better visibility

Complete support to prepare and run metadata component level destructive changes from Source Control.

AutoRABIT is an end-to-end continuous delivery suite for Salesforce, AppExchange. If you are enjoying us, please leave us a review and a rating. If you have something to share, then email us at feedback@autorabit.com. We welcome your feedback.

We are pleased to announce AutoRABIT v.4.1 GA Release. Here is an update on the new features that will be made available over the weekend release scheduled for 3rd March, 2017:

Check-in gate and code reviews

The code check-ins can now be pre-validated and reviewed before check-in to Version Control.

TFS connectivity is extended to connect through TFS customer service account credentials.

AutoRABIT announces the 4.0.2 Release, which will help our customers to further leverage their efficiencies through automation.

The following is a broad overview of some of the forthcoming features of 4.0.2 Release.

Snapshot of 4.0.2 Release

Destructive changes in CI Jobs

Sequence your CI Jobs

Support for Release Label Merge

Improved E-mail Notification

Apex Test Selection in CI Jobs/ Sync SF Orgs/ Selective Deployments

Configuration option for Managed Package Baselines

Filter option of Data loader jobs that are “in-progress”

Job time stamps based on User Profile Time Zone.

AutoRABIT is committed to enhancing customer excellence with your every single experience with us. We always assure you of our best in innovation at every step of your journey with us. Stay with AutoRABIT, stay ahead of the competition.

It is AutoRABIT’s constant endeavor to help our customers minimize their manual work and achieve greater efficiency through automation. In line with this vision, AutoRABIT announces the 4.0 GA Release, which will help our customers to further leverage their efficiencies through automation. The following is a broad overview of some of the forthcoming features of 4.0 GA Release.

SNAPSHOT OF 4.0 GA RELEASE

Now, trigger AutoRABIT builds on your GIT or SVN commits

Merge editor for GIT

Profile Designer, Comparator and Deployer

Seamless integration with JIRA and IBM RTC

AutoRABIT usage reports

Deploy your entire release from Version Control in a single go

AppExchange app configuration automation

Deployment enhancements

AutoRABIT is committed to enhancing customer excellence with your every single experience with us. We always assure you of our best in innovation at every step of your journey with us. Stay with AutoRABIT, stay ahead of the competition.

We are delighted to announce the release of AutoRABIT 3.9.3. We are confident that our new features will help you achieve enhanced efficiency by freeing up your time spent on repetitive manual tasks. We continuously strive to take your customer excellence level to a whole new level with every single experience of yours with us. We always do our best at every step of your journey with us. We would be glad to hear from you about any new features that you would like us to introduce in the near future.

1. Have Better Control Over Version Control System

Now, view the entire Version Control commit history through EZ-Commits.

Compare metadata differences between Salesforce Org and Version Control repository and view the missing data in Version Control repository. Now, you can also delete the Version Control metadata to sync up the Version Control repository with the sandbox.

Get summary view of metadata members committed to Version Control System in EZ-Check-ins

2. Track Your Audit Trail in AutoRABIT

Now, view the entire history of changes (of past 6 months) made to a Salesforce Org in the Audit Trial Log.

3. AutoRABIT now supports Salesforce API 37.0 (Summer ‘16) release.

4. Deployment Support

Custom deployment now supports TFS Version Control System

5. Scheduled Builds Run Only on Modifications

Scheduled builds will now trigger only if modifications are found either in sandbox or Version Control System.

6. Straighten Your Circular References with Data Loader Pro
Now, simplify your complex circular references. With the option to minimize multiple references between same objects in Data Loader Pro, get sizeable data from production (after refresh) with just a single click.

Detailed Release Notes can found in the “Help” section of AutoRABIT. Please write tosupport@autorabit.com for more information or for a detailed discussion on the released features.

We are pleased to announce the AutoRABIT 3.9.2 release. We hope our new features will help you minimize your manual work and help you achieve greater efficiency by way of automation, in line with the vision of AutoRABIT. We assure you that, we are committed to enhancing customer excellence with your every single experience with AutoRABIT. Always you of our best in innovation at every step of your journey with AutoRABIT. We would be glad to hear back from you about any new features that you would like to be introduced by us.

Here is an update about the changes and new features that will be available to you from 23rd May, 2016

Push Salesforce Sandbox Metadata into Version Control System

Salesforce has governor limits (size 400 MB or 10,000 files) to retrieve metadata at a single request. For large enterprise Orgs, it may not be possible to retrieve and commit the entire Org exceeding governor limits to a version control system. AutoRABIT helps you overcome this challenge. You can now commit large orgs to a version control system with a single-click using AutoRABIT version control management.

Managing Your Version Control Credentials is Now Made Simple

Configure version control credentials in your user profile(My Profile)view and eliminae the need to re-enter them at multiple places in AutoRABIT.

Enter the version control credentials in your user profile console only once for a single branch under a repository and continue creating multiple branches. AutoRABIT auto-populates the credentials for all subsequent branches in the user profile.

EZ-Commits

Now,as an Admin, you can verify and commit changes made by all users into a version control system with a few clicks in EZ-Commits.

AutoRABIT EZcommits has a new dimension now. With AutoRABIT, there is an option to retrieve any specific metadata types that a user wants to commit by clicking “ Additional Metadata” button in EZ-Commits.

Now you can compare the metadata differences between your Salesforce Org and your version control system before committing the changes by clicking “Compare and Commit”. This allows a user to see what changes are being committed to the version control system.

Projects (CI Jobs)

An option to exclude metadata types that you don’t want to bundle as a part of your CI build. This would greatly reduce your build time and increase your deployment success rate.

AutoRABIT now offers an option to validate your deployments without actually having to deploy your changes into your Orgs. To do this, check the “Validate Only” check-box.

Have better deployment visibility and enhanced CI jobs with code coverage reports option. You can now configure your apex tests as a part of your CI job.

During profile deployments, you can either retain or remove login IP ranges and user permissions from your source Org by clicking “Profile Settings”.

Selective Deployment

You can directly deploy EZ-Commit labels into Salesforce.

Re-use your un-deployed labels. You can now just validate the deployment and deploy the changes later, whenever required.

Performance improvement in the Org comparison

With parallel deployments, you have no more queues for your deployments.

Enhanced profile and permission sets deployments.

Details about the new features can be found in the “Help” section of AutoRABIT.
Please write to support@autorabit.com for a detailed discussion on the released features.

Register your concerns or issues with AutoRABIT in the tool itself, which will be addressed always on priority.

3.Reusing the un-deployed labels

Once a label is initiated for deployment, you can now just validate the deployment and deploy the build later when ever required. The label created will be stored with AutoRABIT, ready to be deployed whenever required

4.Supportfor validation in the CI job

Apart from deploying builds, you can also validate the builds and look at the detailed reports that are generated. Based on the reports generated, the user can deploy a build, which helps the user focus on the deployment failures and provide fixes accordingly. The user can also re-use this build in custom deployment.

5.Support for Picklists, CustomObjectTranslation in EZ-Commits

When a user modifies pick list values, the last modified date of a Picklist is not updated by Salesforce, so AutoRABIT provides an option to include pick lists in EZ- Commits.

6.Support for AWS Code commit GIT

AutoRABIT provides full support for GIT repositories inside AWS as part of its CodeCommit Hosting. (including Get, Creating branches, Commit list, Latest revisions).

Data Loader Pro now supports :

Circular references

Owner id transfer

User lookup transfer

Rollback of changes after a deployment

Changes are made to the destination org during the deployments. If the deployment fails or has some functional issues, (the issues maybe in the application or due to the failure/success of a build), you have an option to revert back to the original metadata.

User profile

Centralized dashboard for a user, to fill in the details and create a user profile, which includes version control and ALM mappings, roles, Salesforce orgs, etc.

User changes

During the project creation, when you select auto-commit to a version control system, you can have:

Single User commit

Changes made to the code are committed to the version control system of the selected user.

Multi user commit

Changes made by multiple users are committed to the version control system.

Full support for Perforce and TFS.

User based Auto-Commit in the Continuous Integration job.

Support for multiple account registrations for the same organization in the same system.

Stopping a scheduled build when there are no changes in a Salesforce Org.

Deployment using version control Revision number

Deployment validation.

On-demand and cherry-picked sandbox to sandbox deployments

Keep making changes in their source sandbox(s) and use the new Sandbox deployments functionality in AutoRABIT to view the list of changes done in a particular sandbox [ up to a line of a code level ] , select some, or all of them and then deploy them into a destination sandbox , as of them as and when you wish to do .

Keeping track of Deployments history

AutoRABIT keeps track of the changes attached to a particular label and deploy them into the destination. With “History” functionality you can view the changes done to a particular metadata member filtering with date or sandbox or project or author giving you the right audit needed for your project.