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?

Release date: September 13th, 2021

Overview: Data format versions (e.g. X12 004010) can now be set on relationships without the need for a guideline.

Purpose: Followers (trading partners that follow their trading partner's requirements) can now select their data format version without having to assign a guideline.

When going through the initial setup of a new relationship, select the data format and the version in the relationship side panel in our UI.

Release date: 07/19/2021

Overview: Users from your organization are able to see who has access to your organization and invite new users.

On the new Users page, you can see the list of users that can access your organization and their information such as their email address, name, status.

You also have the ability to invite new users to join your organization. This will send an email invite to new users that will then have to complete their sign up.

Release date: July 7th 2021

Overview: More granular statuses for relationships while going through the onboarding process. More guidance around setup to reduce back-and-forth between you and your trading partner, and/or Orderful.

Added 'autoSend' setting on relationships to configure auto-sending behavior for test and live transactions.

Purpose: More guidance and less back-and-forth to reduce time needed to onboarding new relationships.

For an overview of the statuses and over information see here: (Search Relationships)[https://orderful.zendesk.com/hc/en-us/articles/360060656434-Search-Relationships]

Release date: 06/02/2021

Overview: Sending functional acknowledgments to a communication channel is now tracked on the audit trail and is subjected to a retry system.

To make sure a delivery failure isn't related to a temporary server issue, Orderful now retries sending a functional acknowledgment to a communication channel three times:

  • 1st retry: 5 min after the initial delivery failure
  • 2nd retry: 10 min after a delivery failure on the 1st retry
  • 3rd retry: 20 min after a delivery failure on the 2nd retry

Each delivery failure or success on retries is captured on the audit trail.

📘

Orderful retries to send a transaction when the delivery failure isn't tagged as permanent.

Release date: Released on 06/21/2021 and 06/29/2021

Overview: Workflow validation ensures that transactions that belong to the same workflow share the same important business information.

Purpose: This new workflow validation prevents you from sending invalid transactions that contains incorrect and mismatching business information to your partners.

For more information see:

To launch this new validation, Orderful focuses on implementing a workflow validation on the Transportation workflow.

For more information see Workflow Requirements Enforced on Transportation Workflows

Release date: 05/10/2021

Overview: Your transactions in the UI are now shown in your specified data format (JSON or X12). Easily toggle back and forth between the data format of you or your trading partner.

Purpose: Instantly see any transaction in your or your trading partner's data format, even before it is sent. Easily see how new rules affect your transactions in either data format.

Simply toggle data format from either:

  • The Transaction Data View
  • The Rules Editor

More improvements:

  • Superior transaction page performance, both in the JSON view and X12 view – reduced page load times, and greatly improved stability even when viewing large transactions
  • Updated JSON viewer styling
  • When opening a transaction that has a validation error, automatically focus the rules editor & first error
  • Basic/Expanded View replaced with more intuitive "Show empty fields" experience
    Additional fixes:
  • Fixed: Errors appear in the wrong place when a transaction’s structure has changed
  • Fixed: Scroll-to-path doesn’t work when the selected path is in a collapsed array
  • Fixed: Scroll-to-path doesn’t work when the path is an empty field, but "Show empty fields" is disabled
  • Fixed: Scroll-to-path doesn’t work when the path is in a paginated array, but a different index is currently selected

Release date: 05/04/2021

Overview: Scenario checklist steps are now automatically completed when linked transactions are accepted by the receiver.

Purpose: Speeding up testing by automating manual tasks. For more information about our scenario testing feature, please refer to our documentation: