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.
To select and configure the Source application of the Template:
Select the Source application and click Next.
The list of applications differs depending on the chosen routing type (Context based or Content based).Select the data format and click Next.
No (Pass Thru): Select this option to transfer the file from one application to another. This option is not applicable if you have selected Content Based routing.
Yes (Convert): Select this option to transfer the file data from one application to another. To transfer the data, you need to define the mapping between the fields of the Source and the Destination application. On selecting this option, you also need to define Who will define the mapping?.
Select I will define if you want to define the Partner's layout and mapping between the fields of the Source and the Destination application.Select Partner will define if you want your Partner to define the layout and mapping between the fields of the Source and the Destination application.
The next steps differ depending on the chosen Source application and routing type.
Select the trigger from the drop-down list and click Next.
The list of triggers differs for the chosen Source application. For the complete list of triggers of the supported applications, refer to Appendix D: Supported Applications.
Select the Source application account. You can either use an existing account or create a new one. Click
to add a new account. For information on how to add an account, refer to Appendix D: Supported Applications.
Click Test to test the connection to your account.Click Next to add the configuration details.
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 chosen Source application.Click Next to select the routing criteria. This screen appears if you have selected 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. 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. This screen appears only if you have selected Yes (Convert) option in the 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 exist, for example, text, excel. Source data layout is the layout of the source file. You can either use an existing layout or create a new one. Click
to create a new layout. For information on how to create a new layout, refer to Appendix A: File Layouts. 
Click Next to encrypt data.
Select the Is Source File encrypted? check box if the source file is in the encrypted format. The below fields appears. Provide the details in the corresponding fields.
Field Name Description Key Manager Select the Key Manager from the list. To create a Key Manager, visit Account > Security Settings. To create a Key Manager, click here. Key Name The default value is the default. Private Key Password Password of the key. Confirm Password Confirm the password of the key. Click Next. The next screen differs depending on the chosen routing type. For Context based routing, you need to select the Destination application. Whereas for Content based routing, you need to define the routing.
Next Step