Send case team emails as fallback for Orbit #160
Merged
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
simonmoore100
approved these changes
Dec 18, 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.
Under these changes this
notarial-apiweb hook will be removed and instead called from within the Orbit service.It will attempt to extract the form submission reference in the order:
metadata.externalReference- the Orbit case ID if the submission there was successfulmetadata.internalReference- the database record UUIDmetadata.pay.reference- the Gov.Pay payment referenceIf
metadata.externalReferenceis present and notnullit indicates a successful submission to Orbit so the case team will not be emailed. Users (applicants) will continue to be emailed in all cases and using the reference as above so their application can be identified by FCDO staff.