Defining a Custom Partner to Partner Exchange Source Application
- Saurabh Gupta (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.
Select the trigger from the drop-down list and click Next.
Click Next to apply security settings to the REST Listener. This screen appears if you have selected REST WebHook application.
Click Apply Security Policy to apply security settings.
Select the security that you want to apply to the REST Webhook. You can either select an existing security or create a new one.
Click to create a new security policy.
Select the Network of the Partner that will send the file to another Partner. Only those Partners that Company is managing are allowed to access this Template and can send a file to another Partner.
Select the Source application account. This screen appears if you have selected an application apart from REST WebHook. 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 Test to test the connection to your account.
Click Next to add the configuration details.
Provide the configuration details of your account.
The Source application account and configuration details screen differ depending on the Source application chosen in the Template.
Click Next to select the routing criteria. This screen appears for Context Based routing.
Select the routing criteria based on which different data files will be sent to the Partners.
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 .
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).
Click Next to provide the definition of other activities, if any.
Next Step