Inter Workflow Collection Agent in a Real-Time Workflow(5.0)
Open the Inter Workflow Collection Real-Time agent configuration dialog from a workflow configuration. Right-click the agent icon and select Configuration or double-click the agent icon.
Inter Workflow Tab
Field | Description |
|---|---|
Profile | Click the Browse button and select a profile that you want assigned to the agent. All workflows in the same workflow configuration can use separate Inter Workflow profiles, if that is preferred. In order to do that the profile must be set to Default in the Workflow Table tab found in the Workflow Properties dialog. After that each workflow in the table can be appointed different profiles. |
Use Custom Stream | Select this checkbox to enable Stream ID-based connections across multiple workflows using the same profile. When checked, collector and forwarding agents establish connections based on both the profile and a Stream ID, allowing workflows to link dynamically. In cases where a real-time workflow connects to a batch workflow, they scale as a unit, ensuring backend/frontend pairs stay linked via the Stream ID. Note! Example - Configuring a Stream ID in Inter Workflow Forwarder and Collection Agents Scenario: For example, if three processing workflows (A, B, and C) need to send data to three corresponding collection workflows (X, Y, and Z), you can define stream IDs like "A-X", "B-Y", and "C-Z". This ensures each processing workflow sends data to the correct collection workflow while maintaining a simpler, more scalable configuration. |
Stream ID | If you have checked the Use Custom Stream checkbox add a Stream ID. |
Decoder Tab
Setting | Description |
|---|---|
Decoder | List holding available decoders introduced via the Ultra Format Editor. The decoders are named according to the following syntax:
The option MZ Format Tagged UDRs indicate that the expected UDRs are stored in one of the built-in |
Full Decode | If enabled, the UDR will be fully decoded before inserted into the workflow. This may have a negative impact on performance since all fields may not be accessed in the workflow, making decoding of all fields unnecessary. If disabled (default), the amount of work needed for decoding is minimized, using a "lazy" method decoding sub fields. This means the actual decoding work may not be done until later in the workflow, when the field values are accessed for the first time. Corrupt data (that is, data for which decoding fails) may not be detected during the decoding stage and could cause the UDR to be discarded at a later processing stage. |