3.5 Tasks Initiation Batch

  • Batch 1:
    1. Segmentation batch will update segment creation date for all accounts where new segments are stamped. Tasks are initiated based on the rules defined for all strategies of these newly assigned segments.
    2. Tasks for strategies and segments which are de-linked from the account (based on segment end date) are moved to history table.

    Job Name: obcr-task-init

    Setup Prerequisites

    Following is the prerequisite for the setup:

    Recommended to run after segmentation batch.

    Dependent Batch/Job: Not Applicable

    Multi-threaded: Yes

    Multi-stream: Yes

    Table 3-11 Mandatory Headers

    Parameter Name Value Mandatory Description
    userld ADMINUSER1 Yes User Id of the requesting user.
    appld CRTASK 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-12 Parameters

    Parameter Name Value Mandatory Description
    runDate 01102023 Yes It must be in ddmmyyyy format.
    branchCode DMO Yes Branch code.
    userId ADMINUSER1 Yes The user running the batch.
    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:
    1. This batch will move the status of the tasks based on the rules defined.
    2. New Tasks will be opened based on the wait period, dependencies and so on.
    3. Tasks will be escalated or marked as expired based on the periods specified.

    Job Name: obcr-task-operation

    Dependent Batch/Job: obcr-task-init

    Multi-threaded: Yes

    Multi-stream: Yes

    Table 3-13 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-14 Parameters

    Parameter Name Value Mandatory Description
    runDate 01102023 Yes It must be in ddmmyyyy format.
    branchCode DMO Yes Branch code.
    userId ADMINUSER1 Yes The user running the batch.
    overrideDate 2023-10-01 No It must be in yyyy-mm-dd format. It is required to run the batch for a specific day.

Success/Failure Details:

User can verify the record level status in DM_TASK_WRKFLW_OPERATN_DRIVR and DM_ACCOUNT_STRATEGY table in CR_TASK schema. For a successful processing of a record, the below condition should be satisfied.

ERROR_CODE = ‘Success’ and PROCESS_RESULT = ‘1’