This section includes information about Data Veracity Collection agent's transaction behavior.
The agent emits commands that changes the state of the file currently processed.
Command | Description |
|---|
Begin Batch | |
End Batch | UDRs - Emitted when all UDRs have been collected or when a Hint End Batch request is received. The UDRs are then marked as Reprocessed in Data Veracity. Batches - Emitted after each batch has been processed. The batch is then marked as Reprocessed.
|
The agent retrieves commands from other agents and, based on them, generates a state change of the file currently processed.
Command | Description |
|---|
Cancel Batch | No Cancel Batches are retrieved. |
The Input/Output data is the type of data an agent expects and delivers.
The Data Veracity Collection agent collects and output either UDR Type or Batch Type according to the selection in agent configuration tab.
| Data Types | Description |
|---|
UDR Type | When the Collection agent is to collect UDRs, then the agent output type would be UDRType (DataVeracity). You can find the UDRType (DataVeracity) from the UDR Assistance. 
UDR Assistance | UDR Field | Data Type | Description |
|---|
| error_code | String | Error Code that associated with the erroneous UDR through udrAddError APL plugin. | | errorUDR | DRUDR | The erroneous UDR. | | id | Long | The unique ID of the record when inserted into Data Veracity. | | insert_time | Date | The Date Time when record is inserted into Data Veracity. | | metaData | map<string, any> | The MIMs defined in Data Veracity Profile and associated the value to erroneous UDR. | | state | String | The State of the erroneous UDR: NEW, UPDATED, REPROCESSED, PRE_DELETE, DELETE_APPROVED | | txn_id | Long | The Transaction ID when the batch of records are inserted into Data Veracity. | | update_user | String | The last person who updated the record. | | updated_time | Date | The last Date Time when the record was updated. | | workflow_name | String | The Workflow Name that inserted the record into Data Veracity. |
|
| Batch Type | When the Collection agent is to collect Batch files, then the agent output type would be BatchType (DataVeracity). You can find the BatchType (DataVeracity) from the UDR Assistance. 
UDR Assistance | UDR Field | Data Type | Description |
|---|
| error_code | String | Error Code that associated with the erroneous UDR through Error tab in Workflow Properties. | | id | Long | The unique ID of the record when inserted into Data Veracity. | | insert_time | Date | The Date Time when record is inserted into Data Veracity. | | message | String | The Cancel Batch message. If the Cancel Batch happened from cancelBatch plugin, this would be the custom message we passed in to the cancelBatch APL plugin. While if Cancel Batch happened from Dup Batch agent or Failed Decoding, this would be a system message. | | metaData | map<string, any> | The MIMs defined in Data Veracity Profile and associated the value to erroneous batch file through Error tab in Workflow Properties. | | source_node | String | The agent name that triggered the Cancel Batch event. | | state | String | The State of the erroneous UDR: NEW, UPDATED, REPROCESSED, PRE_DELETE, DELETE_APPROVED | | txn_id | Long | The Transaction ID when the batch of records are inserted into Data Veracity. | | update_user | String | The last person who updated the record. | | updated_time | Date | The last Date Time when the record was updated. | | workflow_name | String | The Workflow Name that inserted the record into Data Veracity. |
|
For information about the
MIM and a list of the general MIM parameters, see Meta Information Model in Administration and Management(3.0).
MIM Value | Description |
|---|
Agent Name | The name of the agent. |
Outbound UDRs | The number of UDRs routed from the agent. |
MIM Parameter | Description |
|---|
Agent Name | The name of the agent. |
Outbound Bytes
| The number of Bytes routed from the agent. |
Outbound UDRs | The number of UDRs routed from the agent. |
The agent does not itself access any MIM resources.