3.2.10 Dialer Extract Batch

This topic provides information about the Dialer Extract Batch process.

• Batch 1:
  Dialer Account Filter batch:

  • This batch will pick up all accounts from DM_TASK table that have call type tasks either in Open or WIP status and follow-up date for these tasks is as per the parameter defined.
  • In the next step fact values are fetched for each of the above account and then filtered further based on rules defined for the selection criteria.
  • These accounts are then saved.

  Job Name: obcr-dialer-accts-filter-batch

  Dependent Batch/Job: Not Applicable

  Multi-threaded: Yes

  Multi-stream: Yes

  URI : <protocol>://obcr-data-exchange-services/jobLauncher/runBatch/

  Table 3-52 Mandatory Headers

  Parameter Name	Value	Mandatory	Description
  appld	CRDATAEXCHNG	Yes	The application ID of the host service.

  Specify following parameters while executing this batch:

  Table 3-53 Parameters

  Parameter Name	Value	Mandatory	Description
  runDate	01102023	Yes	It must be in ddmmyyyy format.
  branchCode	DMO	Yes	The branch code of the project.
  userId	ADMINUSER1	Yes	The user ID of the user triggering the batch.
  followUpDays	1	No	Number of Maximum Follow-up days (On Task) from Current Business Date to be considered.
  campaignCodes	SEGMENT_EC	Yes	The campaign code will be the condition(rule) which needs to be evaluated to identify the accounts to be sent to dialer system. Multiple comma separated rules are supported.
  overrideDate	2023-10-01	No	It must be in yyyy-mm- dd format. It is required to run the batch for a specific day.

• Batch 2:
  Dialer Account Filter batch:

  • Additional data is fetched by making API calls to different services for all the accounts of batch 1 (Dialer account filter batch) above.
  • Data persisted in the DB.

  Job Name:obcr-dialer-data-extract-batch

  Dependent Batch/Job: obcr-dialer-accts-filter-batch

  Multi-threaded: Yes

  Multi-stream: Yes

  URI : <protocol>://obcr-data-exchange-services/jobLauncher/runBatch/

  Table 3-54 Mandatory Headers

  Parameter Name	Value	Mandatory	Description
  appld	CRDATAEXCHNG	Yes	The application ID of the host service.

  Specify following parameters while executing this batch:

  Table 3-55 Parameters

  Parameter Name	Value	Mandatory	Description
  runDate	01102023	Yes	It must be in ddmmyyyy format.
  branchCode	DMO	Yes	The branch code of the project.
  userId	ADMINUSER1	Yes	The user ID of the user triggering the batch.

• Batch 3:
  Dialer File Generation Batch:

  • Account and Customer numbers are picked for all accounts stored in batch 2 (Dialer Data Extract Batch) to store in the Driver table (DM_DIALER_FILEGEN_DRIVER) Rest of the details are fetched from DM_DIALER_EXTRACT_DATA for each account in the driver.
  • All the records along with column headers are stored in the file as per the details mentioned in the properties file.

  Job Name: obcr-dialer-file-gen-batch

  Dependent Batch/Job: obcr-dialer-data-extract-batch

  Multi-threaded: No

  Multi-stream: No

  URI : <protocol>://obcr-data-exchange-services/jobLauncher/runBatch/

  Table 3-56 Mandatory Headers

  Parameter Name	Value	Mandatory	Description
  appld	CRDATAEXCHNG	Yes	The application ID of the host service.

  Specify following parameters while executing this batch:

  Table 3-57 Parameters

  Parameter Name	Value	Mandatory	Description
  runDate	01102023	Yes	It must be in ddmmyyyy format.
  branchCode	DMO	Yes	The branch code of the project.
  userId	ADMINUSER1	Yes	The user ID of the user triggering the batch.

Success/Failure Details:

User can verify the record level status in the following tables in CR_DATAEXCHNG schema.

• DM_DIALER_ACCTS_DRIVER
• DM_DIALER_FILEGEN_DRIVER

For a successful processing of a record, the below condition should be satisfied. ERROR_CODE = ‘Success’ and PROCESS_RESULT = ‘1’