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

[CCAP-349] - send app when no response #680

Merged
merged 15 commits into from
Oct 17, 2024
Merged

Conversation

analoo
Copy link
Contributor

@analoo analoo commented Oct 9, 2024

🔗 Jira ticket

Link to Ticket

✍️ Description

  • Add the feature flag to existing submission actions.
    When it is off, sends an application immediately after a family submits.
    When it is on, it does not send the application immediately after the family submits it.
  • When the feature flag is on, a provider response will be populated in the PDF. Since we do not have a provider response, the preparer uses the fields that we have filled from the family and marks provider response as “No response from provider"
  • Create a new background job that waits for the provider to submit their response. If no response is received after 72 hours, then submit the application.
  • The background job runs every hour.

Tests done locally

  • When the feature flag is off, confirm that document transfer service is triggered upon submission and document upload.
  • When the feature flag is on,
    • confirm that the DTS is NOT triggered upon submission and document upload.
    • confirm that applications that HAVE NOT been transmitted after 3 business days get sent to DTS

📷 Design reference

✅ Completion tasks

  • Added relevant tests
  • Meets acceptance criteria

@enyia21 enyia21 temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 9, 2024 16:54 Inactive
@analoo analoo changed the title Ccap 349 send app when no response [CCAP-349] - send app when no response Oct 9, 2024
@enyia21 enyia21 temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 9, 2024 21:43 Inactive
@enyia21 enyia21 temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 9, 2024 22:48 Inactive
@enyia21 enyia21 temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 10, 2024 18:40 Inactive
@spokenbird spokenbird temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 10, 2024 22:28 Inactive
@enyia21 enyia21 temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 10, 2024 23:53 Inactive
@enyia21 enyia21 temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 11, 2024 18:48 Inactive
@enyia21 enyia21 temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 15, 2024 17:59 Inactive
@enyia21 enyia21 temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 16, 2024 00:09 Inactive
@analoo analoo force-pushed the CCAP-349-send-app-when-no-response branch from d08c17c to 50d0fcb Compare October 16, 2024 00:37
@enyia21 enyia21 temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 16, 2024 00:37 Inactive
@analoo analoo marked this pull request as ready for review October 16, 2024 00:39
@analoo analoo added the Open to feedback This PR isn't ready to be merged into `main` but feedback is welcome label Oct 16, 2024
@spokenbird spokenbird temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 17, 2024 19:40 Inactive
@analoo analoo added Ready For Review and removed Open to feedback This PR isn't ready to be merged into `main` but feedback is welcome labels Oct 17, 2024
@enyia21 enyia21 temporarily deployed to il-gcc-ccap-349-send-ap-6awjjd October 17, 2024 20:40 Inactive
Copy link
Contributor

@spokenbird spokenbird 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 to go!

@analoo analoo merged commit d8843bf into main Oct 17, 2024
5 checks passed
@analoo analoo deleted the CCAP-349-send-app-when-no-response branch October 17, 2024 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants