Repairing Messages and Submitting New Messages
A4SWIFT 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 OfficeInfoPath forms within MRSR site.
A4SWIFT 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.
A4SWIFT 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. A4SWIFT 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, A4SWIFT 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 InfoPath form, and enables you to print the message or save it to a file. You can then repair and resubmit the message. However, A4SWIFT 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: