Creating an Outbound Convert Transaction
- Akash Kumar Jaiswal (Unlicensed)
- Shruti Pasayat
- Rohan Dhanwade (Deactivated)
A Transaction is created by using a Template. Therefore, before creating a Transaction, ensure that you have created a Template.
To create an Outbound Transaction:
- Click Transactions > Templates.
On the Templates screen, navigate to the Template you wan to use and click
.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 Network from the Select Network field. The availability of this field is driven by the following conditions.
This field is not available:
When the selected Template has only one Network.
- When the selected Template has more than one Network but the user has access to only one Network.
- This field is available:
- When the selected Template has multiple Networks and the user has access to more than one Network.
Select the partner for whom you are creating this Transaction. All the Partners of the Network(s) to which this Template belongs will be populated in the field.
Click Next to define the value of the parameter. This screen appears only if the Template you are using is created using Context Based routing type.
Provide the value of the parameter corresponding to the variable name.
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.
Field Name Description Contact User
Email id(s) listed here will receive a notification email whenever the Transaction is executed successfully or if there is an error during execution. Multiple email ids are separated by comma.
If Adeptia Connect is running on multiple environments and you want to receive environment name in the emails, then you need to specify the environment name in the relevant property (Account > Settings > Server Nodes Settings > Systems > Personalization).
When to notify the contact user thru email? Always: Send an email whenever a Transaction executes.
On Error: Send an email if an error occurred during the execution of the Transaction.
Do Not Notify: Select this option if you do not want to receive an email notification for Transaction execution.
Email Notification Format This field is visible only when you have selected Always or On Error option to send the notification to the user.
Select the email notification format that you want to use for notification emails sent to the user for successful and failed transaction.
Default: If you select Default, the system will use the default email notification format.
Customized Notification Format: If you select this option, a Custom Error Notification Format field appears. In this field, you can select an existing custom email notification format or create a new one, and use it for email notifications.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. To learn more about these options, refer to this page.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. The Source definition steps appear only when the Template that you are using is created for the Partner to define the Source.
Click Next to define the Destination application account. This screen appears if the Template you are using is created for the Partner to define the account details.
Select the account in the Provide account information field. You can either use an existing account or create a new one. Click to add a new account. For more information on how to add an account, refer to Supported Applications.
Click Test to test the connection to your account.
- Click Next to provide the configuration details.
After providing the configuration details, click Next to open Target layout screen. This screen appears only if the Template you are using is created for the Partner to define the layout.
The Destination application account and configuration details screen differ depending on the Destination application chosen in the Template you are using.- On the Define Layout screen, Select the format and layout. You can either use an existing layout or create a new one.
Click Next to encrypt data.
Select the Want to encrypt target file? check box to encrypt the destination file. The below fields appears. Provide the details in the corresponding fields.
Field Name Description Key Manager Select the Key Manager from the list. To create a Key Manager, visit Account > Security Settings. To create a Key Manager, click here. Key Name The default value is the default. Click Next to define the mapping. This screen appears only if the Template you are using is created for the Partner to define the mapping.
Click Save & Exit to save the Transaction.
This creates an Outbound Transaction.