About importing processes between version of TotalAgility

The system makes some changes when importing a process created in TotalAgility 5.5.0 or 6.0, or upgrading from a 5.5.0 or 6.0 installation to TotalAgility 7.1.0:

  • Upgrades all processes.

  • Retains the Custom Data groupings for variables in the database but does not display them in the interface.

  • Changes (sometimes) the layout of the process due to the new process styling but does not alter the flow.

  • Imports all resources that do not exist in the process where they are imported, and retains resource assignments.

  • Retains the original settings of the following nodes: Loop, Document Creation, TRIM Create Folder, TRIM Add Document, TRIM Get Document, RESTFul web service, Supporting Info, Email, SharePoint Create Site, SharePoint Create Folder, SharePoint Add Item, SharePoint Delete Item, SharePoint Move Item, SharePoint Get Document, Dynamics CRM, CMIS Add Document, CMIS Update properties, CMIS Get Document, MIS Find Document, CMIS Cancel Checkout Document, CMIS Check In Document, Exchange Server Get Attachments, Ready For Review, and Business Rules.

    • Upgrades custom nodes and executes them according to the 5.5.0 functionality.
    • Updates all live jobs so that these nodes can execute.

  • Retains all common properties for .NET, Web Service, Create New job (process in 5.5), Script, C# and VB .NET nodes, with the following limitations:

    Note VBSCRIPT is not supported in on-premise multi-tenancy environment.
    • Does not allow changing .NET, Web Service, Create New job (process in 5.5.0), Script, C# and VB .NET nodes (created in 5.5.0) from automatic to manual and therefore converts these nodes to Synchronization nodes on import.
    • To retain the configuration for supported types, set the nodes to automatic in 5.5 before you export the process.
    • After upgrading to 7.1.0, if you try to take and complete an activity of the .NET, Web Service, Create New job (process in 5.5.0), Script, C# and VB .NET types that are in Live Jobs, the activity fails.

  • Converts the COM, COM Transactional and BAM Event nodes to Synchronization nodes. After upgrading to 7.1.0, if you try to take and complete an activity of the COM, COM Transactional and BAM Event types that are in Live Jobs, the activity fails.

  • Retains all entities with attributes of each type without changing the properties.

  • Retains all exceptions. However, the exceptions that are imported from 5.5.0 and not supported in TotalAgility 7.1.0 are not available within the system and therefore cannot be used.

  • Upgrades the logic rules created in 5.5.0 as follows:

    • Changes each expression to a decision.
    • Changes each calculation to an expression node.
    • Changes each return to an end point.
    • Creates Inputs/Outputs as variables and retains the settings.
    • Imports business rule parameters as server variables and accordingly uses them within the flow rule; displays the Business Rule Parameter category in the Explorer.

Note If enforcing FIPS cryptography algorithms on the Kofax TotalAgility server, then to import a process map exported before 7.0.2, FIPS must be disabled. Otherwise the import may fail if Kofax TotalAgility resource or integration passwords are being imported. Once the import is complete, FIPS can be enabled again. You do not need this for import of processes exported in 7.0.2.