9.24.6.2 ECS Collection Workflow

Owned by Jenni Wallin
Last updated: May 11, 2023 by Former user (Deleted)
2 min read

In order to send a UDR to ECS, a workflow must contain an ECS forwarding agent. To perform a table lookup for all UDRs, an Analysis agent is used. If the lookup succeeded, the UDR is sent on the OK route to be saved on disk, while the failing UDRs are sent to the ECS forwarding agent.

n the collection workflow the same evaluation is tried again. If it fails, the UDR is sent back to ECS with the same configuration.

The prerequisites for being able to collect ECS data is that the UDRs or batches must each belong to an existing reprocessing group, and have the reprocessing state set to New.

A workflow collecting and validating ECS data


Since we want to redo the processing made in the forwarding workflow, we keep the configurations of the ECS Inspector and ECS forwarding agents the same as in the previous workflow.

Workflow Properties

The Error tab in the Workflow Properties must not be configured to handle cancelBatch behavior, since it will never be valid for ECS collection workflows. No calls to cancelBatch are allowed from any agent since it will cause the workflow to immediately abort.

ECS Collection Agent

All UDRs conforming to the collection criteria will be selected and processed as a batch.

Analysis Agent

The Analysis agent only needs to validate and route the UDRs. The Error Code and Error Case is already associated with the UDR.


Example - Analysis agent

udrRoute( input, "error" );

Example - Reassigning to a Different Reprocessing Group

Suppose there is a workflow collecting and validating UDRs from ECS. If the validation fails, the UDRs will be sent back to ECS with an associated Error Code. UDRs assigned to a new or a different Error Code will directed to a new reprocessing group. If desired to associate these UDRs with a different reprocessing group, udrClearErrors must be called prior to udrAddError.

The exception is if the new Error Code is associated with the same reprocessing group.

Case 1 - same reprocessing group

If the new Error Code belongs to the same reprocessing group:

  • Using udrClearErrors will result in a new Error Code and reprocessing group being associated with the UDR in ECS. It will also avoid several Error Codes pointing at different reprocessing groups which makes automatic group assignment impossible.

  • Leaving out udrClearErrors will result in old as well as new Error Codes (including the reprocessing group) being associated with the UDR in ECS.

Case 2 - different reprocessing group

If the new Error Code belongs to a different reprocessing group:

  • Using udrClearErrors will result in a new Error Code and reprocessing group being associated with the UDR in ECS.

  • Leaving out udrClearErrors will not result in any association to a reprocessing group, however both Error Codes are associated with the UDR in ECS.

Note!

All UDRs collected at one activation of the workflow will be processed as one batch.

Any call to cancelBatch will cause the workflow to abort immediately.

Next:

9.24.7 Example - ECS handling of batches