Principals
UWL enables you to associate a variety of UWL configurations to different principals (user, role, or group). The XML configuration is assigned to a particular role or group by assigning a value to the Principal element's attribute uniqueID. In case the logged on user is assigned to the same role or group, the respective XML configuration is matched at runtime and becomes effective. Thus, the user sees the outlook and tasks table associated with the particular UWL configuration. You manage users in the portal's User Management .
You assign a principal to an XML configuration. To identify a principal, its uniqueID should be defined as the only attribute of a Principal tag in the XML configuration file. The Principal tag in the XML can contain several {1..n} principals. The UWL XML configuration files are uploaded in the portal's UWL Administration .
For more information, see:
Administration and Configuration
Below is an example UWL XML configuration with a defined principal:
<?XML version="1.0" encoding="UTF-8"?>
<!DOCTYPE UWLConfiguration PUBLIC '-//SAP//UWL1.0//EN' 'uwl_configuration.dtd'>
<UWLConfiguration version="1.0">
<Principals>
<Principal uniqueID="ROLE.UME_ROLE_PERSISTENCE.un:examplePrincipalRole" />
</Principals>
<Views>
........
</Views>
Conflicting configurations are resolved as follows:
-
Configuration priority
-
Logged user matches the principal that is defined in the XML configuration
-
Alphabetical order/prefixing (used only for configurations with the same principal defined)
For example, if XML A 's name is Configuration and XML B 's name is UWL Configuration , XML B is placed further down the alphabetical order list than XML A .
Below is summary of the possible outcomes of conflicting configurations.
Scenario 1
|
Priority |
Principal |
User |
Description |
|
|
XML A |
Medium |
Role A |
Role A |
- XML A and XML B have the same names - user A is logged on |
|
XML B |
High |
Role B |
Procedure
-
In the UWL Administration , upload XML A .
UWL and the task list are displayed according to XML A .
-
In the UWL Administration, upload XML B .
Result
UWL and the task list are displayed according to XML B . The UWL configuration of XML B overwrites the configuration of XML A because XML B has higher priority.
Scenario 2
|
Priority |
Principal |
User |
Description |
|
|
XML A |
Medium |
Role A |
Role A |
- user A is logged on |
|
XML B |
Medium |
Role B |
Procedure
-
In the UWL Administration , upload XML A .
UWL and the task list are displayed according to XML A .
-
In the UWL Administration, upload XML B .
Result
UWL and the task list are displayed according to XML A . The logged on user A matches the principal defined in XML A 's configuration.
Scenario 3
|
Priority |
Principal |
User |
Description |
|
|
XML A |
Medium |
Role A |
Role A and Role B |
- XML A's name is, for example, Alpha - XML B's name is, for example, Beta - user A is logged on - user A matches both principals |
|
XML B |
Medium |
Role B |
Procedure
-
In the UWL Administration , upload XML A .
UWL and the task list are displayed according to XML A .
-
In the UWL Administration, upload XML B .
Result
UWL and the task list are displayed according to XML B . The UWL configuration of XML B overwrites the configuration of XML A because XML B 's name starts with B ( Beta ), which is below A ( Alpha ) in alphabetic order, in other words, it is of greater alphabetical "value".
Scenario 4
|
Priority |
Principal |
User |
Description |
|
|
XML A |
Medium |
Role A |
Role A |
- XML A's name is, for example, Alpha - XML B's name is, for example, Beta - user A is logged on - user A matches only one principal |
|
XML B |
Medium |
Role B |
Procedure
-
In the UWL Administration , upload XML A .
UWL and the task list are displayed according to XML A .
-
In the UWL Administration, upload XML B .
Result
UWL and the task list are displayed according to XML B . The UWL configuration of XML B overwrites the configuration of XML A because XML B 's name starts with B ( Beta ), which is below A ( Alpha ) in alphabetic order, in other words, it is of greater alphabetical "value".
Scenario 5
|
Priority |
Principal |
User |
Description |
|
|
XML A |
Medium |
Role A |
Role B |
- user B is logged on - user B does not match the principal in XML A |
|
XML B |
High |
No principal defined |
Procedure
-
In the UWL Administration , upload XML A .
UWL and the task list are displayed according to XML A .
-
In the UWL Administration, upload XML B .
Result
UWL and the task list are displayed according to XML B . The UWL configuration of XML B overwrites the configuration of XML A because XML B has higher priority.