About Administrative Object Names

You can use your exact business terminology rather than cryptic words that are modified to conform to the computer system limitations.

There are few restrictions on the characters used for naming administrative objects. Names are case-sensitive and spaces are allowed. You can use complete names rather than contractions, making the terminology in your system easier for people to understand.

The maximum length for SQL Server is 127 characters, and for Oracle is 127 bytes. The number of bytes per character depends on the database setting for character encoding. Thus, for Oracle, the character count will be fewer than for SQL Server if some characters are multibyte. The same is true for all string values stored in the database. For more information, see businessobject Command Syntax.

Avoid using characters that are programmatically significant to 3DSpace, MQL, URLs, and associated apps.

For the following list of administrative objects, only use characters from the defined list of characters to name administrative objects:

  • Admin object types: application, attribute, column, command, application, attribute, command, customevent, dimension, expression, field, format, index, interface, inquiry, location, menu, package, page, pathtype, policy, product, program, relationship, resource, rule, server, site, state, store, tenant, type, uniquekey, vault, view
  • Allowed characters:
    Character NameCharacters
    Letters a-z A-Z
    Digits0-9
    Colon :
    Period .
    Angle brackets< >
    Plus sign+
    Underscore_
    Dollar sign$
    Percent symbol%
    Exclamation Mark!
    Forward slash/
    Parentheses( )
    Space
    Pound sign#

Leading and trailing spaces are ignored in administrative object name and revision strings.

Legal characters in XML are the tab, carriage return, line feed, and the legal graphic characters of Unicode, that is, #x9, #xA, #xD, and #x20 and above (HEX). Therefore, other characters, such as those created with the ESC key, should not be used for ANY fields, including business and administrative object names, description fields, program object code, or page object content.

Avoid giving any administrative object a NAME that can be confused with a keyword when parsing MQL command input. For example, a Role named “All” is misinterpreted if you try to use the role name in the definition of an access rule (or state access definition), since “all” is the keyword that allows all access rights.