I’ve noticed a difference between Capture (web) and Android. On Android, after completing a visit (event), users get a pop-up asking them to schedule the next visit. This comes from the option “Display generate event box when completed” when the program stage is repeatable.
In Capture, this doesn’t happen.
Since scheduling the next visit is really important for programs like NCD, ANC, etc. (especially for tracking overdue patients), I built a small plugin that lets users schedule the next visit directly within the visit form.
Right now, in Capture, users have to complete the event, go back to the enrollment dashboard, and then click to schedule the next visit. It’s a bit clunky and easy to forget.
This plugin also uses a program rule to require scheduling the next visit before completing the event.
We’ve been using it for some time, so I thought I’d share it here in case it’s useful for others.
Thank you so much for sharing example plugins with the community! This one looks great and could be helpful to enforce strict scheduling before actually completing the event.
I do want to follow up on what you said with Capture web and Android behavior differing - there are actually two “legacy” options (In Maintenance) for generating a new event after completing the previous one. There is the one you mention, “Display generate event box when completed”, but also the option “Ask user to create new event when stage is complete”. In Android, both options map to the same behavior, but in web the first option has no effect, as you said. There is this JIRA issue to remove that option completely, and in the new Metadata Management app there is only the “Ask user to create a new event after completion” option.
So if you enable that option, you will get a modal about whether to create a new event, and then taken to the page which you can choose in which stage, and then you will be taken to the new event. (Note - it currently lands on the “Report” tab, but we plan to change this to the “Schedule” tab to align with Android behavior, ref Jira
This one looks great and could be helpful to enforce strict scheduling before actually completing the event.