Release Date: 2022-06-14

We have made improvements to AS2 communication channels.

Inbound and Outbound Connections

On the Communication Channels page, we’ve added a column to represent the connection between Inbound and Outbound Communication Channels to help you understand which AS2 information you’ll need from your AS2 server and/or the Orderful AS2 server to send or receive transactions. We implemented this improvement because the AS2 protocol requires information from both the sender and receiver AS2 servers, meaning you need information from both the Inbound and Outbound Communication Channels.

Side panel improvements

We redesigned the side panel to include more information:

  • Inbound AS2 Communication Channels: The side panel describes the requirements Orderful will use to deliver transactions to your AS2 server.
  • Outbound AS2 Communication Channels: The side panel describes the requirements Orderful can support when receiving transactions from your AS2 server.

Infrastructure improvements

We made some infrastructure changes as well to Increase security and speed up delivery. Each new AS2 communication channel you create will be assigned a unique Orderful AS2 ID and AS2 certificate. Additionally, delivering transactions to new AS2 communication channels now happens synchronously. That means you’ll be informed about transaction delivery updates more quickly.

📘

These infrastructure changes only apply to AS2 communication channels you’ll create going forward. If you have been using AS2 communication channels before this release, we’ll keep delivering and receiving transactions as we have. Your existing AS2 communication channels will be identified with a V1 tag on the communication channel page.

Release Date: 2022-05-10

We have made improvements to our Transaction Status notification emails.

The Transaction Status emails now contain more information about your transaction as well as links and steps to help you troubleshoot any transaction issues.

Here is an example of one of the new emails:

922

Release Date: 2022-09-01

As part of our ongoing efforts to improve performance, stability and scalability, we are implementing API Rate Limits on September 1, 2022. Traffic has been monitored for months to ensure this will not break any existing integrations and exceptions have been grandfathered, still we recommend existing customers consider adapting their integration should they exceed limits in the future. The limits are well above our current peak traffic volumes and are meant to protect the systems from an erroneous, unexpected increase in transaction volume.

For more information, see our Best Practices page: https://docs.orderful.com/reference/best-practices#rate-limits

Release Date: 2022-03-15

We have streamlined our onboarding process for both Leaders and Followers.

Cancel Trade Requests

If you are the sender of a Trade Request, you now have the ability to cancel it. If you open a new outbound Trade Request detail panel and scroll to the bottom, you will see a button labelled "Cancel Trade Request".

Onboarding Emails

Additionally, our invitation emails have improved automation and guidance for customers who are new to Orderful.

If you are a Leader inviting Followers who are new to the Orderful platform, we will now provide them with a guided onboarding entirely from the invitation email:

1176

If you are a Follower inviting Leaders who are not on the Orderful network, we will now provide you with a more streamlined requirements gathering process:

1160

Release date: Released on 03/14/2022

Overview: Enable workflow validation on 210 transaction types.

Purpose: This new workflow validation marks 210 transactions invalid if they reference a SCAC code not matching the SCAC code of the latest related 204 transaction.

For more information see:

We have updated the behaviour of our Get Polling Resources endpoint.

The default limit value was previously 100, but has now been lowered to 30. Additionally, response size is now limited to 200 MB. This means that we will return the maximum number of transactions possible without exceeding either the specified limit or the maximum response size. The maximum value for limit remains 100.

Additionally, we have changed the sorting of the returned transactions to now be First-in, First Out (FIFO). This means that they are sorted automatically by the transaction creation date and time in ascending order, so that you will receive the oldest transactions first.

For more information see our documentation on how to use the Inbound Poller API.

Release date: 09/28/2021

Overview: The Integration Assistance page can now generate a transaction payload in X12 data format. You can then use it to build your connector by understanding the X12 transaction payload and the associated leader’s requirements.

Purpose: If you plan to send and receive transactions using X12 data format, you can select one or several relationships to generate an X12 transaction payload of the same version that respects the leader’s guidelines from the Integration Assistance page. You can then dive into the granular leader guideline requirements for each segment and element of the transaction payload.

For more information see: What is the Integration Assistance?