Create a Feature Migration Template

Overview

This details the step-by-step process to create a standard/community nCino migration template.

Step-By-Step Guide

1. The “New Feature Migration” template can be created through either of the highlighted options

   • Feature

   • Feature Management

2. Click on the “Feature” option under the "Create” drop-down to initiate a new feature migration template creation

1. Click on the “Feature Management” section under the “NCINO” section to navigate to it.

2. Click on the “Create feature” button on the “Feature Management” screen

1. Once the selection is made, the creation of the “Feature Migration Template” will be initiated by landing on the Feature page.

2. You'll be taken to the record-based configuration section, where you will find three tabs that need completed to proceed:

   • Metadata Configuration

   • Record Configuration and

   • Preview and Save

Metadata Configuration

The following screen should be visible on clicking the "Feature" or the "Create Feature" option.

Under Feature Details, enter the items below:

1. Name: Provide a feature migration template name.

2. Associated Partner: The default associate partner would be nCino, which you can change if necessary.

3. Version: Enter the version number here. If you're creating the feature template for the first time, it is recommended to keep the version number as 1.0.

Under the Salesforce Org Details section, do the following:

1. Select the required “Source ORG”

2. On selecting the required “Source ORG”, the related objects will be fetched automatically.

3. By default, only nCino objects available in the Source Org will be auto-populated. To view all the objects available, click on Show All Objects.

1. Click on Next to go to the Record Configuration Tab.

Important Note: Only those objects will be considered nCino objects if their related prefix is included in the Plugins section under the My Account page.

Record Configuration

1. The filters can be applied on the entry objects under this tab

2. The following can be observed under this tab:

   • The “Selected Objects” were displayed under the “Object Bucket List” with the columns “Entry Object”, “Object name” & “Query”

   • Bucket Exclusion Objects: Objects selected here will be excluded from further processing

   • Bucket Mandatory Objects: Objects displayed under this section are mandatory

1. Based on the relationship between the objects, the AutoRABIT application will segregate the object sets, and applying a filter to each bucket is mandatory. By default, AutoRABIT will denote an object in a bucket as an entry point, which can be applied filter. This is not mandatory, but as a best practice, AutoRABIT recommends applying filters to the entry point object rather than any other object.

Applying the Filters

The filter criteria can be entered and the query can be built under this tab.

1. Click on the pencil icon beside the query.

1. On clicking the pencil icon, the ‘query builder’ will be opened.

1. Clicking on the ‘field’ drop-down will provide the list of fields from the ORG.

1. Clicking on the operator drop-down field the available list of operators can be observed

1. On completing the field selection, click on the ‘ADD’ icon to add the query to the ‘query editor’ below.

1. Once the query is added to the query editor, the query can be validated by clicking on the ‘Validate’ button.

2. An SOQL query can also be added to the query editor. After adding the query, the query can be validated.

1. On validating the query, the application will display a success message.

Important Note:

1. All records that get fetched will be in order by "ASC nFORCE__lookupKey__c." If the "nFORCE__lookupKey__c" is unavailable, then the records will be fetched in order by "ASC Id."

2. For the Attachment object, the filter cannot be applied.

1. As the query has been validated, the same query can be saved by clicking on the ‘Save’ button on the ‘Query Builder.’

Important Note:

1. If your nCino objects include an Attachment object, users must confirm whether they want to fetch the Attachment dataset.

2. Check the number of attachments pulled for the job once the attachment object is selected for the data deployment. For each API call, Salesforce returns at least one and a maximum of five attachments based on the size of the attachments. More APIs calls will get triggered for more attachments, which may result in the API limit being exceeded and the application reporting an error.

1. The query should be added to all the buckets. Click on 'Next' to continue to the “Preview and Save” step of the “Feature Migration Creation.”

Preview and Save

This is the summary of the “Feature Migration Template” that is being created. All of the feature details can be observed on the ‘Preview and Save’ page. On the ‘change log,’ any change log information required can be added.

Important Note: Related List section will display only if the Attachment object is part of the Feature Migration Template.

1. On verifying all the details on the ‘Preview and Save’ page, save the template by clicking on the 'Save' button.

2. On clicking 'Save,' you will be redirected to the “Feature Management” page.