D Object Naming Rules in Oracle Portal

This appendix summarizes the rules that apply to the naming of objects in Oracle Portal. Unless otherwise indicated, names and display names are not case sensitive. In other words, in most cases APP is the same as app.

Table D-1 Object Naming Rules in Oracle Portal

Object	Name	Display Name
Attributes	256 bytes Must be unique within its page group and the Shared Objects page group Defaults to Display Name minus invalid characters when no value is entered Alphanumeric and underscore (A to Z, a to z, 0 to 9, and _)	256 bytes Any character, except comma Commas in attribute Display Names interfere with the display of attributes in search-related selection boxes. This is because commas are used as delimiters between attribute names. For example, an attribute with the Display Name Sales, London, UK, appears as three separate, selectable attributes in search-related selection boxes. Multi-byte characters allowed
Categories	60 bytes Case sensitive Defaults to Display Name minus invalid characters when no value is entered Must be unique among all categories at the same level within its page group. Alphanumeric and underscore (A to Z, a to z, 0 to 9, and _)	240 bytes Any character Multi-byte characters allowed
HTML Templates	50 bytes Must be unique within its page group Multi-byte characters allowed Any character except: , & # % \ / : * ? < > | "	With HTML templates, the Template Name doubles as a Name and a Display Name
Items and Portlets	256 bytes or 126 bytes for file names Case sensitive Must be unique within its parent page; when tabs are present, must be unique within a given tab. Multi-byte characters allowed Anything except: , & # % \ / : * ? < > | " In the case of uploaded files, defaults to file name; if file name contains illegal characters, defaults to GUID	256 bytes Any character; in the case of uploaded files, defaults to file name if unspecified Multi-byte characters allowed
Item Types	30 bytes Must be unique within its page group and the Shared Objects page group Defaults to Display Name minus invalid characters when no value is entered Alphanumeric and underscore (A to Z, a to z, 0 to 9, and _)	256 bytes Any character Multi-byte characters allowed
Navigation Pages	60 bytes Case sensitive Defaults to Display Name minus invalid characters when no value is entered Must be unique within its page group Multi-byte characters allowed Anything except: , & # % \ / : * ? < > | "	256 bytes Any character Multi-byte characters allowed
Page Groups	60 bytes Case sensitive Defaults to Display Name minus invalid characters when no value is entered Must be unique among page groups Multi-byte characters allowed Anything except: , & # % \ / : * ? < > | "	256 bytes Any character, except comma Commas in page group Display Names interfere with the display of page groups in search-related selection boxes. This is because commas are used as delimiters between page group names. For example, a page group with the Display Name Sales, London, UK, appears as three separate, selectable page groups in search-related selection boxes. Multi-byte characters allowed
Pages	60 bytes Case sensitive Defaults to Display Name minus invalid characters when no value is entered Must be unique among all pages that are at the same level in its page group's page hierarchy. Multi-byte characters allowed Anything except: , & # % \ / : * ? < > | "	256 bytes Any character Multi-byte characters allowed
Page Types	30 bytes Must be unique within its page group and the Shared Objects page group Defaults to Display Name minus invalid characters when no value is entered Alphanumeric and underscore (A to Z, a to z, 0 to 9, and _)	256 bytes Any character Multi-byte characters allowed
Parameters	200 bytes Case sensitive Must be unique within its parent page Alphanumeric and underscore (A to Z, a to z, 0 to 9, and _)	4000 bytes Any character; defaults to Name if unspecified Multi-byte characters allowed
Perspectives	60 bytes Case sensitive Defaults to Display Name minus invalid characters when no value is entered Must be unique among all perspectives at the same level within its page group. Must be unique within its page group and the Shared Objects page group. Alphanumeric and underscore (A to Z, a to z, 0 to 9, and _)	240 bytes Any character Multi-byte characters allowed
Portal Templates	60 bytes Case sensitive Must be unique within its page group Defaults to Display Name minus invalid characters when no value is entered Multi-byte characters allowed Anything except: , & # % \ / : * ? < > | "	256 bytes Any character Multi-byte characters allowed
Regions	Regions do not have a Name field	4000 bytes Any character Multi-byte characters allowed
Styles	65 bytes Must be unique within the page group Defaults to Display Name minus invalid characters when no value is entered Alphanumeric and underscore (A to Z, a to z, 0 to 9, and _)	350 bytes Any character Multi-byte characters allowed
Tabs	60 bytes Case sensitive Must be unique within its tab set; by tab set we mean all tabs at the same level within the same set, excluding sub-tabs; sub-tabs are members of their own tab sets Multi-byte characters allowed Anything except: , & # % \ / : * ? < > | "	256 bytes Any character; defaults to New Tab if unspecified Multi-byte characters allowed

Notes

In Oracle Portal, Name uniqueness is preserved automatically by the addition of a value.

If the Shared Objects page group contains an object that uses the same name as an object that you move to the Shared Objects page group, Oracle Portal appends a value to the Name (internal name) of the moved object. This is to maintain name uniqueness within the page group.

For example, imagine that the Shared Objects page group contains a category named sample_category. Another page group, Division, contains a category that is also named sample_category. You move sample_category from the Division page group to the Shared Objects page group. Oracle Portal appends a value to the moved category, such as sample_category_AABkUWAAJAABpiAAC. You can revise the internal name, but you cannot give it the same Name as any other object in the Shared Objects page group.

The same rule applies when you try to create any object with a Display Name that duplicates another object's Name. Oracle Portal uses an object's Display Name to create the object's (internal) Name. If you enter the Display Name red for an object, and another object already uses the name red. The first object's Display Name will be red, but its Name will have a value appended to it to make it unique, for example, red1.