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?

Release date: 03/18/2021

Overview: Updated design of the Rules Editor.

Purpose: Same functionality, better experience.

Release date: 03/18/2021

Overview: Added optional 'note' property to Confirm Delivery endpoint for your backend to post delivery notes back to Orderful. These notes are added to the transaction's audit trail.

Purpose: Your ERP can now include a delivery 'note' when confirming the delivery of a transaction. This note will be added to the transaction's audit trail for your reference.

For more information about this new feature, please see this article:

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

Release date: 03/09/2021

Overview: Email notifications for any change of a transaction's validation status, delivery status, or acknowledgment status.

Purpose: Provide an easy and consistent way to subscribe to notifications related to your transactions.

Your subscriptions to email notifications can be managed on the Notifications Settings page.

When subscribed to an email notification, Orderful will send you an email every time a transaction meets the status requirement of the notification (e.g. delivery status = failed).

We’re excited to announce the next improvement to our platform. Data format on relationships!

Release date: 02/18/2021

Overview: Data format toggle migrated from Communication Channels to Relationships.

Purpose: You can now specify your desired data format on a per-relationship basis. 

After analyzing the way our customers trade JSON and X12 data, we decided to move the data format toggle from Communication Channels, on to Relationships. This makes it easier for you to handle your data formats on a per-relationship basis, independently of that of your trading partner.

You'll notice the data format toggle on top of the relationship's side panel.

We’re excited to announce a new improvement when sending a transaction to a communication channel.

Release date: Released on 02/17/2021

Overview: Standardize our retry system when sending a transaction to a communication channel

Purpose: Orderful now retries sending a transaction to a communication channels 3 times before moving the transaction to the Failed delivery status.

To make sure a delivery failure isn't related to a server temporary issue, Orderful now retries sending a transaction to a communication channels 3 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 are captured on the audit trail.

A delivery failure on the 3rd retry moves the transaction to the Failed delivery status.

📘

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