3.12 Correspondence Batch

Correspondence batch currently runs in two sub-batches.

• Batch 1:

  This batch will get all correspondence related facts for all active accounts which are in collections.

  Job Name: obcr-communication-facts-batch

  Setup Prerequisites

  Following is the prerequisite for the setup:

  Data is available in table DM_ACCOUNT from hosts.

  Dependent Batch/Job: Not Applicable

  Multi-threaded: Yes

  Multi-stream: Yes

  URI : <protocol>:// obcr- correspondence -services/jobLauncher/runBatch/

  Table 3-37 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	Entity ID of the request.
  Accept	Application/json	Yes	Content Type of the request.

  Specify following parameters while executing this batch:

  Table 3-38 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.

• Batch 2:

  Job Name: obcr-communication-email-batch

  This batch evaluates all active correspondence template rules against each account and perform communication via letter or email or sms as per the configuration maintained.

  Setup Prerequisites

  Following is the prerequisite for the setup:

  Batch 1 which is obcr-communication-facts-batch must be completed first.

  Dependent Batch/Job: obcr-communication-facts-batch

  Multi-threaded: Yes

  Multi-stream: Yes

  URI : <protocol>:// obcr-correspondence-services/jobLauncher/runBatch/

  Table 3-39 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	Entity ID of the request.
  Accept	Application/json	Yes	Content Type of the request.

  Specify following parameters while executing this batch:

  Table 3-40 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.
  commMode	“letter,email”	No	It is required if you want to perform certain mode of communication in particular.

Success/Failure Details:

• User can verify the record level status in the following tables in CR_CORR schema.
  • DM_COMM_ACCOUNT_DRIVER
  • DM_COMM_ACCOUNT_FACTS_DRIVER
• For a successful processing of a record, the below condition should be satisfied.

  ERROR_CODE = ‘Success’ and PROCESS_RESULT = ‘1’