Create a Feature Migration Template
This details the step-by-step process to create a standard/community nCino migration template.
- Hover your mouse over the nCino module and click on the option: Feature Management.
- Click on New Feature Migration Template button.
- On the next screen, click Create New to create a fresh template and include objects of your choice.
- You'll be taken to the record-based configuration section, where you will find three tabs that need completed to proceed ahead:
- Metadata Configuration
- Record Configuration and
- Preview and Save
You need to provide basic information on this tab to create a feature migration template.
Under Feature Details, enter the items below:
- Name: Provide a feature migration template name.
- Associated Partner: The default associate partner would be nCino, which you can change if necessary.
- 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:
- Choose your Salesforce Org.
- Click Fetch Objects to retrieve all available objects in the selected Source Org.
- 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.
- Using / button, you can select/deselect all the objects for your template. Or, use the Ctrl key and select multiple objects of your choice and move them to the selected tab using /button. Once you have selected the object, ARM will retrieve the fields included in that object behind the scenes.
- Click on Next to go to the Record Configuration Tab.
This tab is where you apply filters for the entry objects. Also, on the left side of the screen, you can see the list of items that are segregated into:
- Selected List: This will include a list of all objects that are part of your selected template and objects that you have chosen to add later on.
- Related List: This section will only be displayed in the Attachment Object as your migration template feature is included.
- Required List: This contains mandatory objects which you cannot exclude,
- Excluded List: This section lists non-required data objects you could permanently exclude while creating a template so that the template does not contain data object information. Some of the objects are auto-selected depending on the selected template, and you have the option to de-select them as well.
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.
The entry object is selected by default, and the user can apply a filter. The entry object is denoted by “E”.
Applying the Filters
Apply the filter(s) using the steps as shown below:
The filter query is added and displayed in the filter box. You can edit the query if any modification is required. Nevertheless, multiple queries can be added based on your requirements. Validate your query to see whether the query entered is stable. Additionally, you'll be able to view several records that will get fetched.
- All records that get fetched will be in order by "ASC nFORCE__lookupKey__c." Nevertheless, if "nFORCE__lookupKey__c" is unavailable, then using order by "ASC Id," the records will be fetched.
- For the Attachment object, the filter cannot be applied.
You can also use the Query Editor to execute a SOQL query on the selected Source Org. Results are displayed in a Query Results grid.
Similar steps are to be followed for objects in other buckets as well.
Once done, click Next to proceed to the Preview and Save screen.
- If your nCino objects include an Attachment object, users must confirm whether they want to fetch the Attachment dataset.
- 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 APIs limit being exceeded and the application reporting an error.
Preview and Save
This is the summary page for the Feature Migration template you're about to create. You can view the features details, and filters you have applied for the last time before the template is created. Any change log information that needs to be added can be mentioned in the Change Log box.
Click Save, and you will be redirected to the Feature Migration Summary screen, where you can track your template recently created.
Next Article: Feature Migration Summary Page