3.7 Dashboard Data Population Batch
Oracle Banking Collections has the capability to calculate the historical data and key performance indicators to be displayed on the collector’s dashboard.
Job Name: obcr-dashboard-data-population
Setup Prerequisites
NA
Dependent Batch/Job: Not Applicable
Multi-threaded: Yes
Multi-stream: Yes
URI : <protocol>://obcr-dashboard-services/jobLauncher/runBatch/
Table 3-25 Mandatory Headers
Parameter Name | Value | Mandatory | Description |
---|---|---|---|
Userld | ADMINUSER1 | Yes | User Id of the Requesting user. |
Appld | CRSEG | Yes | The application ID of the host service. |
branchCode | DMO | Yes | Branch Code of the requesting user. |
entityId | DEFAULTENTITY | Yes | EntityID of the Request. |
Accept | Application/json | Yes | Content Type of the Request. |
Specify following parameters while executing this batch:
Table 3-26 Parameters
Parameter Name | Value | Mandatory | Description |
---|---|---|---|
runDate | 01102023 | Yes | It must be in ddmmyyyy format. |
branchCode | DMO | Yes | Branch code of the project. |
userId | ADMINUSER1 | Yes | User id of the user. |
overrideDate | 2023-10-01 | No | It must be in yyyy-mm-dd format. It is required to run the batch for a specific day. |
pastDays | 180 | No | Number of past days to be considered while calculating historical and performance data of collectors. |
Success/Failure Details:
User can verify the record level status in CR_DASHBOARD table in CR_DASHBOARD schema. For a successful processing of a record, the below condition should be satisfied.
ERROR_CODE = ‘Success’ and PROCESS_RESULT = ‘1’
Parent topic: Batch Execution Details