We're excited to launch a new feature in Orderful: Communication Channel Testing.

For each inbound HTTP or AS2 Communication Channel connected to your internal systems, you can now directly send a test file over and check the connection is up and running.

Send a test to a Communication Channel

From the right side panel of an inbound Communication Channel, you now have the option to "Send a test". You can choose to send one of the generic Orderful test files or upload your own custom test file.

Orderful then displays a test summary, that contains:

• The test status
• The test file you sent
• The delivery proofs (if any)
• The delivery logs

Test an HTTP Communication Channel

When testing an HTTP Communication Channel:

• The test status can only be “Delivered”, “Failed” or “Timed-out”.
• The HTTP response code appears on the “Log” row.
• The full HTTP Response is stored as a file on the Received row.

Test an AS2 Communication Channel

When testing an AS2 Communication Channel:

• The test status is “Pending” until your AS2 server sends a final successful or failed delivery notification. The test status then becomes “Delivered”, “Failed” or “Timed-out”.
• The Message Disposition Notification (MDN) is stored as a file on the Received row.
• The “Log” row displays all delivery notifications received.

In our latest release we’ve added notifications for invalid, inbound transactions. If you validate your inbound transactions against your own inbound guideline, you can now subscribe to be notified whenever you receive a transaction that does not meet your requirements.

You can find the subscription box under your Notification Settings.

We improved the relationship configuration around Communication Channels. On a relationship, you can now assign one Communication Channel for each transaction stream.

Communication Channels for inbound relationships

For transactions that you receive (inbound transactions):

• Live stream transactions are sent to your Live Communication channel.
• Test stream transactions are sent to your Test Communication channel.

📘

To automate the configuration of your inbound relationships, you can set default test and live communication channels on the Communication Channels settings page.
Default test and live communication channels will automatically be assigned to new inbound relationships.

Communication Channels for outbound relationships

For transactions that you send (outbound transactions):

• Functional acknowledgements you receive for live stream transactions are sent to your Live Communication channel.
• Functional acknowledgements you receive for test stream transactions are sent to your Test Communication channel.

Today we improved the relationship configuration around Communication Channels.
On a relationship, you can now assign one Communication Channel for each transaction stream.

Communication Channels for inbound relationships

For transactions that you receive (inbound transactions):

• Live stream transactions are sent to your Live Communication channel.
• Test stream transactions are sent to your Test Communication channel.

📘

Default inbound communication channels

To automate the configuration of your inbound relationships, you can set default test and live communication channels on the Communication Channels page.
Default test and live communication channels will automatically be assigned to new inbound relationships.

Communication Channels for outbound relationships

For transactions that you send (outbound transactions):

• Functional acknowledgements you receive for live stream transactions are sent to your Live Communication channel.
• Functional acknowledgements you receive for test stream transactions are sent to your Test Communication channel.

We have just released a new notification option on Orderful's settings page: Unprocessed Transactions.

Signing up for this alert means you will receive an email notification anytime a transaction is posted by you or your trading partners and it fails to create a transaction in Orderful.

To subscribe to this new notification, sign into Orderful and navigate to your Notification settings page.

We have improved visibility of the transactions that are sent over AS2, FTP/SFTP or VAN by adding delivery information to the transaction's audit trail.

You can now see the delivery status from the “Audit Trail” icon in the top right of the Transaction details page. You will be able to see delivery successes, delivery failures with their logs or even detect communication channel misconfiguration.

If a transaction has been sent over an AS2 connection, you can now view and download the Message Disposition Notification (MDN) as proof of delivery from the “Download Files” icon, also in the top right of the Transaction details page.

Today we improved our transaction sending functionality. For transactions sent over AS2, FTP/SFTP or VAN, we added delivery information on the transaction audit trail and on the transaction files.

You can now see the delivery status from the “Transaction Audit Trail”. You can see delivery successes, delivery failures with their logs or even detect communication channels misconfiguration.

If a transaction has been sent over an AS2 connection, you can now view and download the Message Disposition Notification (MDN) as proof of delivery, from the “Download Files”.

Feature

• Added the ability to resend accepted inbound transactions to the designated communication channel.

Changes

• The business number of X12 document type 820 Payment Order/Remittance Advice is now taken from the Reference Identification field in the Trace segment (transactionSets[0].trace[0].referenceIdentification).
• Uploading or assigning a scenario file is no longer required when creating or editing a scenario.

Features

• Create, edit & publish testing scenarios (for more information, see the documentation at https://docs.orderful.com/docs/about-scenarios).
• This is step 1 of a much larger feature release coming in the weeks ahead. Stay tuned...