You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
The story covers the work needed to provide the ability for an admin-type user to configure/set up email content for communicating request updates to subjects.
Assumptions
No dynamic values in email content for now.
Acceptance Criteria
Demonstrate that a user has the ability to navigate to a location where they can configure communications for their request types --this will be done by adding a "More" dropdown option on the Subject Request landing page. --only users with the privileges to manage subject requests privileges should be able to see this "more" dropdown. Users without that privilege should not be able to see the "more" dropdown at all.
Demonstrate that a user can select which request type to configure communications for --the number and type of communications to configure should match the number of policies that the organization supports. (e.g. if the PC allows users to submit just access requests, then there should only be a way to configure communications for access requests) (CONFIRM THIS WITH DESIGN)
Demonstrate that a user can input a different email subject and body for each phase of the request.
Confirm that a user can save the communication content.
Confirm that an audit log is created when a user saves a new version of the email communications.
Description
The story covers the work needed to provide the ability for an admin-type user to configure/set up email content for communicating request updates to subjects.
Assumptions
Acceptance Criteria
Mockups
Figma
The text was updated successfully, but these errors were encountered: