Configuring Notifications and Messages

You can configure notifications on messages specifically for your company.

String resource files follow the same procedure as properties files for editing the contents. You must create a page object using the exact names of the string resource files: emxFrameworkStringResource.properties and emxFrameworkStringResource_en.properties. In addition, you will have string resource files and the equivalent page objects for any language translations you want to provide.

You should create a text file containing the edited and added string resources for each string resource file. Edit that text file to add the properties below, and then import the file into the page object. For more information, see Editing Properties Using MQL.

  1. Create or open the text file to contain customized string resource properties. For more information, see Editing Properties Using MQL. To revise message text for English, open the file in any text editor.

    To revise message text for any non-English language:

    1. Open the text file using Microsoft Word.

      Word prompts you to choose the file encoding necessary to load the file.

    2. Click OK to accept the default.
  2. Copy the message you want to configure from the string resources properties file to the text file.
  3. Edit the text after the equal sign (=). Do not edit the tag that identifies the message.
  4. To define a company-specific version of the message:
    1. Copy the entire line for the standard message (tag and content) and paste it under the line.
    2. To the end of the tag, add a period (.) and the company's name, with no white space between words and using the same capitalization and spelling used in the company's database definition.
    3. Edit the message by editing the text after the = sign.
  5. If you are working with an English file, save the file normally.

    If you are working with a non-English file:

    1. Save the file as encoded text.
    2. Click Yes to save it in text format, then choose the same encoding used to load the file (should be the default).
    3. Click OK.
    4. Convert the file to ASCII by running the following command: 

      native2ascii -encoding CODE INPUTFILE OUTPUTFILE

      where:

      CODE is the language encoding (shown in the files header).

      INPUTFILE is the name of the file you edited.

      OUTPUTFILE is the name of the file to be created. The output file will be in Unicode, which means it will contain letters followed by escape characters in place of the native characters.

      For example: 

      native2ascii -encoding JIS emxFrameworkStringResource_ja_Native.properties    emxFrameworkStringResource_ja.properties

  6. When finished updating the text file with all string resources you want to modify, including the ones shown here, use the text file to modify the page object. For more information, seeEditing Properties Using MQL.