Evergreening batch jobs
Using the Batch Console sample application, data stewards can launch several batch jobs that are predefined in the TaskDefinition and TaskRoleAssoc tables.
| Task definition ID | Task name | Task Launch Action |
|---|---|---|
| 10 | Standardize Person Name | XML request template for the standardizeAndUpdatePersonName transaction. |
| 20 | Standardize Organization Name | XML request template for the standardizeAndUpdateOrganizationName transaction. |
| 30 | Standardize Address | XML request template for the standardizeAndUpdateAddress transaction. |
| 40 | Standardize Contact Method | XML request template for the standardizeAndUpdateContactMethod transaction. |
| 42 | Synchronize Person Records | XML request template for the synchronizeeME transaction for Person parties. |
| 43 | Synchronize Organization Records | XML request template for the synchronizeeME transaction for Organization parties. |
| 50 | Create Suspects | XML request template for the createSuspects transaction. |
| 60 | Collapse Suspects | XML request template for the collapseMultipleActiveParties transaction. |
Evergreening batch jobs must be added along with the data steward’s criteria. For example, when an address standardization task is registered in the Batch Console, a job is recorded with a single TaskCommentBObj object that holds the following XML in its CommentText attribute:
<TaskParameter>ADDRESS.ADDR_STANDARD_IND_NOT=Y</TaskParameter>
<TaskParameter>ADDRESS.OVERRIDE_IND_NOT=Y</TaskParameter>If the job is requested for addresses in Canada (country_tp_cd=31), then the following parameters are passed when creating the jobs:
<TaskParameter>ADDRESS.COUNTRY_TP_CD=31</TaskParameter>
<TaskParameter>ADDRESS.ADDR_STANDARD_IND_NOT=Y</TaskParameter>
<TaskParameter>ADDRESS.OVERRIDE_IND_NOT=Y</TaskParameter>