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.
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.
- 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 content based routing activity in a process flow.
- A process flow must use pre-bundled content 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.