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.
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 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 Test to test the connection to your account.
- Click Next to provide the configuration details.
Provide the configuration details of your account.
Field Name
Description
Folder Location Folder location from where to pick files. Process all the existing records/files To process all the existing files from the specified location. Process duplicate files This option appears only for FTP application. Selecting this option will process any new file that has the same name as the file that has already been processed. This option process the duplicate files as per the retain time defined in the event metadata property. Delete file on success Delete the file once it is processed. File type File format to process the files. Multiple file formats are separated by a comma. Use *.* to process all file formats. Trigger Type You can set trigger through POLLING and CRON EXPRESSION.
POLLING: The time interval during which the Transaction triggers. By default, Transaction triggers after every 10 minutes. Select No polling option to trigger Transaction manually.
CRON EXPRESSION: Define the specific time schedule for the Transaction to trigger. For more information on how to define Cron Expression, click here.
- It is mandatory to define the first cron expression, if you have selected cron as a Trigger type. For example, if you have set a FTP Event to run every 5 minutes from Monday to Sunday, you can set the cron expression as "0 0/5 * ? * MON, TUE, WED, THU, FRI, SAT * ".
- You may make use of the second cron expression to define another condition or address a condition supplementary to the first one. For example, if you have set a FTP Event to run every 5 minutes from Monday to Sunday, but do not want the same event to run from 12 AM to 12 PM on Sundays, the second cron expression can be defined as "0 0/5 13-23? * SUN * ".
- The firing schedule you define in the second cron expression must not overlap the one defined in the first cron expression.
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.
Only filterable custom fields will be displayed in the "Field Name" field while specifying filter criteria.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.
You can choose from the following applications only - Database, Email, FTP, File, JMS, and Spazio MFT/s.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.