-
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
Move Thailand Production RACD Plan Generation to OpenSRP #853
Comments
Template 1
|
Template 2
|
How to post a plan template Make a POST request to The request body should contain the following { The template The
|
Tested adding a plan template and this was tested on the Thai - preview and template 1 above. see below template retrieved compared to the one posted here Retrieved template:
|
Template 1 and template 2 can be successfully added and retrieved. This has been tested by Posting the two templates and then doing a get request and comparing the response payload with that of the initial post. However there has been an issue noted on task generation where RabbitMQ was missing on thai preview.This has since been installed. |
Presently, on Thailand production environment, case triggered plans (RACD) are generated from NiFi.
In the recent past, there has been issues with plan generation. This was pointed to unavailability of nay of the 3 systems that are involved in RACD plan generation, that include OpenSRP and postgreSQL DB. As a mitigation, a recommendation was made to shift the plan generation from NiFi to OpenSRP to reduce the number of components involved in plan generation. This move is anticipated to reduce the incidents where RAC plan generation failed.
This work is anticipated to take about 3.5 weeks to complete. The technical scoping can be accessed here.
Tasks
QA
a) POST the plan templates 1 and 2 as explained here
b) For each of the templates retrive the by making a GET request t0
/rest/templates/{templateId}
c) Verify that the templates are correct
a) Insert an index case into the mhealth db
b) After 10 or so minutes check whether the plan has been created. This can be done using the web UI or a db query
c) Verify that the plan is well formed
d) verify that the correct template was used as documented here
e) verify that 2 plans were created if the index case has both a
p_site_id
and asource_site_id
. This can be checked by confirming that data inserted to mhealth DB contains p_site_id and a source_site_id.a) Assign the plan to a team and OA
b) Activate the plan
c) Verify on the android app that tasks have been genrated for all the actions available on the plan
The text was updated successfully, but these errors were encountered: