The first one is server-responsibility profile
hierarchy type. This hierarchy type can be used while defying Profile
options and can be set at Site level, User level, or a new combination
Server+Responsibility. This hierarchy type can be set in the profile
option definition and cannot be changed later at the runtime. When using
server+responsibility level both are considered as
a pair. Profile values can be set for combinations of a specific server with a specific responsibility, or for only a server or responsibility with a default for the other.
While processing a request the profile value is determined as follows:
1. User level value
2. Specific Server + Specific Responsibility value
3. Specific Responsibility + Default Server value
4. Specific Server + Default Responsibility value
5. Site level value
At top level the User level value overrides all other values. Once a profile has been defined to use the Server+Responsibility hierarchy type, values can be set at this level on the Define Profile Values page.
Second one is Profile categories that can be used to classify and group related profiles together. Once a Profile category is defined, it can be used to search for profiles by category when setting or viewing profiles values. Categories are also useful for finding related profiles, by looking for other profiles grouped in the same categories. Administrators can define as many categories as per the requirement , containing any profiles. Many profile categories are available as seeded data for the Administrators. Administrators are free to customize these categories to meet their requirements, or delete them entirely and replace with their own.
Next is the Value Set Definition form has added two additional features. One a new Usages button that shows everywhere a value set is used a Test button for Table Validated Value Sets that tests the value set for SQL errors . The Usage button opens another window which displays all descriptive flexfields, key flexfields, and concurrent programs referencing this value set. This information can be useful when a value set defintion has to be changed or deleted.
a pair. Profile values can be set for combinations of a specific server with a specific responsibility, or for only a server or responsibility with a default for the other.
While processing a request the profile value is determined as follows:
1. User level value
2. Specific Server + Specific Responsibility value
3. Specific Responsibility + Default Server value
4. Specific Server + Default Responsibility value
5. Site level value
At top level the User level value overrides all other values. Once a profile has been defined to use the Server+Responsibility hierarchy type, values can be set at this level on the Define Profile Values page.
Second one is Profile categories that can be used to classify and group related profiles together. Once a Profile category is defined, it can be used to search for profiles by category when setting or viewing profiles values. Categories are also useful for finding related profiles, by looking for other profiles grouped in the same categories. Administrators can define as many categories as per the requirement , containing any profiles. Many profile categories are available as seeded data for the Administrators. Administrators are free to customize these categories to meet their requirements, or delete them entirely and replace with their own.
Next is the Value Set Definition form has added two additional features. One a new Usages button that shows everywhere a value set is used a Test button for Table Validated Value Sets that tests the value set for SQL errors . The Usage button opens another window which displays all descriptive flexfields, key flexfields, and concurrent programs referencing this value set. This information can be useful when a value set defintion has to be changed or deleted.