Back and Cancel Button Behaviour

[zoeyli-46]

Description:

Refer to this Figma for guidance on where to use a Cancel button versus a Back button.

Acceptance Criteria:

Cancel button should appear after user clicked Add, so that users can "cancel" accidentally creating something.
Cancel button should appear on where the user was "viewing" something and now they clicked "edit", so they can cancel accidentally editing something they already submitted/saved.

Back should appear when viewing something, (i.e., they clicked View Details), or when submitting something i.e., on View Details for a contact

Given that I clicked View Details,
Then the button says Back

Given that I clicked Edit or Add
Then the button says Cancel

Development Checklist:

• Checklist item
• Checklist item
• Checklist item
• Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

• User story is included
• User role and type are identified
• Acceptance criteria are included
• Wireframes are included (if required)
• Design / Solution is accepted by Product Owner
• Dependencies are identified (technical, business, regulatory/policy)
• Story has been estimated (under 13 pts)

Definition of Done (Note: If any of these points are not applicable, mark N/A)

• Acceptance criteria are tested by the CI pipeline
• UI meets accessibility requirements
• Configuration changes are documented, documentation and designs are updated
• Passes code peer-review
• Passes QA of Acceptance Criteria with verification in Dev and Test
• Ticket is ready to be merged to main branch
• Can be demoed in Sprint Review
• Bugs or future work cards are identified and created
• Reviewed and approved by Product Owner

Notes:

[zoeyli-46]

@patriciarussellCAS I've added this ticket for the back/cancel button behaviour. For reporting, we've implemented this behaviour already but in registration its not done yet. This is related to what Tiegan flagged as a concern during UAT, about the placement of "cancel" buttons/