We've made improvements to the Orderful Welcome Page.

If you’re new to Orderful and haven’t gone live with your first Partnership, your Welcome Page will now highlight where you are in the Orderful onboarding and configuration process.

Relationships that trade using the JSON format can now choose to send acknowledgments. Previously acknowledgments were only available for Transactions in X12 format.

You can also now send and retrieve Transaction acknowledgments using our API. More information can be found in our API reference:

We have released native support for internal code lists from the ANSI X12 specification. Going forward, when entering an X12 guideline, you will be able to select an element's "Allowed Values" from a predefined list.

Leaders can now resend the Orderful invite email to a partner from the side panel of a Pending Trade Request.

New organizations in Orderful will have a Welcome Page guiding users through the onboarding of their first partnership.

The onboarding steps displayed will be different for:

  • A new Orderful customer starting as a Leader
  • A new Orderful customer starting as a Follower
  • A Follower invited by a Leader using Orderful

Existing customers that have already onboarded at least one partner won’t see the Welcome Page.

Starting Monday April 17th, Orderful will batch Transaction Status Updates in one email every 15 minutes.

If you are subscribed to any Transaction Status Updates, we will send you up to one email every 15 minutes, detailing any issues and next steps.

Orderful has improved delivery logging and tracking for acknowledgments.

Acknowledgment delivery updates are now available on the audit trail of the transactions related to the acknowledgment.

We have removed the "Direction" of Guidelines. Guidelines can now be assigned to both outbound and inbound Relationships. This means that Organizations that both send and receive transactions of the same type no longer have to manage duplicate Guidelines.

We have added a "Delete" function the Rules Engine. It can be used to remove any whole part of an EDI document. For X12 documents you can remove a loop, segment, or element. For JSON documents you can remove a property or object.

For an example usage, please see our documentation on how to Use the Rules Engine.