Skip to content

Latest commit

 

History

History
32 lines (22 loc) · 3.65 KB

repairing-messages-and-submitting-new-messages.md

File metadata and controls

32 lines (22 loc) · 3.65 KB
description title ms.custom ms.date ms.service ms.reviewer ms.suite ms.topic
Learn more about: Repairing Messages and Submitting New Messages
Repairing Messages and Submitting New Messages
06/08/2017
biztalk-server
article

Repairing Messages and Submitting New Messages

[!INCLUDEbtaA4SWIFT2.3abbrevnonumber] Message Repair and New Submission enables you to repair a message that has failed XML or Business Rules Engine validation. The repair process includes verification and approval steps that ensure the accuracy and appropriateness of the message repair. This process is performed using Microsoft [!INCLUDEbtsOfficeNoVersion][!INCLUDEbtsInpathNoVersion] forms within MRSR site.

[!INCLUDEbtaA4SWIFT2.3abbrevnonumber] also enables you to submit a new message using this process. A creator submits the message, and the workflow can include a repairer, a verifier, and an approver performing the same tasks as in message repair.

[!INCLUDEbtaA4SWIFT2.3abbrevnonumber] ensures the security of this process by assigning different users to perform each task. You assign the appropriate repair, verify, or approve role to each of these users, and each user must use a specific certificate to perform the task. [!INCLUDEbtaA4SWIFT2.3abbrevnonumber] also supports the use of departments in processing repaired and submitted messages. Each department involves a specific workflow of tasks performed on a specific set of messages. In any of the create, repair, verify, or approve steps, when you submit the message, [!INCLUDEbtaA4SWIFT2.3abbrevnonumber] calls BRE validation and verifies that the user is a member of the appropriate department. For more information about message repair and new submission, see Message Repair and New Submission.

If you receive an unparsed message, Message Repair and New Submission displays the message and a description of the failure in an [!INCLUDEbtsInpathNoVersion] form, and enables you to print the message or save it to a file. You can then repair and resubmit the message. However, [!INCLUDEbtaA4SWIFT2.3abbrevnonumber] does not call BRE validation or check membership in a department when you submit an unparsed message that you have repaired. In addition, a resubmitted unparsed message is not verified or approved. For more information about unparsed messages, see Repairing Unparsed Messages.

This section contains: