...
| Anchor | ||||
|---|---|---|---|---|
|
Summary
...
The Admin UI is the user interface that HEE admins use to interact with TIS. It allow them to manage the key business entities within TIS, People, Programmes, Posts, Placements and Assessments (4xP+A). The Admin UI constrains what a user can view or edit based on their Role, which groups up relatively granular set of Permissions. E.g. the standard 'HEE Admin' Role has read/write access to 4xP+A but can't view or edit sensitive data fields.
It is an Angular 5 application utilising the Bootstrap libraries.
What it does
- Provides a top menu (L1 menu) with access to People, Posts, Programmes, Concerns, Assessments and Admin sections (based on the users Role)
- Within each L1 menu dropdown, L2 items provide links to pages within each L1 section.
- Typically these consist of a 'Search' (effectively a filterable, searchable List page of records of the object in question, e.g. People) and a CRUD (Create, Read, Update, Delete) - effectively a form allowing the CRUD of an individual record of an object - e.g. a Person record.
- The List and CRUD pages will typically invoke the TCS or Assessment microservices to read, create and update data and use the Reference microservice to populate individual fields within the pages that display / search reference data
- For the more complex People and Assessment objects, a Level 3 (L3) navigation is provided - e.g. tabs within an individual Person record provide access to different data or objects directly related to that Person record (e.g. their contact details, or a list of their Programme Memberships, Placements or Assessments.) Where a list is provided within a tab, the records (e.g. Placements) are editable via an inline expanding form rather than a navigation to a full page.
- The Admin UI implements view/edit constraints for 5 Roles initially, the base HEE Admin, extensions to provide access to both Sensitive Data and Revalidation/Concerns, a full TIS Admin with access to reference data, and a Trust Admin with data access constrained to Trainees and Posts related to their Trust. Full details can be found on the Admin User Management page.
- The Admin UI was initially built using a JHipster autogeneration model and has been incrementally improved. Some elements such as the Admin sections List and CRUD pages are early versions and lacking functionality, whereas the more widely used objects such as Person/Post/Programmes have a richer interface. A full rewrite of the List functionality is currently in development initially for People which removes the last remnants of the JHipster 'scaffold'.
- The Admin UI also provides the user interface to the Document Management feature within TCS, allowing documents to be stored against a Person record with limited editable metadata.
- The Admin UI also provides the user interface to the Generic Upload microservice, more details can be found Generic Upload section
- For a user to access the Admin UI, they must authenticate via Keycloak and the Admin UI establishes their Roles and Permissions via the Profile service
TIS Core Services (TCS)
Summary
...