Configuring Change Logs for Multiple Entities

You can configure the CustomerChangeLog pre-configured batch to execute a change log for different entities in the same batch.

By default, the CustomerChangeLog pre-configured batch has a populateCustomerChangeLog task with STG_PARTY_MASTER as the $CHGTBLNM$ parameter value. To execute a change log for different entities in the same batch, follow these steps:

1. Navigate to the Scheduler Services.
2. In the Scheduler Service, navigate to Define Task.
3. Select CustomerChangeLog from the Batch drop-down list.
4. Copy the populateCustomerChangeLog task and rename the Task Name and Task Code.
5. Edit the $CHGTBLNM$ parameter value for any entity other than STG_PARTY_MASTER and click Save.
   • The parameter value for country of residence is FCC_STG_PARTY_ADDRESS_VW.
   • The parameter value for source of wealth is FCC_STG_PARTY_DETAILS_VW.

     Note:

     Each new entity of the change log must have one new task copied and edited.
6. Edit the precedence for the newly created tasks. The tasks should follow one after the other. In the end, the endDataPipeline task should have the preceding task as the nth populateCustomerChangeLog task.

If the CustomerChangeLog batch has three populateCustxomerChangeLog tasks, then the task precedence should be set as:

1. The populateCustomerChangeLog task should be marked as the preceding task for populateCustomerChangeLog2.
2. The populateCustomerChangeLog2 task should be set as the preceding task for populateCustomerChangeLog3.
3. The populateCustomerChangeLog3 task should be the preceding task for endDataPipeline task.

This allows all the populateCustomerChangeLog tasks to be captured in one execution of the CustomerChangeLog Batch.

Note:

You can also run the CustomerChangeLog batch once per stage entity. To do this, set the task parameter value of populateCustomerChangeLog, such as, $CHGTBLNM$, accordingly and trigger the batch. Once that execution is complete, the same process can be repeated for other stage entities.