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

Create alert message for overdue requests #34452

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jenniemc
Copy link
Contributor

@jenniemc jenniemc commented Feb 2, 2025

Are you removing, renaming or moving a folder in this PR?

  • No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
  • Yes, I'm removing, renaming or moving a folder

⚠️ TeamSites ⚠️

Examples of a TeamSite: https://va.gov/health and https://benefits.va.gov/benefits/. This scenario is also referred to as the "injected" header and footer. You can reach out in the #sitewide-public-websites Slack channel for questions.

Did you change site-wide styles, platform utilities or other infrastructure?

Summary

This PR shows alert message when there has not been any response to user's CC and VA pending requests.

  1. On pending CC and VA requests, include the date the request was made.
  2. On the 4th business day and beyond, display a warning message to the user to ask the Veteran to call their facility to schedule the appointment along with the date that the request was made.
  3. Use the date-dfs date utility library

Related issue(s)

Testing done

unit test and e2e test

Screenshots

Note: This field is mandatory for UI changes (non-component work should NOT have screenshots).

Before After
Request Detail Screenshot 2025-02-02 at 10 57 53 AM Screenshot 2025-02-02 at 10 31 18 PM
Request Past Due Screenshot 2025-02-02 at 11 01 45 AM Screenshot 2025-02-02 at 10 32 27 PM

What areas of the site does it impact?

Alert messages for CC and VA requests

Acceptance criteria

Matches Figma design

Quality Assurance & Testing

  • I fixed|updated|added unit tests and integration tests for each feature (if applicable).
  • No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
  • Linting warnings have been addressed
  • Documentation has been updated (link to documentation *if necessary)
  • Screenshot of the developed feature is added
  • Accessibility testing has been performed

Error Handling

  • Browser console contains no warnings or errors.
  • Events are being sent to the appropriate logging solution
  • Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

  • Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

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.

2 participants