9.15.2.1 Data Veracity Collection Agent Configuration
- Jenni Wallin
- Former user (Deleted)
- Karthik Bangalore
- Former user (Deleted)
The Data Veracity Collection agent configuration window is displayed either when right clicking on the Data Veracity Collection agent in a workflow and selecting or double clicking on the agent. You can select to either collect data from an Error Code that has been defined in the Data Veracity Web UI or from a filter that has been saved in Data Veracity Search. The available settings in the configuration dialog depends on which option you choose.
Data Veracity collection configuration
| Setting | Description |
|---|---|
Profile | Click Browse to select a predefined Data Veracity Profile. The profile contains details about the Data Veracity For further information, see 8.7 Data Veracity Profile. |
UDR Configurations | This table is where all UDRs, Collection Type and Value of the Collection Type will be displayed. The Collection Type will vary between Error Codes and Saved Filters with the Value being the Error Code name or the Filter name. Only 1 UDR Type Only 1 UDR type will be allowed, regardless of Collection Types. |
Collection Size | This field will hold the value of the batch size used to fetch the TXN_IDs, size for the updates to the database tables and also the total size for each batch transaction. The default value is 5000. The range for the value is 1 - 100000. |
| SQL Bulk Size | This field will hold the amount of UDR the agent will collect from the database table. The default value is 1000. The range for the value is 1 - 100000. |
| State | This combo box displays a list of states that indicates which UDRs with the corresponding state to collect from the database. The choices presented in the list are NEW, UPDATED and NEW or UPDATED. The default value is NEW or UPDATED. |
| Read Only | This check box will have the agent retrieve the Data Veracity UDRs without updating the state of the UDRs from the database. e.g UDRs that were collected with the state NEW will not have its state changed to REPROCESSED when Read Only is enabled. |