Salesforce Org Management
  • 14 Nov 2022
  • 4 Minutes to read
  • Contributors
  • Dark

Salesforce Org Management

  • Dark

Important Note:
This article is for the 'Org Administrator' in particular. The actions discussed in the article will not be available to the General Users.  


All of the org connections added to AutoRABIT can be seen on the Salesforce Org Management page. This page lists details for the Salesforce Org you have added yourself, and any org that has been shared with you by members of your team.

The Salesforce Org Management page shows information about:

  1. Details of your Salesforce Org
  2. ALM / Plugins mapped with your Salesforce Org
  3. List of metadata members available with your Salesforce Org
  4. Default Apex Test Class configured
  5. User Permissions assigned to your Salesforce Org

Salesforce Org- Details

A summary of the Salesforce org registered with AutoRABIT is displayed in this area.

The fields displayed in this section are described in the table below: 

Field NameIndicates
NameName of the Salesforce Org given at the time of registering with AutoRABIT
TypeSalesforce Organization types such as Developer, Sandbox, or Production Org
EnvironmentYour Salesforce Environment i.e., Production or Development Edition, Sandbox, or Production
URLSalesforce login URL
Registered DateDate of account activation
Access TypeAuthorization type such as OAuth, Standard. For the 'Standard' Access type, the username, password, and security token will be displayed.
Re- AuthenticateIf the OAuth token has expired for a saved connection, click this to re-enter your user credentials and refresh the connection so AutoRABIT can continue to connect to it.
Test ConnectionTo check if the connection has been authenticated or not. Once clicked, a success message is displayed once the authentication is successfully complete.
Person Accounts EnabledWhen you do business with individual consumers, you can enable the Person Accounts. Person accounts are applicable to organizations that operate on a business-to-consumer model. Remember that you cannot disable Person Accounts once you enable them. For more information, refer to the article published in Salesforce:
nCino Package EnabledThis checkbox is selected by default if your Salesforce Org is enabled with nCino objects. Unselecting the checkbox will remove the nCino objects configured with your Salesforce Org and you'll not be able to use the nCino metadata and data for deployment.
About nCino Package Enabled
Selecting the 'Enable nCino package' previously required getting all nCino deployed packages of the Salesforce org; however, users without Modify All Data and Download App permissions were unable to register the org in the AutoRABIT application. To avoid this, the mandatory option to load nCino deployed packages while registering a Salesforce org has been disabled.

Additional options under 'Salesforce Org - Details' section

  1. Clone: AutoRABIT clone functionality is used to create records that are like each other, reducing unnecessary retyping.
  2. View/Download Audit Log: The audit log shows the recent changes made to your org. It lists the date of the change, who made it, and what the change was. All objects include fields to store the name of the user who created the record and who last modified the record. This provides some basic auditing information. To save the audit log in your local system, use the Download Audit Log button.
  3. Generate Code Coverage Report: This function allows you to run all available Apex Test Class in the Salesforce org and generate a code coverage report for the same. The code coverage report will be emailed to your registered email id with the CSV file attached. The CSV file will contain the failed test classes that require the user's attention to resolve.Attached is the sample email that's will be notified to the user whenever the code coverage is run.
    Code Coverage with a success rate of more than 75%
    Code Coverage with failure count of more than 20
    Code Coverage with failure count of less than 20 (detailed error report will be included in the email body)

Salesforce Org- Mappings

Mapping your Salesforce Org with your Version Control System and/or ALM configured in AutoRABIT. This helps in creating a control during a Commit, Merge, or Deployment action that is performed on your Salesforce org or Version Control branch.

Let us assume you would like to connect your Salesforce Org with Version Control as a GIT

  1. Click on the Mapping button for Version Control as GIT.
  2. Select the respective Version Control Repository and the Branch for your GIT.
  3. Click Test Connection to authenticate your connection.
  4. Do not forget to click on Save Mappings to save the details or else you need to repeat the above steps again.

In another scenario, let us assume you also like to configure JIRA (ALM tool) with your Salesforce Org. 

Important Note:
To proceed ahead with the below steps, make sure the JIRA is successfully integrated with AutoRABIT (LEARN MORE)
  1. Click on the Mapping button beside JIRA. 
  2. Select the JIRA label and the Project from the drop-down list. 
  3. Click on Save Mappings to save the details and you're done.

Salesforce Org- Skip Members

In this section, you can add certain metadata members from your Salesforce org that will be skipped whenever any deployment happens to the org.

Let us assume you would like to skip Analytics Cloud Integration User, Analytics Cloud Security User, and Authenticated Website metadata members for the 'Profile' metadata type. In such a case, you need to select the Type as Profile under and click on the Fetch Members button.

Select the metadata members from the list. These members will be skipped each time the deployment is performed on the above Salesforce org. Click OK.

In a similar fashion, you can add different metadata members for various metadata types. Additionally, if you do remember certain members that you like to add manually, you can do so by entering in the Enter members manually field and click Add.

A summary of the selected metadata members can be seen in the Salesforce Org- Skip Members section. Click on Save Members to save the steps configured.

Salesforce Org- Default Apex Test Class Configuration

This section is all about configuring the default Apex Class for your Salesforce Org. This topic is covered in a separate article. Refer to the article HERE.

Salesforce Org- User Permissions

The list of users allowed to work with your Salesforce Org is available in this section. The administrator may assign permission to its users on various modules of AutoRABIT that are feasible with the Salesforce Org.

Was this article helpful?

What's Next