Troubleshooting Role and Person Information

Owned by Nancy Mond
Last updated: Jan 06, 2009Version comment
2 min read

System users such as Help Desk Support users are called upon to investigate problems with a person's access. Troubleshooting role and person information requires that the system user be able to view a person's roles, role information and information about the person, since there is a mapping between role and the access allowed. This mapping is not contained within Open Registry, at least not in the first release of Open Registry.

Actors:

  • Open Registry System
  • System User

Pre-Conditions:

  • System User MUST be authenticated with Open Registry System.
  • System User MUST have some privileges for viewing/editing role and person data.

Business Flow:

  1. The system user will provide identifiers to the system to find the person to view/edit. Based on the values of the identifiers provided, the system will present a list of matches. When displaying possible matches information about each match will be presented to enable the system user to pick the person that they wish to act on. The information supplied will vary based on the information available and the privileges of the system user. For example, not all system users are authorized to view SSN or birth date.
  2. The system user will select from among the persons listed and will go to step 3 or will go back to step 1 to adjust identifiers supplied.
  3. The system will display the data for the person selected showing only the data that the system user is authorized to view. Fields will be enabled for editing based on the privileges associated with the system user.
  4. The system user will make the necessary changes and the system will validate the data. If there are no validation errors the data will be saved.

Post Conditions:

  • Errors are logged and appropriate people notified.
  • Every data change is audited and logged for debugging purposes. Appropriate business rules are triggered based on changes.