Replacing placeholders with dynamic or static values

Batch job templates use placeholders that can be overridden by dynamic or static values at runtime.

Placeholder values in the templates appear within the template as follows:

...
<TCRMObject>
		<PersistEntityRequestBObj>
			<EntityId><<ENTITY_ID>></EntityId>
			<EntityType><<ENTITY_TYPE>></EntityType>
			<PersistenceMode><<PersistenceMode>></PersistenceMode>
		</PersistEntityRequestBObj>
</TCRMObject>
...

In this example, <<ENTITY_ID>>, <<ENTITY_TYPE>>, and <<PersistenceMode>> are placeholders for values in the PersistEntityRequestBObj.

Placeholder values can be replaced either dynamically or statically.

Dynamic placeholder replacement

If your strategy is to dynamically replace the placeholder values for each request, then you can use either a SQL query or titled CSV file as input.

• SQL query inputs must provide an ENTITY_ID value to match the defined column names. For example:

  <SQLOverride>
  SELECT DISTINCT CURENTRECNO AS ENTITY_ID FROM 
  MPI_ENTLINK_MDMORG WHERE CURENTRECNO NOT IN (SELECT ENTITY_ID FROM 
  CONTACT WHERE PERSON_ORG_CODE = 'O' AND ENTITYLINK_ST_TP_CD = 2)
  </SQLOverride>

• Titled CSV file inputs must provide two columns named ENTITY_ID and ENTITY_TYPE as input. CSV files define the column names on the first line. For example:

  ENTITY_ID
  100000000
  100000001
  100000002

The placeholder names for dynamic values must be defined in the CDMETADATAINFOTP table. For example, a METADATA_INFO_TP_CD value of 8 in the TASKDEFINITION table corresponds to the METADATA_KEY value ENTITY_ID in the CDMETADATAINFOTP table. When the placeholders are configured this way, then the ENTITY_ID value must be provided dynamically.

Note: For more information, see Mapping input columns to request templates.

Static placeholder replacement

If your strategy is to statically replace the placeholder values for each request, then you can define the replacement value within VariableParameter tags in the job description. In the TaskCommentBObj, you can modify the CommentText’s CDATA section to define the static placeholder replacement value.

For example, you can edit the CDATA section to replace the <<ENTITY_TYPE>> placeholder with mdmorg:

<VariableParameter>ENTITY_TYPE=mdmorg</VariableParameter>

The placeholder names for static values do not need to be defined in the CDMETADATAINFOTP table.

Note: For more information, see Batch job definitions.