After you have provided the definition of the Template, the next step while creating a Template is to define the Source application. A Source application is an application from where data is received. After defining the Source application, you must choose a Trigger.

A Trigger is an event that initiates the data exchange. For example, in an FTP Source application, if you choose On File Created as a trigger, then data exchange will initiate when the new file is created to the source FTP.

You need to define and configure all the source applications if the Process Flow has multiple source activities. Following are the steps to define and configure the Source application. Follow the same steps to configure other source applications.

To select and configure the Source application of the Template:

Select the Source application and click Next.

If you are using REST WebHook application then you can also test this application on your REST Client by clicking > Copy URL option after activating the Template.

The list of applications differs depending on the routing type (Context based or Content based).

The next steps differ depending on the chosen Source application.
Select the trigger from the drop-down list and click Next.

The list of triggers differs for chosen Source application. For the complete list of triggers of the supported applications, refer to Appendix C: Supported Applications.
Click Next to apply security settings to the REST Listener. This screen appears if you have selected REST WebHook application.
1. Click Apply Security Policy to apply security settings.
2. Select the security that you want to apply to the REST Webhook. You can either select an existing security or create a new one.
3. Click to create a new security policy.
  
  Option Name Description
  Name Name of the security policy.
  Authentication Type Default is Basic.
  User ID A unique username to authenticate a user.
  Password Password to authorize a user.
Select the Network of the Partner that will send the file to another Partner. Only those Partners that Company is managing are allowed to access this Template and can send a file to another Partner.

This screen appears only for the triggered Source application.
Select the Source application account. This screen appears if you have selected an application apart from REST WebHook. You can either use an existing an account or create a new one. Click to add a new account. For information on how to add an account, refer to Appendix C: Supported Applications.

Click Test to test the connection to your account.
Click Next to add the configuration details.

Option Name	Description
Name	Name of the security policy.
Authentication Type	Default is Basic.
User ID	A unique username to authenticate a user.
Password	Password to authorize a user.

Provide the configuration details of your account.

Field Name	Description
Folder Location	Folder location from where to pick files.
Process all the existing records/files	To process all the existing files from the specified location.
Process duplicate files	This option appears only for FTP application. Selecting this option will process any new file that has the same name as the file that has already been processed. This option process the duplicate files as per the retain time defined in the event metadata property.
Delete file on success	Delete the file once it is processed.
File type	File format to process the files. Multiple file formats are separated by a comma. Use . to process all file formats.
Trigger Type	You can set trigger through POLLING and CRON EXPRESSION. POLLING: The time interval during which the Transaction triggers. By default, Transaction triggers after every 10 minutes. Select No polling option to trigger Transaction manually. CRON EXPRESSION: Define the specific time schedule for the Transaction to trigger. For more information on how to define Cron Expression, click here.

The Source application account and configuration details screen differ depending on the Source application chosen in the Template.

Click Next to select the routing criteria. This screen appears for Context Based routing.

Select the routing criteria based on which different data files will be sent to the Partners.

Criteria	Condition	Parameter
Currently, only File Name is supported.	A condition to filter the files. Equals: Select this option to allow your Partner to provide the exact file name with its extension. Contains: Select this option to allow your Partner to provide any part of the file name.	A variable name for the specified condition.

Criteria

Condition

Parameter

Currently, only File Name is supported.

A condition to filter the files.

Equals: Select this option to allow your Partner to provide the exact file name with its extension.

Contains: Select this option to allow your Partner to provide any part of the file name.

A variable name for the specified condition.

For example, here in the example, cust_id is specified as a variable name. The Partner needs to specify the value for the variable name (cust_id) at the time of creating a Transaction. Suppose, the value specified is CUST147. When the Transaction will execute, it will fetch all the records containing CUST147 such as CUST14789.txt, CUST1478.xls, CUST147.docx.

If you have specified Equals in the Condition drop-down list then Transaction will fetch all the records containing CUST147 only such as CUST147.txt, CUST147.docx.

Click Next to select the source data format.
Select the source data format and source data layout for the Source application. Source data format is the format in which the data of the source file exists, for example, text, excel. Source data layout is the layout of the source file. You can either use the existing layout or create a new layout. To create a new layout, click .
Click Next to define the subsequent source application. This screen appears only if the Process Flow is using multiple source applications.

You can choose from the following applications only - Database, Email, FTP, File, and JMS.
Repeat all the above steps to define the subsequent source application(s).
Click Next to provide the definition of other activities, if any.

Browser not supported