You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
With the increased number of first order operational models managed by Registry, it is increasingly important to have a consistent language of menuing to make it easier for users to find the tasks that they need to perform.
Proposal: The primary menus split his operation versus configuration. Operational tasks should be accessible from the left side ("main") menu, either directly or with one additional click. Configuration tasks, which are performed less frequently, should be accessible via the configuration menu (under the main menu).
This table itemizes current (as of v3.1.0) and future operational and configurational models, and identifies the current misalignments in bold red.
| Operational | Configurational1 |
|---|
- CoPerson, CoPersonRole, and associated models
- Should "My Identity" move to the main menu?
- Search should be easier to access
- Enrollment and CoPetition
- OrgIdentity, and associated models
- Search should be easier to access
- Authenticator
- CoCluster (future)
- CoDepartment (new)
- CoGroup
- CoJob (new)
- CoService Portal
- Report (future)
| - Authenticator (new)
- Cou
- CoEmailList (new)
- CoEnrollmentFlow
- CoExpirationPolicy
- CoExtendedAttribute
- CoExtendedType
- CoIdentifierAssignment
- CoIdentifierValidator
- CoLocalization
- CoMessageTemplate
- CoNavigationLink
- CoPipeline
- CoProvisioningTarget
- CoSelfServicePermission
- CoService
- CoSetting
- CoTermsAndConditions
- CoTheme
- OrgIdentitySource
- Search should be accessible via the main menu
|
1CO, not CMP level