ProcessID

Using the ProcessID parameter for a data set, you can specify a workflow name in the FileWatcher.xml file. This is an optional element.

For example, you can set up two different data sets, each one importing to the Customer repository. However, the import requirement for each source can be different and a different workflow is needed. In such a case, you can specify the workflow in the data set definition itself. When the FileWatcher fires a workflow, it takes the specified workflow and skips the workflow selection using business process rules.

Note: This feature supports all import modes except Database Loader because it does not use any workflow in the import operation. The supported import modes are Direct Load, Split/Approval Required, and Split/No Approval.

Example

<DataSet type="single">
   <Name>ENT2 Import</Name>
   <Credential domain="GLN">
   <Identity>0065064183212</Identity>
   </Credential>
   <Action>DataServiceUpdate</Action>
   <URIInfo scheme="local">
     <Relative>MQ_COMMON_DIR</Relative>
     <URI>fwtest/DataForImportdata</URI>
   </URIInfo>
   <ProcessID>fwtest/workflow/wfin26dataservicev2</ProcessID>
</DataSet>
Note: Even though you specify the workflow name, you have to deploy the workflow through TIBCO MDM Studio.