As well as EGL naming conventions, certain names in Rich
UI have additional restrictions.
When you assign names in Rich UI applications, do not use characters
that would require special encoding if they were used in a URL. This
rule applies to the following locations:
- Rich UI project names
- Package names in a Rich UI project
- RUIHandler names
- RUIPropertiesLibrary names
Examples of such characters include the number sign (#), ampersand
(&), and space characters. Double-byte characters also require
special encoding.
Symptoms
The following symptoms occur if
characters that require special encoding are used in the URL:
- If you use characters that require special encoding in the project
name, package name, or Rich UI Handler name, they are not encoded
when the URL is created for the Rich UI Handler. You cannot view the
Rich UI handler in the Rich UI editor and you cannot deploy the Rich
UI Handler. When you view the handler in the Rich UI editor, the
following error message is displayed:
document.write("Could not open /package_name/handler_name.html")
where package_name and handler_name are
the names you specified for these elements.
- If special encoding characters are used in the name of the RUI
properties library file (RUIPropertiesLibrary stereotype), the property
file is not loaded during the execution of the Rich UI handler. If
you run a Rich UI Handler that contains a reference to a RUI properties
library file, the following error message is displayed:
Could not render UI, [CRRUI2015E] The file properties/properties_file_name for RUIPropertiesLibrary rui_library_name is missing