-
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
Edit Rule #1273
Comments
@vinayvenu final review this also |
Not Implemented
|
… removed uglify to help with debugging.
Scope: Different places where from edit form can be launched
Out of scope
Additional Acceptance Criteria
For testing - Valid Disallow Rule
For testing - Valid Allow Rule
For testing - Invalid Rule (should create rule failure telemetry record in the database
|
… element group edit for program encounter and general encounter.
Screen.Recording.2024-02-27.at.3.31.23.PM.movScreen.Recording.2024-02-27.at.3.32.06.PM.mov |
… "Draft/Scheduled" encounters "Do" button.
https://avni.readme.io/docs/rules-concept-guide#edit-form-rule
(also linked from writing rule page)
…On Thu, Feb 29, 2024 at 2:31 PM Himesh ***@***.***> wrote:
Scope:
Different places where from edit form can be launched
1. Registration
2. Enrolment
3. Enrolment Exit
4. Program Encounter
5. Program Encounter Cancel
6. General Encounter
7. General Encounter Cancel
8. Group Subject Registration
9. Form Element Group Edit
10. Checklist Item
Out of scope
1. Location (as it is not transaction data)
2. Task (there is no edit screen for it)
3. BeneficiaryIdentification (not clear what this is for)
4. SubjectEnrolmentEligibility
5. ManualProgramEnrolmentEligibility
6. Encounter Drafts (Should always be editable)
7. Scheduled Encounters (Should always be doable)
Additional Acceptance Criteria
- Rule Failure Telemetry Failure should be saved correctly.
For testing - Valid Disallow Rule
"use strict"; ({params, imports}) => { const {entity, form, services,
entityContext, myUserGroups, userInfo} = params; const output = { editable:
{ value: false, messageKey: "foo" } }; return output; };
For testing - Valid Allow Rule
"use strict"; ({params, imports}) => { const {entity, form, services,
entityContext, myUserGroups, userInfo} = params; const output = { editable:
{ value: true } }; return output; };
For testing - Invalid Rule (should create rule failure telemetry record in
the database
"use strict"; ({params, imports}) => { undefined.foo(); };
@petmongrels <https://github.com/petmongrels> shouldn't we include all
this information in the readme documentation.?
—
Reply to this email directly, view it on GitHub
<#1273 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAZ3C7USY5YXGKFL57J37TYV3W7JAVCNFSM6AAAAABBUO46HOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGY4TKMZUGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Vivek Singh | +91 98452 32929 | @petmongrels
<https://twitter.com/petmongrels>
|
|
|
|
@AchalaBelokar its not decision rule, its edit form rule
|
Checklist item is out of scope. |
Need:
Acceptance criteria:
One of the test cases:
Disable edit of subject, encounter, and enrolment after 24 hours of encounterDateTime in TeachAP app.
The text was updated successfully, but these errors were encountered: