Process Flow Guidelines

A Process Flow for your Custom Template must follow these guidelines:

You should create a Process Flow as per your requirement and publish it as a Template. However, the activities used in the Process Flow act only as placeholders that will be configured while creating a Template.
You can't use an activity twice in a Process Flow. For example, you can not use the same schema for both Source and Destination applications.
If the Process Flow has multiple sources, you must set one of the sources' eventContextEnable property to True. This source will work as a trigger in the Template. You must set this property to true only for one source, setting this for more than one source will cause an error while defining activities in the Template.
In case, there is a Database at Source or Target end, you must apply a condition in the Process Flow to skip the schema activity. This is because Database schema is bundled with source or target whichever is applicable.

For skipping source/target schema, you need to set the below code in the Java condition:
```
return "database".equals((String)context.get(<<SOURCE/TARGET ACTIVITYNAME>>));
```
where,
<SOURCE/TARGET ACTIVITYNAME> is the name of the Source or Target activity defined in the process flow. The name should be in double quotes (" ") here.
For example,
```
return "database".equals((String)context.get("FileSource"));
```
Click here to know how to set the code in the condition.
In a condition based process flow, a stream selector receives outputs from multiple services but directs only one eligible output to the next service. In the process flow design being discussed here, the StreamSelectorService can receive outputs from both Source and Source Layout and send the last received output to the mapping service DM_XML_TO_POS. To understand more about a Stream Selector, refer to Using Stream Selector page.
A Gateway in a process flow is where you define a condition to be satisfied before an output can proceed to the next stage. Based on a set of conditions, the Gateway decides and directs the output from the previous service to the next stage in the process flow. In the event of having a database at the source or the target in the process flow, it can cater to the need for bypassing the layout service based on the defined set of conditions.
For a SOAP Consumer Web Service, you must include only the Web Service activity in the Process Flow. You can not drop any other activity as a placeholder for the Web Services in the Custom Process Flow.
If a SOAP Consumer Web Service is used either at Source or Destination then the corresponding mapping activity must have respective Web Service activity loaded in the mapper.
There can be only one custom based routing activity in a process flow.
A process flow must use pre-bundled custom based routing activity (Routing) only.

Custom Template - Limitations

You can not configure Human Workflow activity and Custom report while creating a Custom Template. However, these activities can be used in the Process Flow for a Custom Template as a fixed step.
EDI Transactions are not supported through Custom Template. For such transactions, use EDI Template.
In case, there are multiple sources in the Process Flow then while creating the Template:
- The source set as a trigger can use any application, but for the sources other than trigger can use only following applications: File, FTP, Database, JMS, Email, and Spazio MFT/s.