Setting Application Message Numbers

Typically, the unique message number consists of an alphanumeric prefix that identifies the application or its owner, followed by an autonumbered suffix that is created and applied when the message is constructed. You are not required to follow this model, but it provides the best way to identify and locate messages.

For example, your organization is called WonderWare, and you have an application called IssueTrack. You can create and designate a message number prefix like "WW-IssTr-" to identify all messages used in conjunction with this application. If you add an autonumbering suffix to this, you can then create messages for your application without worrying about maintaining unique message numbers. Using this process also allows you to locate all messages designed for use with this application.

To create this type of message numbering:

Use the Message Num Prefix field on the System Parameters form or General Parameters form to specify the prefix. The system uses the prefix automatically when messages are created.
Use the Maintain Application Messages form to construct the message.

For more information see Constructing Application Messages.

The Message Num column on this form is defined as a TBD (To Be Determined) field, which means that, when you create a message and save it, the system automatically uses the prefix and assigns the next available number as the suffix.
Continuing our example, when you create your first application message, the system automatically assigns the message number "WW-IssTr-1" to it. The next message is created as "WW-IssTr-2" and so on.

Note: Predefined core messages assigned to and used by Mongoose have the prefix "MG_". Other Mongoose-based applications might have and use other prefixes.
Save the message.