JIRA reference: FT-332
High Level Requirements
Give the applicant the ability to grant a colleague (must have a UH username) access to review their dossier prior to the application submittal deadline.
Database changes
Add role COLLEAGUE
Icon placement and action
- add Share icon after the Edit icon
- The icon must only display when the status of the application is In Progress. It must not display at any other status.
- When the icon is clicked, display a modal that takes in the UH Number, UH username or email address (UH only)
- Validate the UH Number, Username or Email Address against LDAP and prevent the applicant from adding someone not in the UH system
- Add standard Cancel and Save buttons to the dialog
- Add status bar when the Save is clicked so processing can complete
- Post click actions
- Add the colleague as a READER to the shared drive
- Add the permissions ID to the TnP database table
- Add the colleague to the APPLICATION_ROLE table with role COLLEAGUE
- Log the action (
create action ID) - Email the colleague when access is granted (See Colleague Review template)
Colleague Actions
- On the main menu, they are able to view applications for which they have role COLLEAGUE
- In the application, they have read-only access to the Eligibility and Dossier tabs; they must not see any other tabs
Potential Risks
There's no listing of Colleagues that the applicant or ITS can manage. What happens if a colleague is added twice?
This spec doesn't account for removing a colleague (if added in error for example). When the application is submitted, the system will remove everyone from the shared drive but will it remove colleagues as well?