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:

• What are Transaction Workflows
• Understand Workflow Requirements and Workflow Validation

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:

• For Followers: https://docs.orderful.com/docs/test-go-live-follower#scenario-testing-for-followers
• For Leaders: https://docs.orderful.com/docs/test-go-live-leader#scenario-testing-for-leaders

Release date: 05/04/2021

Overview: New OAuth 2.0 configuration available on HTTP Communication Channel.

Purpose: When creating or editing an HTTP Communication Channel with an Authorization Type OAuth 2.0, you can now optionally configure an Audience and add one or several scopes.

More details about HTTP Communication Channels on this article:

• For Followers: https://docs.orderful.com/docs/set-up-org-follower#inbound-http
• For Leaders: https://docs.orderful.com/docs/set-up-org-leader#inbound-http

Release date: 04/23/2021

Overview: New notifications for incoming EDI failures

Purpose: At Orderful we take care of the behind the scenes work of managing EDI connections. This makes EDI easy as calling an API. Unfortunately sometimes there are problems with data from your trading partners for which needs attention, for example if they send malformed EDI and we can't make heads or tails of it. In some cases the only solution is to reach out the trading partner and ask them to fix it. Traditionally we've done this by flagging trouble EDI documents in our system and then having a support agent review it and reach out to you, the customer, who in turn contacts their trading partner to resolve the situation. But when time is money, this process can take too long. So we're happy to introduce notifications which notify you of EDI destined for you which failed to be turned into transactions so you can address them faster.

See additional documentation for handling some failure notifications here: Inbound EDI Job Errors

Release date: 04/21/2021

Overview: New endpoint to list your relationships.

Purpose: This endpoint returns a paginated list of relationships and details relationships information such as relationship id, important timestamps, sender and receiver EDI accounts, transaction types and status.

Release date: Released on 04/13/2021

Overview: From the relationship side panel, you can access the guidelines assigned to your relationships.

Purpose: To help followers onboard with their leaders, we added links to the leaders guidelines to the relationship side panel. 
If you're a leader, you can also use this quick link as a shortcut to access your own guideline.

Release date: 03/30/2021

Overview: Creation of new Transaction Type Rules has been disabled.

Purpose: Any transaction type-specific logic should live in the connector between the Orderful platform and your backend. Relationship-specific logic can be defined using Relationship Rules. Existing transaction type rules can still be used and will continue to be applied to transactions.

Release date: 03/25/2021

Overview: When resending an inbound transaction to your communication channel, you now have two options:

• Send: Resend the transaction with the exact same payload as before
• Reprocess and send: Apply any rules changes, revalidate it against your inbound guideline (if applicable), and send.

Purpose: If your backend rejects an inbound transaction because of a rule issue, you can now fix the appropriate relationship rules, apply them to the transaction, and resend the transaction without having create a new copy. 

You'll notice that clicking the Send button at the top right of a Transaction details page now opens a drop down with the two options.

Release date: 04/06/2021

Overview:New Integration Assistance page to help you build your connector by understanding the JSON transaction payload and the associated leader’s requirements.

Purpose: On your new Integration Assistance page, you can select one or several relationships to generate a transaction payload that respects the leader’s guidelines. You can also access granular guideline requirements for each property of the transaction payload.

A relationship is composed of two partners - a sender and a receiver - and a transaction type.
In each relationship, one partner is the leader and the other partner is a follower.
Leaders define and assign guideline and scenario requirements that the follower must respect.

When building a connector for a transaction type, you must respect the leader’s guideline requirements when mapping your transaction payload to your ERP or SOR data: 

• If you’re a Leader, you should map the transaction payload to your requirements.
• If you’re a Follower, you should map the transaction payload to all your leader’s requirements.

The Integration Assistance helps you build your connector mapping for a specific transaction type according to the leader’s requirements by allowing you to:

• Generate a transaction payload in JSON for specific relationships of the same transaction type.
• Access the leader’s guideline requirements for each property and array of the transaction payload.

More details on these articles: What is Integration Assistance?