Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PI1.3 26084: Withdraw Package screen and email messaging #1400

Merged
merged 9 commits into from
Nov 8, 2023

Conversation

kristin-at-theta
Copy link
Collaborator

@kristin-at-theta kristin-at-theta commented Oct 31, 2023

Story: https://qmacbis.atlassian.net/browse/OY2-26084
Endpoint: Click here

Details

After seeing the demo of the RAI Response Withdraw process, our Business Owners wanted to change some of the language around Package Withdrawal to make it more specific to the user and better differentiate it from RAI Response Withdraw.

Changes

  • Followed the ONEMAC_LABEL[parentType] pattern used in the Type field on the Withdraw form as the for this story
  • Updated Introductory text on Withdraw Package forms (now includes the package type)
  • Updated submit confirmation heading and text for Withdraw Package form.
  • Updated email receipt sent to state user upon successful Withdrawal Request submission.
  • ALSO fixed two warnings/errors in validateUser and getMyPackages (territoryList === [] no longer works)
  • ALSO added some TE seed data so the first build TE tests don't fail.

Test Plan

  1. Login as a state submitter user for whom you have email access
  2. Navigate to Dashboard
  3. For any package type that can be withdrawn (all but TEs):
    a. Find a package of that type with "Withdraw Package" as an available action
    b. Verify the Intro text on the withdraw form matches the AC
    c. Complete form and click Submit
    d. Verify the Confirmation Heading and text match the AC
    e. Confirm the Submit
    f. Verify the email matches the AC.

Copy link

Endpoint URL - https://d2pw7kqcao5lf0.cloudfront.net

@kristin-at-theta kristin-at-theta marked this pull request as ready for review October 31, 2023 18:18
Copy link
Collaborator

@bflynn-cms bflynn-cms left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good and new text follows ACs.

Approved.

@kristin-at-theta kristin-at-theta merged commit 159d0e9 into develop Nov 8, 2023
90 of 92 checks passed
@kristin-at-theta kristin-at-theta deleted the pi1-26084 branch November 8, 2023 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants