Summary

We've made several changes to the editor used to create or edit Guidelines to make things clearer and easier to use:

• When creating a new guideline, if the selected transaction type already has an existing draft guideline, you’ll be warned about that right up front and won’t be able to continue. Previously, you wouldn’t find out about that until you’ve already spent the time setting up your guideline structure.

• The ISA & GS segments, as well as transaction sets & the first segment of any selected loop are now ‘locked’ - i.e. they can’t be deselected.

• Checking a loop will automatically check any of its contents which are mandatory under the X12 spec (although they can still be deselected, with the exception of the first segment in the loop).

• Unchecking a loop will automatically uncheck all of its descendants too. This eliminates the possibility of creating an invalid guideline structure in the structure editor, which previously would prevent the user from saving the structure.

• The ‘plus’ and ‘minus’ buttons to add and remove variants are now swapped - only the bottom-most variant has the ‘minus’, while all others have the ‘plus’.

• When attempting to edit the structure of a guideline, if you have existing unsaved changes, you are warned about that before you’re able to edit the structure. Previously, you wouldn’t be warned until after you had already made your structure changes.

Summary

We've made some improvements to viewing and editing an invalid Transaction for your experience. If a Transaction is invalid because it doesn't meet your Trading Partner's guidelines, you can now access them directly by clicking on "View Guideline" button or by clicking the "View in Guideline" icon in an error card!

Summary

We're excited to announce support for Webhook destinations. Webhooks will allow us to push Transactions directly to your endpoint when they are received in Orderful.

How To Create a Webhook

Webhooks can be created via the UI by navigating to the Settings tab in the top right of the navigation bar.

Then click on Settings.

From here, you may enter the URL that you would like to receive the transaction_created webhook event for.

After you save the URL, we will provide you with your Secret Key that you can use to verify that we are the sender of the requests.

See the Webhooks guide for more details.

Summary

Orderful now supports multiple Guideline variants to help you complete guidelines for complex transactions such as an 856.

Creating a Guideline and adding multiple items

Clicking "New Guideline" will now bring up the Guideline Structure Editor, which you can use to select relevant loops or segments that you need. To add variants, simply click the "+" and variants will appear. To remove a variant, you can click the "-" button.

Summary

We've added a new way to create and customize your guidelines using the Guideline Structure Editor. Say goodbye to marking entire loops and segments as not used to remove them from your guideline, and use this instead to pick and choose the items that you'll need in your guideline!

Editing a Guideline with the Guideline Structure Editor

Click on any Guideline that you wish to edit, and then select the "Edit Guideline Structure" button. A window will open that allows you to select and de-select specific loops or segments.

Summary

We're happy to announce that we have introduced Draft, Published, and Archived Guidelines to Orderful. With this new feature, transactions will not be validated against a guideline until it is has been published.

Publishing a Guideline

Here is an example of how you would go about Publishing a Guideline

Copy to New Draft

If you wish to make changes to an already published guideline, you can make use of the Copy To New button to make an improved version of your Guideline.

Summary

Organizations often have more than one ISA ID that they use to send EDI transactions. With this release, we're happy to announce that Orderful now supports multiple ISA IDs per organization.

Just as before, a 'relationship' in Orderful continues to exist between two organizations, but enabling a relationship now means that documents can be transmitted between any of the sending or receiving party's ISA IDs. Any EDI guidelines that have been created for the sender or receiver will apply, regardless of which ISA ID is being used – which means that you only need to set them up once.

If your organization only uses one ISA ID, you don't need to change anything with your existing workflow. If you'd like to add a second ISA ID, you can do that under the new 'EDI Accounts' option under your organization's settings, as shown below.

If you'd like to view all the ISA IDs being used by your trading partners, you can do so under the 'Relationships' link by clicking on an individual relationship.

New interfaces

New Organization -> EDI Accounts tab:

Create/Edit EDI account modal:

New columns on the transactions views:

New columns on the transaction detail view:

View relationship -> edi accounts table:

Summary

We have added support for the following transactions to the Print View feature:

• Response to a Load Tender
• Transportation Carrier Shipment Status Message

Response to a Load Tender Print View

Transportation Carrier Shipment Status Message Print View

Changelog

• added: Transaction Print View for Response to a Load Tender
• added: Transaction Print View for Transportation Carrier Shipment Status Message

Rule logs are a new Orderful feature meant to make it easier for you to troubleshoot a Relationship Rule or Transaction Type Rule. Now, whenever you are unsure about why or how a rule was applied to a property in your transaction, we show you a step by step evaluation of how the rule was executed. This is especially useful when a rule isn’t giving you the results you expect or when a rule is giving you an error.

Viewing Rule Logs for a Transaction

1. Click on the transaction
2. Go to the Rules Editor
3. Click the dropdown in the right hand side pane
4. Select 'Rule Logs'
5. Click 'Show Execution Log' for the rule you're trying to investigate

Reading Rule Logs

This is an example of the step by step evaluation. Expressions are evaluated from the inside out to reflect the logical order of execution. In this example the first three steps resolve references that will become the arguments used in step 4.

Notifications allow you to stay informed of significant events in Orderful. In this release, we are introducing three types of Email Notifications:

• Invalid Transaction
• Failed Transaction
• Rejected Transaction

These Notification types track a Transaction state change in which the new state of a particular transaction is Invalid, Failed, or Rejected. An Email Notification will be sent to users who subscribed to any of those Notification types via their Account's settings panel.

Subscribing to Notifications

To subscribe to Notifications, go to Settings and click on Notifications (under User Settings). You'll then be able to subscribe to any of the available Notification types by checking the box associated with the desired Notification type and clicking "Save Changes". To unsubscribe, uncheck the box associated with the desired Notification type and click "Save Changes".

In this example, a user who has subscribed to Invalid Transaction Notifications is notified by email that a transaction sent to a trading partner is Invalid because it does not meet the validation requirements of the trading partner. Read more about Transaction Statuses here.