...

Relevant Resources

• 2024-01-22 - 2024-01-26 openIMIS/CORE-MIS Developers Workshop

• 2023-05-08 - 2023-05-12 openIMIS/CORE-MIS Developers Workshop

• Project: 2023.T3 CORE-MIS Merger

• Project: 2022.T3 CORE-MIS Merger

• https://openimis.atlassian.net/wiki/spaces/coremis

...

2. Groups

   1. Create a group of individuals

      1. there must be a possibility to move a certain individual from one group to another

      2. changes group for many individuals should happen with a imported file → then the task as for data update shall be created

      3. option to create a new group from UI on the “Change group” modal (it’s displayed once you want to change a group for a particular individual)

      4. bulk upload - once user will be uploading data of individuals and indicated group will not exists system must create a new one with the name inidacted in the uploaded file

   2. Edit groups via UI

      1. no criteria at this point; any individual may belong to any group

   3. Modify group head and other data parameters

   4. photo

      1. for MVP purpose we can proceed with only 1 foto attached to Individual

      2. ability to add photos of individual through the bulk upload - that’s the priority

3. Programs

   1. View beneficiaries that belong to a program, under POTENTIAL, ACTIVE, SUSPENDED and GRADUATED

      1. There needs to be a link to a task for easier identification

      2. We need to make the process of identifing tasks easier as currently it’s too complicated

      3. Keep the search critieria detailes once we route back (search criteria on core-mis related modules)

   2. Update beneficiaries between statuses, also require a reason the update happened

      1. We need to keep the change log for beneficiary data update. It shall be visible on beneficiary detailed page. The goal is to visualize all the changes made for beneficiary on benefit plan level

   3. Everything that was deleted has to be read only.

   4. Include maker-checker logic on benefit plan deletion

4. Data updates

   1. Add a label to distinguish what data is old and what is new

   2. Dash cannot indicate that there is no change in the data since it’s confusing. Instead we need to repeat the previous data (not changed one) and those which are requested to be updated are changed to new one and highlighed

   3. Have a timestamp of that change (new column) and order it from the most recent one

   4. We need to change the way of how the tasks are currently assign for a tast executioner group. it has to be set in a config to have a specific execution group assign to task group by default. We can choose any other suitable way to handle that. Ideally, we can create a right that will be assign to a task group on the UI and once user has a particular right assign, it will be automatically granted the permission to approve/reject task

Program Graduation

• Mark a program as closed and mark all beneficiaries as graduated

...