When creating or editing an AS2 Communication Channel, you can now configure advanced settings:

• Authentication: You can choose Basic Authentication and provide Orderful a username and password to use when delivering messages to your AS2 server.
• Encryption algorithm: Encryption algorithm Orderful must use when delivering AS2 messages to your AS2 server: 3DES (Default), AES128, AES192, or AES256.
• Encryption encoding: Encoding Orderful must use when delivering or receiving messages to and from your AS2 server: Base64 or Binary.
• Signature algorithm: Signature algorithm Orderful must use when delivering messages to your AS2 server: SHA-1, SHA-256 (Default), SHA-384, or SHA-512.
• Orderful AS2 ID and certificate: Which Orderful AS2 ID and certificate Orderful must provide for a specific Communication Channel. You can choose:
  • Generic AS2 ID (ORDERFULAS2) with a self-signed certificate.
  • Custom AS2 ID with a self-signed certificate.

We’ve added Inbound and Outbound Self-hosted SFTP Communication Channels to the Communication Channels page.

From the Communication Channels page, you now can create:

• Orderful-hosted SFTP: Orderful creates, hosts and manages the SFTP server.
• Self-hosted FTP/SFTP: You create, host and manage the SFTP server.

Currently Self-hosted SFTP Communication Channels have the following restrictions:

• Only X12 data can be sent and received.
• Username and password is the only available authentication method.
• For FTP protocol, only passive mode is supported.
• Orderful deletes files after downloading them. Archiving files after downloading them will be available soon.

If you want to create a Self-hosted FTP/SFTP Communication Channel without one of these restrictions, you’ll need to contact our support team.

For instructions on how to set-up an Inbound Self-hosted SFTP Communication Channel see here: https://docs.orderful.com/docs/set-up-org-follower#inbound-ftp-and-sftp

For instructions on how to set-up an Outbound Self-hosted SFTP Communication Channel see here: https://docs.orderful.com/docs/set-up-org-follower#outbound-ftpsftp

Orderful is now generating Functional Acknowledgements per Functional Group based on the acknowledgment status of each Transaction. This change allows us to better handle some rare edge cases:

1. If a Transaction Set cannot be created by Orderful, a Functional Acknowledgement will not be sent.
2. If a Transaction Set can be created, but can’t be passed from the Sender to the Receiver Organization (for example because it is invalid or hasn’t been auto-sent), a Functional Acknowledgement will not be sent.
3. If the receiver returns a Functional Acknowledgment, Orderful will now return a Functional Acknowledgment for each Functional Group, with the Functional Acknowledgement containing the acknowledgment status for each Transaction Set.

Customers who use the X12 format, or have a Trading Partner who uses it, can now filter Transactions by Reference Identifiers. Currently the only supported Reference Identifiers are:

• Interchange Control Number
• Functional Group Control Number
• Transaction Set Control Number

You can access these filters in 3 different ways:

1. The Transactions page now contains columns for each of these numbers.
2. Additionally, if you click on Filters icon you will see the new "Reference Identifiers" filters at the bottom of the Filters dialogue:

3. The List Transactions API has also been updated with the following query parameters:

• referenceIdentifier
• senderInterchangeReferenceIdentifier
• senderGroupReferenceIdentifiersender
• transactionReferenceIdentifier
• receiverInterchangeReferenceIdentifier
• receiverGroupReferenceIdentifier
• receiverTransactionReferenceIdentifier

The referenceIdentifier has been added to our JSON Transaction payload:

"referenceIdentifiers": [
  {
    "value": "000000352",
    "type": "INTERCHANGE",
    "owner": "RECEIVER"
  },
  {
    "value": "352",
    "type": "GROUP",
    "owner": "RECEIVER"
  },
  {
    "value": "0001",
    "type": "TRANSACTION",
    "owner": "RECEIVER"
  }
]

We have made improvements to X12 file uploads from the Transactions page:

1. The file size limit has been increased from 1 MB to 12 MB.
2. A success message will appear in the bottom left of the page, with a link to the processing details for your file. For example, if you uploaded an EDI file containing multiple Transactions, Orderful will list the different Transactions from this file and their creation status.

We’ve added inbound and outbound Orderful-hosted SFTP Communication Channels to the Communication Channels page.

For now, only Orderful-hosted SFTP can be created. That means Orderful is creating, hosting and managing the SFTP server.

Currently Orderful-hosted SFTP Communication Channels have the following restrictions:

• Only X12 data can be sent and received
• Username and password is the only available authentication method
• Only the SFTP protocol is supported.

After you create an SFTP communication channel, the SFTP server configuration details, credentials, upload and download requirements are automatically generated and available through Orderful.

For instructions on how to set-up an inbound Orderful-hosted SFTP Communication Channel see here: https://docs.orderful.com/docs/set-up-org-follower#inbound-ftp-and-sftp

For instructions on how to set-up an outbound Orderful-hosted SFTP Communication Channel see here: https://docs.orderful.com/docs/set-up-org-follower#outbound-ftpsftp

If you want to create a self-hosted FTP/SFTP Communication Channel, you’ll still need to contact our support team.

We have made infrastructure changes to our AS2 backend that should result in your transaction delivery updates arriving more quickly.

We also added support for an Orderful CA certificate: For Trading Partners who require them, Orderful can now provide CA certificates for AS2 Communication Channels. If you'd like to enable this, please contact [email protected].

Finally, Orderful will now send a positive MDN even if we can’t create an EDI job. This means that you will no longer receive the "Unexpected Processing Error" Outbound MDN error. This error has been removed from our AS2 Troubleshooting page.

We have added a new API endpoint that retrieves a list of transactions: GET /transactions/.

Additionally, the Transaction object has been updated, with more information in the sender and receiver objects. Both objects now include:

• name
• isaId
• isaIdQualifier
• testIsaId
• testIsaIdQualifier

To read the updated documentation, see the List Transactions page.

Previously, Orderful would only accept AS2 messages sent over HTTPS. We now also accept AS2 messages sent over HTTP to http://as2.orderful.com as long as the AS2 message is encrypted with an Orderful AS2 certificate.

We made some infrastructure changes to speed up delivery for VAN Communication Channels. Transactions to new VAN communication channels are now delivered synchronously. This means you’ll be informed about transaction delivery updates more quickly.