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:

Click Transactions > Templates.
On the Templates screen, navigate to the Template you want 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.

In a transaction with context based routing, Adeptia Connect validates if the "Contains" criteria is already used in other transactions to prevent creation of duplicate transactions.
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 drop-down list.
1. You can click to add a new Partner. Add Partner window will open.
2. You can import the Partner through WebForm by clicking Import Partners icon. This option will work only if you have selected Allow Import Partner(s) checkbox while creating a Template.
Click Next.

Enter the following details to configure the Transaction Settings.

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 > Expand Application Settings > Common > Expand 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.

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 > Expand Application Settings > Common > Expand 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.

Click Next to define the parameter values. This screen appears only if the Template you are using is created to get the values from the Partner or Company user.
Provide the values in the fields.
Click Next to define the Source application account. This screen appears if the Template you are using is created for the Partner to define the account details.
Select the Source application account. You can either use an existing account or create a new one. Click to add a new account. For information on how to add a new account, refer to Appendix C: 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 when this transaction is turned on	To process all the existing files from the specified location.
Don't process duplicate files	This option appears only for FTP application. Selecting this option will not process any new file that has the same name as the file that has already been processed. This option does not process the duplicate files as per the retain time defined in the event metadata property.
Send mail notification for no data on trigger	Selecting this option will check the data and send mail notification to the Partner for no data on trigger.
Send mail notification for error on trigger	Selecting this option will check the data and send mail notification to the Partner for error in data on trigger.
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.
File exclude	Type the file format to exclude the file type while transaction is running. Multiple file formats are separated by a comma. For example if you want to exclude text files from the FTP location, type .txt in the text box.
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.
File Stable Time	You can set file stable time in the text box and select time unit from the drop-down list. This option is applicable for On File Created and On File Modified Trigger Type. The trigger will wait for the specified time for the file to become stable. For example, if you choose 30 Seconds in the stable time then system will wait for 30 seconds for the file to go stable before it triggers the transaction.

The Source application account and configuration details screen differ depending on the Source application chosen in the Template you are using.

Expand Other Settings and provides the detail.

Select Trigger in Sequence check box to trigger the Transaction in sequential manner. If you do not select the Trigger in Sequence check box then the associated Transaction will trigger concurrently.

If you want to enable misfire handling for your file event then, select the Run Once option from the Action on Misfire Event drop-down list. If you do not wish to enable misfire handling for your file event then, select the Ignore Misfire option. For more details, refer to Handling Misfire Event.

The Run Once option will run only one collective instance of all the misfires for a particular event. Whereas the Ignore Misfire option will not run a misfired event.

The default value for Action on Misfire Event field is set to Run Once for all of the earlier events.
The Connector drop-down lists the APIs to connect to the FTP Server. The options changes as per your selection of the protocols that you want to use to establish FTP connection.
Protocol
Options
FTP
Native
Secured Inet Factory
SFTP
J2SCH (VFS)
Secured Inet Factory
J2SSH
FTPS
J2SCH (VFS)
Secured Inet Factory
Select Verbose check box, if you want to create a log file of your FTP activity. This check box is enabled only if you select Secure Inet Factory from the Connector drop-down list box.
Click Next to select the source data format. This screen appears if the Template you are using is created using a file-based application for the Partner to define the layout.
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 exist, 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 to create a new layout.
Click Next to encrypt data.

Protocol	Options
FTP	Native Secured Inet Factory
SFTP	J2SCH (VFS) Secured Inet Factory J2SSH
FTPS	J2SCH (VFS) Secured Inet Factory

Select the Is Source File encrypted? check box if the source file is in the encrypted format. 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.
Private Key Password	Password of the key.
Confirm Password	Confirm the password of the key.

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 Inbound Transaction.

Browser not supported