We have refreshed our Transactions page UI and updated our Filtering options:

• In addition to filtering by date, you can now also filter by time (HH:MM:SS AM/PM).
• You can now select multiple options in all dropdown menus, as well as Select all.
• The following filtering properties have been removed:
  • Trading Partner
  • Hide Trading Partners
  • Owner ISA IDs
• The following filtering properties have been added:
  • Your EDI Account: Select one or more EDI Accounts that you have configured for your Organization.
  • Partner EDI Account: Select one or more EDI Accounts that belong to your Trading Partners.

To hide specific Trading Partners, you can select all Partner EDI Accounts, and then unselect the Partner EDI Accounts you'd like to hide.

To access the new Filtering options, click on Filter at the upper left of your Transactions list.

We have improved the popular LOOKUP function of our Rules Editor. LOOKUPV2() can now be used to not only look up single element values, but also to look up entire segments and loops - all in one go.

This is especially helpful when using the Rules Editor to move loops and segments from one place in the transaction to another. When writing a new rule using LOOKUPV2(), you'll see updated guidance to walk you through the steps.

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

We've made improvements to the EDI Accounts Page:

• The EDI accounts page has been moved directly within the navigation menu, under the requirements section.

• You can set up new default requirements on each EDI account:
  • Data format and Version
  • Send Acknowledgements
  • Receive Acknowledgements
  • Timeout time
  • Communication Channels
  • Guidelines
  • Scenarios
• You can see all EDI account defaults in one place.

When new relationships are created, you don’t have to manually configure them anymore. Orderful can auto-configure them entirely based on the default requirements set up on the EDI accounts.

That means if you and your partner set up all default requirements on your respective EDI accounts, new relationships will be ready to be tested right away.

We have recently pre-populated allowed values from the X12 specification into our Guideline creation UI.

When you are creating a new X12 Guideline, you will now sometimes see a list of allowed values already available for a particular element. This only occurs if the X12 specification contains a list of allowed values.

You can now define custom allowed values as well.

Here is an example of the new UI for an 850 SAC01 element:

We have added a new header to the Transaction Details UI. In addition to a visual refresh that displays more information, this new header also allows you to manually create Acknowledgments for inbound Transactions. If you choose to reject a Transaction, you will be prompted to provide a reason for rejection.

We’re introducing a new Forward feature.

As a customer trading JSON, you can now configure your Inbound Relationship to forward transactions to one of your Outbound Relationships.

Note:You can only forward transactions if both Relationships have been configured with the same data format and version. Additionally, only JSON transactions can be forwarded.

If “Auto-send” is enabled for a Relationship, inbound transactions will be automatically forwarded when they are sent to the receiver organization.

You’ll also be able to forward inbound transactions manually from the transaction details page if a forward is configured on the associated Relationship.

Note: If you have Rules written for your inbound transaction, they won’t be applied on the forwarded transaction.

Any transaction forwarded will appear in the audit trail of both impacted transactions.

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.

We improved the following pages to guide you while onboarding your first partnership:

• Transactions
• Trade Requests
• Relationships
• Scenario Testing
• Communication Channels
• Scenarios
• Guidelines
• Integration Assistance

If you haven’t created anything on any of these page, you’ll now have:

• A brief description of the page
• A summary of any prerequisites
• Links to documentation

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:

• Create an Acknowledgment
• Get an Acknowledgment

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.