After you have selected the Source application, the next step while creating a Template is to define the Destination application. A Destination Application is an application from where data is to be transferred from the Source application. After defining the Destination application, you must choose an Action.
An Action is performed at the destination. For example, in an FTP Destination application, if you choose Create File as an action, then a file will be generated at the destination.
You need to define and configure all the destination applications if the Process Flow has multiple target activities. Following are the steps to define and configure the Destination application. Follow the same steps to configure other destination applications.
To select and configure the Destination application of the Template:
Select the application and click Next.
Select the action and click Next.
The list of actions differs for the selected Destination application. For the complete list of actions of the supported applications, refer to Appendix C: Supported Applications.Select the Network of the Partner who is receiving data from the Partner. Only Partners of the selected Network are allowed to access this Template and can receive a file.
This screen appears only for the triggered Destination application.Select the checkbox Allow Import Partner(s) which allow you to select a Web Form to import Partners while configuring the Transaction.
- Click Next.
Uncheck the Partner will define this step (if checked) checkbox and then select the Destination application account. You can click Test to test the connection to your account.
You can either use an existing account or create a new one. Click
to add a new account.You can also allow the Partner to define this step by clicking Partner will define this step check box. The Partner will define this step while Creating a Transaction using this Template.
Click Next to add the configuration details. This screen appears only for FTP application.
Provide the configuration details of your account.
You can define the folder location using Partner parameters in the following format:
$$Partner.{PartnerParameterName}$$
where,
PartnerParameterName is the name of the parameter that you have configured for the Partner.
Ensure that you have configured the specified parameter for the Partner for which you are creating this Template.
Click Next to select the target data format.
Select the target data format and data layout for the Destination application. Target data format is the format in which you want the destination file, for example, text, excel. Target data layout is the layout of the destination file. You can either use an existing layout or create a new one. Click
to create a new layout. 
You can also allow the Partner to define this step by clicking Partner will define this step check box. The Partner will define this step while creating a Transaction using this Template.Once you select this option, you need to follow the steps given below:
Select Auto generate layout name and description check box 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_transactionNameBy default, this checkbox is enabled for Create New and Select from the List or Create New policy and disabled for Default policy.- 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 destination application. This screen appears only if the Process Flow is using multiple destination applications.
- Repeat the above steps to define the subsequent destination application(s).
Click Next to provide the definition of other activities, if any.
The next screen differs depending on the routing type. For Context based routing, you need to select the mapping. Whereas for Content based routing, you need to define the routing.