Chain agreements: feedback, correction, chunking, transport, releases

Correction and resending: once accepted, never corrected unilaterally

After a rejection the sender may send a corrected message without consultation. After an acceptance not: a reused messageId yields HTTP 400 with feedback, and a correction first requires consultation with the receiver. The correction message gets a new messageId and refers with originalMessageId to the message it replaces. Message function 54 is something else: sending unchanged content again.

Steps

• After rejectionSenderCorrect and resend with a new messageId; originalMessageId refers to the rejected message.
• After acceptanceSender and receiverConsult; only then a correction message with a new messageId and originalMessageId. Function 54 is only for sending unchanged content again.
• Non-executable orderReceiverFunctional rejection via feedback with statusType 0 and classified errorCode. feedback

Source: Handleiding paragraaf 2.4 en 4.4; release notes v0.2.0 (function 54); codelijst ADNFUN