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.
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.
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
Click on the transaction
Go to the Rules Editor
Click the dropdown in the right hand side pane
Select 'Rule Logs'
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".
Subscribing to Notifications
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.
Our Print View make EDI transaction data easy to understand with the naked eye and our web form feature allows you to create any transaction easily on our web site. Now, we've combined the power of both to allow for data entry in an attractive, simple package.
Supported transaction types:
204 Motor Carrier Load Tender
812 Credit Debit Adjustment
820 Payment Order/Remittance advice
824 Application Advice
850 Purchase Order
860 Purchase Order Change
864 Text Message
Overview
To start, go the transaction list and click 'New Transaction'. Once you have selected one of the supported transaction types above, you will see the new print view entry where you can preview the print view as you fill out the form.
As you focus on an input field and start typing, if the field is used to form the print view, it will be highlighted in yellow on the print view and display the value, otherwise, it will be shown under the 'Additional Fields'.
You can also click on the print view field or the additional field, and it will scroll to the corresponding input field on the form.
Once you click 'Save', if there are errors, they will be displayed both on the form and on the print view. You can click the errors on the print view or simply click 'Start fixing' on the new error wizard, and you will be navigated through the errors and be able to correct them.
Wherever you are in Orderful's application, you'll now always see your active organization's logo in the navigation bar, so you'll always know which organization's data you're looking at. Don't have a logo yet? No worries – we've set the default logo as your organization's initials.
To upload a logo, navigate to the 'Organization' tab in 'Settings' and upload either a JPEG or PNG image file. To delete your uploaded logo and restore the default logo, simply click 'Delete Image'.
Today we're announcing the launch of our lookup data feature. A frequent ask from customers and implementors is the ability to have a "scratch pad" of structured data that they can add to their transactions. With the new lookup data feature, you can now securely store information like product item data, vendor locations, or any other information in our flexible lookup data tables, and then apply this information to your transactions, all in just two easy steps.
Store your data
Create your lookup table by defining key-value data pairs.
Applying the data in the rules engine
Using the new LOOKUPDATA function you can write rules to reference your lookup tables and populate your transactions.
