Defining a Custom Inbound Destination Application

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:

1. Select the Destination application and click Next. 

   

   The next steps differ depending on the selected Destination application.

2. 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.

3. 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.

   
   
   

4. Click Next to define the configuration details.

5. Provide the configuration details of the selected Destination application.  

   The Destination application account and configuration details screen differ depending on the Destination application selected in the Template.
6. Click Next to select the target data format. This screen appears only if you have selected a file-based application at the Destination. 

7. 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: 

   1. 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_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 in the Access Policy field. 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.
     • 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. in the Schema Type. You can also search the schema from the Search box.
       
       

8. Click Next to define the subsequent destination application. This screen appears only if the Process Flow is using multiple destination applications. 

9. Repeat all the above steps to define the subsequent destination application(s). You can also allow your Partner to define this step or all the steps by clicking Partner will define this step check box. The Partner will define the steps while creating a Transaction using this Template.
   
   
   
   
10. Click Next to provide the definition of other activities, if any. 
    
    

Next Step

Defining the mapping