Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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:

  1. 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.



  2. Click Continue.

  3. Select the partner for whom you are creating this Transaction. All the Partners of the Network(s) will be populated in the drop-down list.



  4. Click Next.

  5. Enter the following details to configure the Transaction Settings.

    Field NameDescription

    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 FormatThis 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.
  6. Click Next to define the Source application account. 

  7. 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 Appendix C: Supported Applications

     

    Click Test to test the connection to your account.

  8. Click Next to provide the configuration details.
  9. Provide the configuration details of your account.



    Field Name

    Description

    Folder LocationFolder location from where to pick files.
    Process all the existing records/filesTo process all the existing files from the specified location.
    Process duplicate filesThis 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 successDelete the file once it is processed.
    File typeFile 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.

    The Source application account and configuration details screen differ depending on the Source application chosen in the Template you are using.
  10. 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.

  11. 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.   

  12. Click Next to define filter criteria. This screen appears if the Template is created using an app-based application.
  13. 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'
  14. Click Add Filter.

  15. 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" drop-down list while specifying filter criteria.
  16. 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.
  17. 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.

  18. Depending on the option chosen in the Template you are using, you need to define all the steps. 

  19. Click Next to define the mapping. This screen appears only if the Partner needs to define the mapping

  20. Click Save & Exit to save the Transaction.

    This creates an Inbound Transaction.

  • No labels