Creating an Inbound Custom Transaction
A Transaction is created by using a Template. Therefore, before creating a Transaction, ensure that you have created a Template.
To create an Inbound Transaction:
Provide the name and description of the Transaction. The name and description of the Transaction are generated automatically based on the selected Template. You can edit the Transaction name and description that can be up to 48 and 300 characters long.
Click Continue.
Select the partner for whom you are creating this Transaction. All the Partners of the Network(s) will be populated in the field.
Click Next to go to Transaction Settings step.
On the Transaction Settings screen, do the followings:
Enter the details as described in the following table.
Expand Advanced Settings to set the Logging Level, Repository File Retention, and Activity Logging Retention. The available options for the fields are as follows:
Logging Level- INFO, DEBUG, and ERROR
Repository File Retention- DONT DELETE, DELETE, DELETE ON SUCCESS, and DELETE ON SUCCESS EXCEPT SOURCE DATA
Activity Logging Retention- DONT DELETE, DELETE ON SUCCESS, and NO LOGGING
To learn more about these options, refer to this page.
The three fields (Logging Level, Repository File Retention, and Activity Logging Retention) appear on this screen only when the Template you are using is created by setting Routing Type to None. When you use a Template with Routing Type selected as either Content Based or Context Based, only the Repository File Retention field appears on the screen.If you hide the Transaction Settings page using Select the steps which you want to hide at the time of Transaction creation option from the Settings screen while creating a Template, by default the following values will be set for the fields in a Transaction:
When using a Template with Routing Type as None:
Logging Level : ERROR
Repository File Retention : DELETE ON SUCCESS EXCEPT SOURCE DATA
Activities Logging Retention : DONT DELETE
When using a Template with Routing Type as Content or Context Based:
Repository File Retention : DELETE ON SUCCESS EXCEPT SOURCE DATA
Click Next to define the Source application account.
Select the Source application account. You can either use an existing account or create a new one. For information on how to add a new account, refer to Supported Applications.
Click Next to provide the configuration details.
Provide the configuration details of your account.
Click Next to select the source data format. This screen appears if the Template is created for the Partner to define the layout using a file-based 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 Next to define filter criteria. This screen appears if the Template is created using an app-based application.
This screen allows you to retrieve only specific records using AND/OR filters. For example, name=John and Id=12345 will retrieve only the record where name is 'John' and Id is '12345'.
Click Add Filter.
Select the field name, condition, and value to filter the records. Depending upon the application used in a Template, you can filter the records using AND, OR, or both AND and OR filters. Click AND Filter to add more records.
Click Next to define the next Source application details. This screen appears if the Process Flow used in the Template is using multiple source applications and Partner needs to define the application details.
Select the application and repeat the Steps 6 to 11 to define the application details. The steps may differ depending on the option chosen in the Template.
Depending on the option chosen in the Template you are using, you need to define all the steps.
Click Next to define the mapping. This screen appears only if the Partner needs to define the mapping.
Click Save & Exit to save the Transaction.
This creates an Inbound Transaction.