5.2.2 Defining the User Access Properties and Relationships
The following types of data compose a user’s security configuration:
- Business Domain(s): Property that enables an Oracle client to model client data along operational business lines and practices.
- Jurisdiction(s): Property that enables an Oracle client to model client data across such attributes as geographic location or type or category of a business entity.
- Role(s): Permissions or authorizations assigned to a user in the system (such as, Oracle administrator or Auditor).
The following table provides the relationships between the data points that Figure 8 illustrates.
Table 5-2 Relationships between Data Points
| Data Point | Relationship |
|---|---|
| Role | Associated with 0..n Users |
| Has no direct relationship with an Organization | |
| User | Associated with 1..n Business Domains |
| Associated with 1..n Jurisdictions | |
| Associated with 1..n Roles | |
| Associated with 1..n Scenario Groups | |
| Associated with 1..n Case Type/Subtypes | |
| Associated with 1..n Organizations (as members) | |
Associated with one Organization (as
mantasLineOrgMember)
|
|
| Business Domains | Associated to 0..n users |
| Business domain keymust be in the KDD_BUS_DMN table | |
| Jurisdiction | Associated to 0..n users |
| Jurisdiction keymust exist in the KDD_JRSDCN table |