Navigating the MER user interface

Figure 1 shows the main pages of the Message Entry and Repair facility, and how to navigate them:
Figure 1. Main pages of the Message Entry and Repair Facility
Figure showing the main pages of MER and connections between them
 1  MER
The Message Entry and Repair page is the entry point to the Message Entry and Repair facility. It displays a list of queues for the selected OU, as described in Entry and Repair page. From that list, you select a queue either to work with its message list  2  or to create a new message  3 .
 2  Message list
The message list provides access to existing messages, draft messages, or templates in the MER Facility. For more information, see Message list page. From the list, you can open individual messages as described in Opening a message. Depending on the queue purpose, the message content is editable  4b  (for queues with purpose Create or Edit) or read-only  4a  (for queues with other purposes). From a queue with purpose Create and of type draft or template, you can directly start to create a new message or template  3 .
 3  Create a message
The Create page is used to select the message domain, sender, and type of a new message or template. These values must be chosen in advance because they define the structure of a message and are also needed to check user rights. They can be selected individually or by choosing an existing template (see Message editor tasks). After the required values are selected, the page for editing the new message is displayed  4b .
 4a  4b  Message that is read-only or editable
The message processing page presents the content and associated data of a message. It is described in Message processing page. After you close the current message, you return to the message list  2  or the Create page  3  from which you opened the message.
 5  Message that is unparsable
When you open an unparsable message or use a template that became unparsable because of a SWIFT standards release change, the message cannot be presented in the regular fashion. Instead, the page for unparsable messages opens. It displays the message in raw format for provisional editing (see Editing a message). After the parsing problems are fixed, you can proceed to the message processing page  4b .
Note: Do not use multiple browser tabs or windows to access MER. Do not use the back button or the browser history within MER, either. Otherwise, you will encounter problems because only one message can be open in a user session. The server tracks which message is open and issues a warning when you try to open another one. It issues an error when you work with a message that is no longer open. The server also tracks refreshes of the formatted view of a message and issues an error if you work with an outdated view.