Add backend support for handling case mappings within Form Builder #37109
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.
Product Description
Technical Summary
This is the HQ half of the Form Builder changes. This modifies the context we send down to Vellum so that Vellum's case management plugin has access to the current mappings and the case property suggestions.
Case property suggestions are populated by calling
get_all_case_properties_for_case_type. It should be noted that this can be very slow, especially on large domains. It is currently the same call used within the data cleaning tool and the case management page, but because the use case of form builder is different, the slowness with this call is more severe here and likely requires a followup improvement. For these reasons, I'm considering this a "High Risk" PR until this changes (and would not suggest releasing it as is).Feature Flag
saas_formbuilder_save_to_caseSafety Assurance
Safety story
Tested locally, on staging, and run through QA.
Automated test coverage
Various test suites added
QA Plan
Currently running through QA
Rollback instructions
Labels & Review