When you import a business process template, rules are applied that determine what components are imported from the export file, and what components are overwritten in an existing template.

Most components from a template can be imported, and will overwrite components in an existing template, but there are some exceptions. Before you import a template, it is important to be aware of the following rules so that you can prepare the importing system accordingly.

Components that are not imported

Related items such as contacts and tasks in a business process template are not imported and must already exist in the system to which you import the template.

For example, assume that you have exported a template that contains an entry action for one of its steps. This entry action references a task called Follow Up. If you want to import the template into another system, you must ensure that the importing system also has a corresponding task called Follow Up.

If a related item is present in an exported template, but does not exist in the system to which you import the template, you will not be able to complete the import. When the export file is checked, an error will be given and the Import button will be disabled. You can view the details of the error by clicking View Report.

The following components are not imported when you import a business process template. To help you read any errors, the components are listed using their names as they appear in the report.

Contact
The contact that a business process step, entry action, or exit action is for. Matched using the ID or, if the ID is not found, using the first name, last name, and telephone numbers. Contacts are managed in the Contacts workspace in NexJ CRM.

UserPerson
The user that a business process step, entry action, or exit action is assigned to. Matched using the ID or, if the ID is not found, using the first name, last name, and telephone numbers. Users are managed on the Users page in NexJ Admin Console.

ActivityPlanTemplate
An activity plan template used for an entry or exit action. Activity plan templates are managed in the Customize workspace in NexJ CRM.

ActionItemTemplate
A task template used for an entry or exit action. Tasks are managed on the Document Codes page in NexJ Admin Console.

AssignmentModel
The assignment model that a business process step, entry action, or exit action is assigned to. For example, Coverage or Opportunity Team. Assignments models are managed on the Assignment Models page in NexJ Admin Console.

AssignmentModelRole
The specific assignment model role that a business process step, entry action, or exit action is assigned to. For example, Account Manager or Advisor. Matched using the ID or, if the ID is not found, using the assignment model and the role enumeration value. Assignments model roles are managed on the Assignment Models page in NexJ Admin Console.

WorkQueueInteraction
The work queue that a business process step, entry action, or exit action is assigned to. For example, General Client Service Requests. Work queues are managed on the Work Queues page in NexJ Admin Console.

EntityHierarchyContext
The entity hierarchy that a business process step, entry action, or exit action is for. For example, Company or Household. Entity hierarchies are managed on the Entity Codes page in NexJ Admin Console.

EntityHierarchyRole
The specific entity hierarchy role that a business process step, entry action, or exit action is for. For example, Dependent or Spouse. Matched using the ID or, if the ID is not found, using the hierarchy and the role enumeration value. Entity hierarchy roles are managed on the Entity Codes page in NexJ Admin Console.

TelephoneNumber
The telephone number of the contact or user for a business process step, entry action, or exit action. This is used to match the contact or user when a match is not found using the ID, first name, and last name. Telephone numbers are managed in the Contacts workspace in NexJ CRM. They use the following international format: + <countryCode> <nationalDestinationCode> <subscriberNumber>.

UserGroup
The user group specified in the view or edit security settings of a business process step, entry action, or exit action. User groups are managed on the Users page in NexJ Admin Console.

Components that are not overwritten

In addition to the components that are not imported, some components do not overwrite duplicates in the system to which you import a business process template.

For example, assume that you have exported a template that contains an attachment called Financial Plan. If a document called Financial Plan already exists in the system to which you import the template, the document from the template will not overwrite the document in the importing system. The newly imported template will use the existing document in the system.

The following components are not overwritten when you import a business process template. When a duplicate component is found in the importing system, the import will proceed and a warning will be listed in the report. You can view the details of the warning by clicking View Report. To help you read any warnings, the components are listed using their names as they appear in the report.

ActAttachment
An attachment for a business process or business process step. If a match is found in the importing system, the attachment in the exported template will not be imported; the existing attachment in the system will instead be used. If a match is not found, the attachment will be imported and its document will be added to the root folder of the Document Manager.

ActTemplateResult
The outcome of a business process, either Approved or Rejected.

ActTemplateStatus
The status of a business process, one of Completed, Outstanding, or Pending.

DocumentMgrItem
A file in the Document Manager. If a match is found in the importing system, the document in the exported template will not be imported; the existing document in the system will instead be used. If a match is not found, the document will be imported and added to the root folder of the Document Manager.

flow:FlowTemplateVersion
The version number of the flow for the form in a business process template. Instead of overwriting this, the system increments the version number of the current flow.