- Possible Value Keys, Configuration Values, User Messages

Keyed Possible Values

This section allows you to manage keyed values, including possible values, configuration values, and user/error messages.

View Possible Values

With a keyed possible value, you specify a key, a value, and a display value for each PV. (The key is used to group the PV's together). Then in an FD (field descriptor) under the list of Possible Value Keys, you will see the keys of the Possible Values that you added. This is a separate PV option than using PV Operations - so there are two different ways to use PV's with WOW.

This displays a list of all of the Possible Value Keys that have been created. The size of the list will vary greatly depending on how many PV keys have already been set up on your version of WOW. The screenshot below shows a list of PV keys.

Add Possible Value

Adding a keyed Possible Value is much like adding a user account or theme like described above. The figure below shows an example of the Add Keyed PV Operation.

Possible Value Group Information

Key – This is the Key that will be used with the Possible Values.

Possible Value Keys were described in detail here.

Possible Value Information

Value – This is the value given to a specific possible value. Generally numeric data is used for the value when working with PVs but this is not required.

Display Value - This is the value displayed for the PV. This should be as descriptive as possible making it easy for the user to understand the value being used.

TODO: Complete sections below.

Additional Information

Display Order – ###

View Configuration Values

###

TODO: Finish configuration values

Add Configuration Value

###

Add User Message

User Messages provides the ability for you to supply your own messages to your WOW Applications. For example, a common error message that occurs when a user tries to insert a duplicate key value would be:

[23000] A violation of the constraint imposed by a unique index or a unique constraint occurred. Duplicate entry

This is not a user friendly error message you would want your users to see. Using User messages, you can override this internal system error message with a user friendly alternative.

The User Messages section of the WOW utilities contains two operations, “Add User Message” and “View User Messages”

The screen shot below shows the Add User Message screen. After adding the relevant information, simply hit the insert button to add the new user message.

Message Information

• • Message Type – This is the message type to override (insert, update, delete, etc.). This field is required.

  • Matching Error Message Text– For error messages, this is the matching text from the original message that will be used to identify the specific message to replace. This field does not apply to the non-error message case and will be ignored. This field is optional. If this field is not specified in the error case, the user message will be used for all error messages of the specified message type. If you specify two messages of type "Delete Error" and the second entry leaves the matching text field blank, the first entry will be used when a match is found and the second entry will be used in all other cases for that message type. You will want to use just a partial text string such as "Duplicate Entry" Do not include the error message id (23000) because it is not part of the searched error string.

  • Replacement Message- This is the replacement message to be displayed. The message text can contain non-prompting parameters (ex. ??FLD1 or ???USERID). This field is required. This is the user friendly message the user will see such as "Duplicate Item Found, Please Specify a Unique Value".

TAGS: Override message, ERROR messages, User messages, override errrors, use my own message

NOTE: For performance reasons, the user message entries are read in once after the server is started. If message entries are changed after the server is started, you will most likely need to restart your server again to incorporate the new replacement messages.

File Information

• • Connection Name – This is the connection alias used to access the table. This field is required.

  • Library Name – This is the library that contains the table. A generic '*' (without the quotes) is allowed to represent all libraries. This field is required.

  • Table Name– This is the table name that the message override applies to (for any insert, update and delete). This field is required.

View User Messages

This displays a list of all user messages that have been created.