Now-a-days, I feel I am closely working with Superman! When I first read about Superman, I wondered about the existence of such super powers in the real world. Now I see them happen in front of my own eyes!
Yes, I am talking about the Salesforce Super Data Loader Pro of AutoRABIT. It has all the powers of a Superman.
Wondering how? Here is the analogy:
- Super Speed: Super Data Loader Pro can transfer millions of records from one sandbox to another, along with all their related entities, in a breeze.
- Super Senses: Super Data Loader Pro can sense the presence of parents at any level of ancestry, and pick up and transfer records with great ease and accuracy.
- Super Intelligence: The intelligence of Super Data Loader Pro to detect and resolve problems with circular references and its creative approach to handle multi-level self-references are unmatched to any other data loader out there, which makes it a stand out in the crowd.
- Super Locomotive: Super Data Loader Pro can take a load of gigabytes of records and attachments together in one cycle.
- Super Transcendent: Just by a click of a button, Super Data Loader Pro transfers a huge chunk of data from one sandbox to another regardless of the complexity of the relationships in the sandbox.
If we continue talking about the powers of the Superman, there is at least one similar feature in Super Data Loader Pro, which makes it as powerful as the Superman, with its superheroic capabilities.
Your ALM Tool indicates that a new User-Story has to be implemented, you are assigned a new task:
“New Custom Fields need to be added to existing custom Objects, some Profile changes need to be applied and Apex classes have to be modified.”
The Sandbox you work in is not your own. Other members of your international team, working in different time zones, need to use it as well. But that does not worry you.
No one on your team can even remember the last time anyone has overwritten someone else’s code. The Version Control System (VCS) together with timestamps and User ID records prohibit that from happening.
This is guaranteed by your cloud hosted Salesforce Release Management Automation Suite which makes logical connections between SFDC – the user of the Salesforce Release Management Automation Suite – as well as all Version Control commits.
You log into your Sandbox and start working on your task. Once done, you save your changes, update your User Story – and, log out.
You do not prepare change sets. Nor will you be updating elaborate excel sheets, you definitely don’t move anything between Orgs manually, and you definitely won’t be caught writing scripts for functional test cases either.
Your work is done for the day. Go have a few drinks with your friends.
The next day.
Your inbox has a new email stating that your changes have been moved through your SIT and QA/UAT, instance without a problem. Currently, they are already being used by many happy end users in production:
Metadata Migration (120 types) – Successful
Static Code Analysis – Successful
Code Coverage – Successful
Full Permission Set Migration – Successful
Full Profiles Migration – Successful
Functional Tests – Successful
Child/Parent Relationship Migration – Successful
Data Migration – Successful
ALM User Story Update – Successful
How did that happen?
While you were asleep AutoRABIT which is your end to end Release Management Automaton Suite ran a comparison between your Sandbox and VC. Triggered by your User Story Update it fetched all your latest changes and did a commit to your SIT branch.
Once complete, a predefined Salesforce Continuous Delivery (CD) process executed the deployment from VCS (SIT Branch) into the Staging and Integration Instance (SIT). It checked on your Code Coverage, emailed all concerned parties about its success and generated a detailed report.
The success triggered the next CD process, by first committing the changes to the QA/UAT Branch in Version Control and then promoting the updated metadata into the QA/UAT Instance. There the Static Code Analysis of Apex classes has been performed. In addition it ran all Functional Test Scripts, emailed all concerned parties about its success and generated a detailed report.
After successfully completing these tasks AutoRABIT – your end to end Salesforce Release Management Automation Suite, once again committed the changes, this time to the Production Branch. Then the metadata was pushed into Production, emails went out to all concerned parties about its success, a detailed report was generated, and the ALM User Story updated.
If this sounds too good to be true I invite you, no dare you to contact us. firstname.lastname@example.org. You will be surprised…
We are pleased to announce AutoRABIT 3.9 GA, the first GA release after Dreamforce’15, wrapping up most of the awesome feedback received during the event. Here is an update on the new features that will be made available for our customers over the weekend release scheduled for 17th Jan, 2016:
1. Salesforce Metadata Deployments:
a.Back-up and Rollback – You can now take a back-up of the destination metadata before deploying. The deployment can also be rolled-back in case of any functional issues.
b.Smart Profile Deployments – You can now deploy profiles with an option to Skip Visibility settings for the metadata members that are missing in the destination.
c.Metadata API Support for the Winter’16 release components .
2. Salesforce Data Migration Enhancements:
a.AutoRABIT Advanced Data Loader Pro has become more powerful with its comprehensive circular reference resolution algorithm. The Sandbox environment set up can be a breeze now with the records of an object along with the parent-child relationships transferred all at a time.
b.Filters on Record Types are provided to give more flexibility in restricting what records can be transferred to the destination.
c.Incremental Migration to ensure that you can synchronize your environments by migrating the delta of records on a schedule.
d.Chatter Data Migration support.
a.Thin Client for TFS – Salesforce Teams can now check-in to Team Foundation Server, Register Repositories , Create Branches in addition to deployments right from AutoRABIT .
b.Thin Client for Perforce – Salesforce Teams can now check-in to Perforce, Register Repositories , Create Branches in addition to deployments right from AutoRABIT .
4.ALM Integration – “ No Deployment” Theme supported for Jira
a.Automated deployments can now be scheduled into multiple environments based on the Jira User Story Status with AutoRABIT
b.Attach the metadata changes to Jira tickets for User Story-based deployments .
5.Test Automation Factory
a.Special Automation Templates to automate manual steps with Orchestra CMS deployments, Apptus and Skuid
a.Org Level ACL’s – Org Administrators can now set access control levels for various operations in AutoRABIT at the Salesforce Org level for team members .
b.User Profiles – Users logged into AutoRABIT can now map their Salesforce Org user and their SCM user details making it easier for Administrators in Salesforce Org Mapping step.
Please write to email@example.com for more information and detailed discussion on the Release features.