-
Notifications
You must be signed in to change notification settings - Fork 22
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
Rule is not applied until the page get refreshed #1354
Comments
2 tasks
When performing an action on the first page (default questions), the page (rules of other page elements) is not getting refreshed. For reference: My.Movie.mp4 |
@adamsanadi6 found your comment to be a different issue, so moved it to separate card: #1398 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue:
Details: When a rule C depends on B, and rule B depends on A, form element for C doesn't get updated, when A is updated. Only form element corresponding to B rule gets updated.
env : prod
org : apfodishauat
user : dineshg@apfodishauat
Steps to reproduce :
1.Login to the app
2.Register the individual
3.Try to enrol in the pregnancy program
4. we have the logic if the birth order count is 1 then we will not display the question birth spacing
Expected result : it should not display the question
Reference video :
https://github.com/avniproject/avni-client/assets/127730126/8049294d-6db4-4e6d-9af3-e3554b8d6617
Analysis:
This is because we do only one refresh on going to a page. Here the form element rules are such that, the spacing value needs to be set based on value set on
birth order
which is set by refresh on going to the pageAC:
Add documentation (in writing rules doc) that transitive dependency of rules doesn't work and rules need to be written accordingly..
old:
AC:
Form element rules for lower form elements need to execute on values of form element at higher level set during the same rules execution
Old: ignore
Add documentation to how rules need to be written. No fix needed.
The text was updated successfully, but these errors were encountered: