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.
However, depending upon the routing type you chose while defining the template list of available apps will vary:
For Content Based Routing: Box, Dropbox, Email, FTP, File, Google Drive, REST WebHook, SOAP WebHook, JMS, Database
For Context Based Routing: Box, Dropbox, Email, FTP, File, Google Drive, REST WebHook, SOAP WebHook (as context based routing needs file names, these are the applications that support file transfer).
No Routing: All apps
,

If the selected process flow has content based routing activity then for the triggered Source application, only Rest WebHook application appears. You can also test this application on your REST Client by clicking > Copy URL option after activating the Template.

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

The list of triggers differs for selected 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 for REST WebHook application only.
1. Click Apply Security Policy to apply security settings.
2. Select the security that you want to apply to the REST Webhook. The drop-down will list the security policies created in Developer's Studio. 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.
Skip the next step(s) as these steps are defined by the Partner while creating a Transaction using this Template.
Click Next to select the filter criteria. This screen appears only if you have selected a business application, for example, QuickBooks, HubSpot. Skip this step; the Partner who will use this Template will define this step.
Click Next to select the source layout and format. This screen appears only if you have selected a file application, for example, FTP, Google Drive or REST WebHook application.
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 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 Layouts.
You can also define this step by clicking Partner will define this step check box or allow your Partner to define this step. The Partner will define this step while creating a Transaction using this Template.
1. Select Auto generate layout name and description checkbox if you want to auto generate the activity name and description while creating the Transaction. You can not change the automatically generated name and description.
  
  The defined format of the auto generated name and description are explained below:
  
  Name : Layout_transactionId_sequenceId
  Description : Layout_transactionName
  
  By default, this checkbox is enabled for Create New and Select from the List or Create New policy and disabled for Default policy.
2. Select the type of access policy from the drop-down list. It helps the user to define the policy to displays the activity at the time of creating the transactions by another user of the same partner. The following policies are:
- - Default Policy : Using this policy, user can view all layouts and also can create a new layout while creating a Transaction.
  - Create New : User can only create a new layout while creating a Transaction. No layout is displayed from the drop-down list of layout field.
  - Select from the List or Create New : Using this policy, user can create a new layout or user can define a custom list of layouts which will appear at transaction end.
    
    You can select the type of schema like Text, Excel, etc. from the drop-down list of Schema Type. You can also search the schema from the Search box.
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, JMS, and Spazio MFT/s.
Repeat all the above steps to define the subsequent source application(s). You can also allow your Partner to define this step or all steps by clicking Partner will define this step check box. The Partner will define these step while creating a Transaction using this Template.
Click Next to provide the definition of other activities, if any.
Click Next. The next step differs depending on the selected process flow. If the process flow has content based routing activity then in the next step, you need to define the routing else define the Destination application.

You may be interested in...

What is new
Application architecture
Key terms
Install
Usage scenarios

Browser not supported