Import a process
You can import process maps between different TotalAgility installations.
Importing a process map is subject to the following:
You can only import an unlocked map unless the map is locked by the user performing the import.
You can only import a higher version process than the process version available on the system. You cannot import a lower version process than the version available on the system.
When you import a map from an older version into Kofax TotalAgility 7.6.0 and the Password hashing algorithm has been set to Scrypt (System> System settings > Logon and authentication>Passwords and logon), the resources with passwords will fail to logon to TotalAgility as the passwords can no longer be decrypted. To logon, the password for each resource must be reset by the administrator.
When importing packages simultaneously on a split Kofax TotalAgility Web Application deployment, a maximum of 100 concurrent connections from the Web server to the Application server is configured by default. To change this:
In Agility.Server.StreamingService.exe.config available in the same folder where the Streaming service exe resides, locate the following:
<connectionManagement> <add address="*" maxconnection="100" /> </connectionManagement>
Update the maxconnection value.
The Import page is displayed.
Browse to the file that has processes to import or drag the files from your machine to the
File to import box. The following message appears:
The file you have selected contains a process.and the appropriate import options are displayed.
The following items are automatically imported along with the process.
The category of the web service is imported and created if not already existing.
If the web service being imported has the same ID as the existing web service, the imported web service is used.
You can import web services manually or separately.
Including the following capture activities:
If existing roles are being imported for a new version of an existing process map, you can choose to overwrite role members.
If a template with the same name exists, and
If you select this option, all the elements of the existing template are replaced with the elements of the imported template.
If you clear this option, all the elements of the imported template are added to the existing templates.
If a template with the same name does not exist, the imported template is added as a new template.
If an existing entity has the same name as the entity being imported, you can choose to overwrite it.
If the entity contains multilingual lookups, all the content for the lookup is imported with the entity.
If an existing lookup has the same name as the lookup being imported, you can choose to overwrite it.
When importing a capture-enabled process map, the associated profiles are imported, even if they do not exist in the system.
If a thread pool being imported has the same ID as the existing thread pool, the imported thread pool is used.
If the server variables being imported already exist on the importing machine, they are not overwritten.
If process variables on the imported process map exist as server variables on the server with only difference of type, Clashing variables occur. A warning identifies the process variables that pose a problem during import.
Importing a capture-enabled process, also imports any document type or folder type variables configured as initialization variables.
If you import a process map that has a checklist item with the same name as one on the importing machine, the existing checklist item is overwritten. Otherwise the imported item is added as a new item.
Extraction groups associated with classification group
Document types associated with extraction group
The classification group, extraction group and document types of a process are imported even if they do not exist on the system.
By default, the classification group, extraction group, document types are imported to the Default category. To import the classification group, extraction group and document types to the specified category, select Category.In Kofax TotalAgility Azure and On-Premise Multi-Tenancy system, the maximum limit of the extraction and classification group is set to 500MB. When you exceed this limit, a message is displayed stating that the action cannot complete. To configure this limit, update the value for MaxCaptureProjectSize in the Web.config file of TotalAgility Azure.
In Kofax TotalAgility On-Premise, the maximum limit of the extraction and classification group is set to 2GB. When you exceed this limit, a message is displayed stating that the action cannot complete.
If a predictive model is defined, the weighting and score calculation for the process are included in the selected version of the imported process.
If the Evaluate score property is selected (in the Advanced tab and After processing tab) for an activity, those are also imported for the selected process version.
Optional items to import include:
Categories saved with the process map.
This option is only available if categories were exported with the process map being imported.
Any resources saved with the process map.
If an existing worker resource has the same UserID or ResourceID as the resource being imported, the existing resource is used by the imported process map.
If a non-worker resource or a category exists with the same name and type or ResourceID as the resource being imported, the existing resource is used by the imported process map.
If you import a resource without an active email ID, and the Unique Email Enforcement option is set Yes in the system settings module, then an error message is displayed.
Group resource members
Includes details of the members of any resource groups.
This option is only enabled if the Resources option is selected.
Imports all the export connector mappings.
Ensure all the export connectors are installed on the target machine; otherwise, an error occurs and the process is not imported.
By default, the work types, role members, checklist templates, entities, lookups, profiles (Scan/VRS, PDF generation
and Separation) are overwritten. You can choose to overwrite page renditions and reporting tags.
If you select to overwrite page renditions, the existing setting is overwritten by the setting included in the process. For example, the target machine has Rendition 1 and Rendition 2 and the process has Rendition A and Rendition B.
If overwritten, Rendition A and Rendition B are retained in the target machine.
Otherwise, Rendition 1 and Rendition 2 are retained in the target machine.
The selected maps are imported.
If any errors or warnings occurred, the information appears. If any variables or variable types clash, or if the required Web services are unavailable, you can view the details of the error.If an error exists, you cannot import the map until you fix the error. If warnings occur, you can still import the map.