Deployment Using Feature Migration Template

This article will walk you through deploying nCino data using the Feature Migration template. This provides a step-by-step procedure for creating a fresh migration using the "Deploy from template configuration." If you're referring to this article for the first time, please navigate to Feature Migration Templates, which guides you through the process of creating a new migration template in AutoRABIT.

1. A Feature Deployment can be triggered in the following ways:

   a. Click on the "Create" button to see the options and select "Feature Deployment" as the option.

   

   b. Click on "Deployment History" under the nCino tab to access "Create feature deployment."

   
2. Upon selecting "Create Feature Deployment" or "Feature Deployment," a Source Type screen will appear—choose from the available options to proceed.

1. On selecting the "Source Type", the "Source" screen will be displayed.

1. Continue to input the required fields on the screen:

   1. Label Name: Input the desired label name.

   2. Description: Input a matching description that best describes the deployment.

   3. Feature Type: Select from either "Standard" or "Community" options.

   4. Feature: Select the required feature from the list available.

   5. Version: Select from the versions available.

2. Upon entering the required details, click on 'Next' to continue to the Destination screen.

1. The destinations can be "Salesforce Org" and/or "Version Control."

2. To deploy to a Salesforce Org, enable the Deploy To slider and choose your Destination Org. To commit to a branch, enable the Commit To slider, select the Repository/Branch details, and enter a comment (if any).

3. After selecting the destination(s), continue to the "Job Settings" page to select the required settings.

1. Before deploying to the destination, review and select from the available deployment criteria to proceed.

   Deployment Filters

   1. Disable Workflow Rules: This option will deactivate the workflow rules associated with the objects part of the deployment.

   2. Use Bulk API (Batch API will be used if not enabled): You can transfer bulk records at one time from the source and destination org.

   3. Use UTF-8 file encoding for file read and write operations: Use UTF-8 as the internal representation of strings. Text is transcoded from the local encoding to UTF-8 when data is written to or read from a file. UTF-8 must be enabled if your data exclusively contains English alphabet. UTF-8 must be disabled if your data contains non-English alphabets. UTF-8 should be enabled by default in accordance with Salesforce.

   4. Automap User/Owner Data: To ensure user permission differences between different environments will not affect the RBC deployments, users are provisioned to disable the auto-assignment of users as they trigger the RBC deployments.

   5. Disable Validation Rules: This option will deactivate the validation rules associated with the objects part of the deployment.

   6. Insert/update with Null Values: This will either insert or update record field values with null in the destination org (if the value is null in the source org).

   7. Enable Rollback: Enabling this option makes sure that the done deployment can be rolled back to the desired previous state.

2. Continue to the "Preview" tab to review to go through the selection made and to either "Retrieve Dataset" or "Retrieve Dataset, Deploy and Commit"

3. Upon selecting either the "Retrieve Dataset" or "Retrieve Dataset, Deploy and Commit" options, you will be redirected to the "Deployment History" page.