Handle import events

When a message is imported using storage or direct mode, it 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 to take appropriate paths based on different import events that are triggered during document import. Based on these events, a process map can avoid duplicate import scenarios. You can view the following events for a job in Tungsten 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, such as a 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)

  • If the source system responds that the message is already confirmed, which means that another import source has imported the message.

  An error message is configured in the ErrorMessage variable.

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

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

You can either import this ZIP into TotalAgility Advanced Studio and embed the ImportConnectorEventHandler process map in your existing process map or 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 into your main map.