This change comes with a helping of humility. We're making a breaking change to an API endpoint. After some future planning we've realized a recently released endpoint could be made more future-proof with a small modification. The only reason it's acceptable to make a breaking change is that our operational analytics indicate that no one has integrated to the endpoint yet. There are occasional test requests but no production loads relying on it.
We are excited to release another improvement to our platform: Poller communication channels!
Since releasing our Scenario Testing feature, we have received feedback from our customers that testing does not always take place in the Orderful platform. To solve for cases where you do not want to do any testing in Orderful, we have introduced functionality that allows you to skip testing any of your Scenario Checklists .
We're excited to launch a new feature in Orderful: Communication Channel Testing.
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.
Today we improved the relationship configuration around Communication Channels.
On a relationship, you can now assign one Communication Channel for each transaction stream.
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.