Defining a Custom Outbound Source Application
- Ankit Gandhi (Unlicensed)
- Rohan Dhanwade (Deactivated)
- Akash Kumar Jaiswal (Unlicensed)
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
Select the trigger from the drop-down list and click Next.
Select the Source application account. 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 Next to add the configuration details.
Provide the configuration details of your account.
Click Next to define the Routing Criteria. This is applicable only if you have selected context based routing as a Routing Type.
Select the routing criteria based on which different data files will be sent to the Partners.
On the Routing Criteria screen:
Select the file name from the Criteria drop-down list.
Select the type of condition from the Condition drop-down list.
Enter the parameter name in the Parameter field.
Select the Ignore Case check box if you want the search to be case insensitive.
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 . For more information, refer to Layouts.
Click Next to define the subsequent source application. This screen appears only if the Process Flow is using multiple source applications.
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 of the application 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 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.
Next Step
