[CCAP-464] Temporarily fix PDF download by adding confirmation code screen to new provider flow #919
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…creen to new provider flow
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
.../resources/templates/providerresponse/temporary-provider-response-confirmation-code-fix.html
Dismissed
Show dismissed
Hide dismissed
cram-cfa
approved these changes
Dec 16, 2024
analoo
approved these changes
Dec 16, 2024
cram-cfa
approved these changes
Dec 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔗 Jira ticket
CCAP-464
✍️ Description
Temporarily adds the confirmation code screen to the new provider registration flow so that we can download the PDF for acceptance testing in that flow.
The confirmation code is needed because it's how we pull the family submission data for PDF generation.
Note the changes in this PR should be removed / replaced with a long term solution for this once we have one.