We've got a really exciting new feature to announce – support for X12 relational conditions, i.e. Syntax Notes!

Under the X12 specification, whether or not a certain data element should be sent as part of a given segment often depends on whether other related data elements are sent alongside it. For example, if one data element contains a qualifier code specifying the type of data sent in another element, then it's often the case that you need to send either both of those elements together, or neither of them, otherwise your X12 message will be invalid.

With our new Syntax Notes feature, you're now able to specify those conditions when writing your guideline, and we'll take those conditions into account when validating transactions.

Here's an example of adding a Syntax Note to a segment:

800

We know it can be a lot of work adding all your trading partner's requirements when building a guideline, and our syntax notes feature just adds to that, so we've snuck in one more new feature with this release – improved pre-population of X12 default values!

What that means is that when you add a new segment to your guideline, the syntax notes & maximum use values specified by the X12 standard will be pre-filled for you, and any elements which are always mandatory in that segment, together with their data types & lengths, will be automatically added as well. We think you'll now find that once you've added all the needed loops & segments to your guideline, your work is very nearly complete.

We've got a new feature to announce today – the ability to upload a PDF of your guidelines, accessible by both your organization and your trading partners.

We've been working hard here at Orderful on our Guidelines feature, and we've made a lot of improvements over the past couple months to make guideline entry easier and faster than ever. That said, we understand that mistakes do happen when entering data, and we've heard the request that it'd be nice to have an easy way to reference the original PDF guideline to verify that the guideline was entered correctly and that transactions are being validated as expected.

That's now a possibility with our new PDF guideline upload feature, live in our app as of this morning. You'll have the opportunity to upload your PDF at the time of either creating a new guideline or viewing an existing one. Also, when your trading partners see that one of their transactions has failed validation, they'll also have the opportunity to click through to your guideline and download the original PDF.

See it in action:

600

As always, we'd love to hear your feedback, so reach out to us anytime and let us know how you like it!

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.

480

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!

1905

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.

1014

Then click on Settings.

1012

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.

1151

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.

1905

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.

948

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

1905

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.

1905

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:

1200

EDI Accounts tab

Create/Edit EDI account modal:

714

New columns on the transactions views:

1202

New columns on the transaction detail view:

1207

View relationship -> edi accounts table:

1211

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

1920

Transportation Carrier Shipment Status Message Print View

1920

Changelog

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