Preferred Name
Last updated
Was this helpful?
Last updated
Was this helpful?
This Application allows users to change their Preferred Name and Email Address. The users fills out a form where they can request to change their first-name, last-name, or both names, whatever change they request in this form will also change their email address first-name.lastname@boston.gov if users belong to the BPL or BPHC agencies only their name will be updated. For users in the BPL or BPHC agencies the app will skip the confirmation screen.
On the Enter Name view, on submit a request is send to the node server route /preferred-name-request
This route constructs params needed to make request to the [PREFERRED NAME] WORKFLOW
endpoint URL
requestJson
authorization token
The params are sent to requestNewNameEmail function on line that will connect to the WORKFLOW and return the new name and/or email
IF the user belongs to the BPL or BPHC agencies
The UI/UX send the request to the /preferred-name-submit ROUTE. This route method submit a request to the WORKFLOW endpoint to change the users name and/or displayname. For these users only their names will be requested to change. The SUCCESS/ERROR view are displayed after depending on the result from the WORKFLOW.
ELSE ^ ... The App displays the next VIEW (Confirmation), use to confirm the user's changes and displays the new Email Address composed from the (first/last) name entered in the previous view.
SUBMMITTING the request from Confirmation view will send the request to the /preferred-name-submit ROUTE, the route will use step 3 (above), SUCCESS/ERROR view are displayed after depending on the result from the WORKFLOW.
(Node) Server
Routes
Request a new Name
Submit new Name and/or Email Request
provided the Security Team
path:
line: Route Request Method
path:
line: Route Request Method