8000 Added update_multi field for FormActions by mjriley · Pull Request #36471 · dimagi/commcare-hq · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Added update_multi field for FormActions #36471

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mjriley
Copy link
Contributor
@mjriley mjriley commented May 21, 2025

Product Description

Technical Summary

Associated ticket: https://dimagi.atlassian.net/browse/SAAS-17568.
This just creates the field to make saving multiple questions to a single case property possible. It also introduces utility functions to eventually allow us to use update_multi as a substitute for update, even for actions that don't save multiple questions to a single case property. However, it does not introduce any logic allowing for this yet. Anything that would break current behavior will be introduced behind a feature flag.

Feature Flag

No current feature flag, but the follow-up work will be feature-flagged.

Safety Assurance

Safety story

The new field is unused by current code, so it shouldn't pose a safety risk

Automated test coverage

New test suite for the utility functions

QA Plan

No QA

Rollback instructions

  • This PR can be reverted after deploy with no further considerations

Labels & Review

  • Risk label is set correctly
  • The set of people pinged as reviewers is appropriate for the level of risk of the change

@mjriley mjriley requested review from biyeun, jingcheng16 and nospame May 21, 2025 17:58
@mjriley mjriley requested a review from orangejenny as a code owner May 21, 2025 17:58
@mjriley mjriley added the product/invisible Change has no end-user visible impact label May 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product/invisible Change has no end-user visible impact
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0