After all the excitement of our new rules editor and guidelines feature wore off we took the opportunity to fix a few bugs.

Changelog

• fixed: Nested REPLACE rules weren't evaluating correctly
• improved: The dropdown to select another path when creating a rule has been sped up considerably
• improved: Made breadcrumbs bigger and easier to see
• fixed: Daylight savings time was not being correctly referenced in timestamps

Today marks a big release with some new features and important fixes. The platform team is proud to introduce Guidelines and a revamped Rules Editor

Guidelines

Guidelines allow an organization to create an element-by-element specification for their trading partners to follow when crafting a transaction. Orderful provides these guidelines for all off-network organizations so you can make sure you trade right the first time. This saves time and costly penalties.

The creation process for guidelines should be familiar to anyone who has read an EDI spec.

Rules Editor/Transaction View

There were two things about Orderful's rules editor that we knew we could improve – first, the widget interface was less than intuitive, and second, it was awkward having to write rules without being able to see the validations at the same time. With today's new rule editor all rules are created in a single text entry bar familiar to anyone who's used Microsoft Excel. The bar has been fixed overtop of the transaction view with enough room for validations to be seen to the right of the transaction. It's now easier and faster than ever to create rules.

Also, this new entry makes it possible to easily add complex logic like nesting and branching of rules.

But wait there's more....

There's also a new organization switcher in case you're responsible for managing multiple organizations

Plus some minor tweaks you can read more about below.

Changelog

• added: Guidelines feature
• added: New Rules Editor
• added: Organization switcher
• improved: Update password now requires an e-mail
• fixed: Unreadable code errors being displayed on API calls

Ability to register webhooks to receive async updates when you have a new transaction.

Changelog

• added: Create Transaction webhook
• fixed: Stopped DB errors form being shown in production

Minor update for UI with some polish

Changelog

• fixed: Various copy wasn't consistent on the site e.g. document and transaction.
• improved: Error messages are now more descriptive

Added support for 23 new transaction types. These new types map directly to familiar X12 EDI document types. Included docs are

• 204
• 210
• 214
• 810
• 820
• 824
• 850
• 855
• 856
• 857
• 870
• 875
• 876
• 880
• 940
• 943
• 944
• 945
• 947
• 990

Changelog

• added: 23 new transaction types
• fixed: Deleting rules wasn't updating transaction messages
• fixed: 404s for GET /transactions/{id} could return an empty pagination envelope

Enjoy our fresh new look!

Also tackled a bug hounding a few integrations where external trading partner transactions were previously getting held up for not meeting the semantic validation. This restriction has been loosened so those transactions no longer need to pass validation, they can simply be corrected with a rule on the Orderful user side.

Changelog

• fixed: Inbound transactions from external organizations are no longer gated
• added: New styling in attractive Orderful orange added
• fixed: Improved error messages when something fails to save
• fixed: General stability fixes

An assortment of minor bug fixes as reported by users like you.

Changelog

• fixed: Transactions sent to you but still being tested by your trading partner are no longer visible in the list view
• fixed: POST'd transactions which have invalid data and a trading partner with whom you don't have a relationship now return a 400 Bad Request but no longer create a new relationship.
• fixed: Transactions with invalid/failing rules no longer fail to be created

Two quick fixes.

Changelog

• fixed: dateFrom query parameter was not exclusive.
• fixed: ISA IDs could contain leading or tailing white space. Now they are trimmed.

New feature to offer our API users more options.

Changelog

• added: Ability to select which idType you'd like GET /transactions to return. Default is isaId and withOrgId parameter makes it orgId
• fixed: Sometimes selecting a Modify Rules from a transaction view would open the rules editor with a different transaction

Improve performance on some actions by over 50% and more.

Changelog

• improved: Merged some function calls together to improve performance
• fixed: Removed ability to over post transaction data
• fixed: Fixed bug causing some new relationships to fail