Handle import events

When a message is imported using the storage mode or direct mode, for a successful import, the message should be deleted/confirmed from the source. In some cases, the message is not deleted/confirmed from the source, and it can be imported again and may result in a duplicate import.

You can use process maps that can take appropriate paths based on different import events which are triggered during the document import. Based on these events, a process map can avoid any duplicate import scenario. You can view the following events for a job in Kofax TotalAgility Workspace.

• IMPORTRUN: This event is triggered when the confirm/delete request is successful from the source system.

• IMPORTDUPLICATE: This event is triggered for one of the following scenarios and may result in duplicate document import:

  • If the source system does not receive the confirm/delete request due to errors.

  • If the source system responds that the message is already confirmed. This means that the message is already imported by another import source.

  An error message is configured in the ErrorMessage variable.

If the source system does not receive a confirm/delete request due to errors, such as network failure, and no event (either IMPORTRUN or IMPORTDUPLICATE) is triggered for a configured timeout, the process moves to the next node in the map. Default: 30 minutes

The sample process maps (Import Connector Event Handler Package.zip) are available in the TotalAgility installation folder. The default location is:

C:\Program Files\Kofax\TotalAgility\Sample Processes

You can import this ZIP file to the TotalAgility Designer, and then embed the ImportConnectorEventHandler process map in your existing process map or can create a new process map and embed the same in your process map.

Do the following to create a new process map:

1. Create a process map to add import events.

2. Create a process map for raising the import events.

3. Embed the process map created in Step 1 to your main map.