Persistence batch jobs
The Batch Activity Dashboard application can execute added persistence batch jobs that are predefined in the TaskDefinition and TaskRoleAssoc tables.
For more information about persisting entities with the Batch Activity Dashboard application, see the link at the end of this topic.
| Task definition ID | Task name | Task Launch Action |
|---|---|---|
| 80 | Persist Entities (multiple entity types) | XML request template for the persistEntity transaction. Use this task definition ID if you are providing both the entity_id and the entity_type in the CSV file or SQL statement. This task applies best to cases in which you want to load organization data and person data together simultaneously, or in cases where you already provide the entity_id and the entity_type in order to generate the CSV file or SQL statement. In order to override the link-only status, you can also specify PersistenceMode within the task definition comment by setting the value of the VariableParameter tag. See the discussion of PersistenceMode following this table. |
| 90 | Persist Entities (single entity type) | XML request template for the persistEntity transaction. Use this task definition ID if you are persisting data that is all of a single entity_type. This allows you not to specify the entity_type for all records in the CSV file or SQL statement. Instead, within the task definition comment, set the value of the VariableParameter tag in order to specify entity_type. Also within the task definition comment, you can override the link-only status by specifying a value for PersistenceMode. See the discussion of PersistenceMode following this table. |
Batch jobs for persistence must be added along with a CSV file or SQL. For example, when the Persist Entities (multiple entity types) activity is added in Batch Console, a job is recorded with a single TaskCommentBObj object that holds the CSV file or SQL to provide to the persistence data resource. For hybrid MDM, the Register Virtual Entities for Physical MDM job generates CSV files that you can provide to the batch job.
If you do not specify the PersistenceMode parameter, each entity is updated according to its original persistence status. When started, the persistEntity transaction determines whether the entity was already persisted. If it was persisted, the transaction determines how it was persisted originally. If the entity was persisted in entity registration mode, persistEntity updates only the limited number of attributes used to register entities. If the entity was originally persisted with all attributes, persistEntity updates any attributes that have changed in the composite view of virtual MDM.
Alternatively, if you specify the PersistenceMode parameter with a value of 2 when invoking persistEntity to do updates, the transaction overrides the status of any entities that were originally persisted in entity registration mode. In other words, setting PersistenceMode to 2 causes the persistEntity to persist all attributes of the entities regardless of how they were persisted originally. If they were persisted in entity registration mode, the update transaction updates the status to indicate a fully persisted view and proceeds to persist all current attributes of the entity from the composite view of virtual MDM.