Implement compliance criteria

[jeremi]

Description:

We are introducing a new feature to our OpenSPP program management system: Compliance Criteria. This is conceptually similar to Enrollment Criteria, yet with operational differences.

Requirements:

1. Compliance Criteria are ongoing conditions that enrolled participants must continue to meet in order to stay active in a program and receive its benefits. Compliance checks would occur regularly at each program cycle.

2. Just like with the enrollment criteria, the compliance criteria should be flexible and customizable for each program, as different programs may have different compliance rules.

3. Technically, the compliance criteria check should be similar to that of the enrollment criteria check, but with a crucial difference: while enrollment criteria are evaluated once, compliance criteria need to be evaluated at each defined cycle or period.

Example:

In the 'cash for work' program, the enrollment criteria could be based on the unemployment status and income level, but the compliance criteria would look at whether the individual has worked the required number of days in a month.

Tasks:

1. Develop a mechanism for defining compliance criteria for each program, similar to enrollment criteria.
2. Implement regular checks for compliance at each program cycle.
3. Provide a UI to visualize the compliance or not at a given cycle for a person.

Outcome:

Fully functional compliance criteria feature that provides regular checks and validation against defined program rules.

The cron job will check the eligibility.

[jeremi]

We need to decide if we should implement this in OpenG2P or OpenSPP

[gonzalesedwin1123]

@jeremi @dasunhegoda , may I ask about the eligibility criteria. Will the "Compliance Manager" use the criteria defined in the "Eligibility Manager" to maintain consistency with the cron executed compliance criteria and the validation of eligibility available in the program and cycle buttons.

In our current setup, beneficiaries are enrolled and their eligibility are evaluated using the criterias defined in the "Eligibility Manager". In my understanding of the compliance criteria defined in this ticket, it will be a new manager (Compliance Manager) that will run at regular schedules (cron). Having a different criteria in the "Compliance Manager" and the "Entitlement Manager" will have an issue later on when the program users clicks the "Verify Eligibility" button in the program and cycle levels.

[nhatnm0612]

NOTE: 21/07/2023

• cron will not affect approved cycles

NOTE: 25/07/2023

• only edit cycles that in draft or to_approve state
• not edit the cycles where end_date is in the past

[dasunhegoda]

@gonzalesedwin1123 @nhatnm0612 : should be able to configure it when creating a program.

[nhatnm0612]

@gonzalesedwin1123 @nhatnm0612 : should be able to configure it when creating a program.

THIS COMMENT IS OUTDATED

@dasunhegoda yes, it is configurable on program creating, and also can be set after if you change your mind

[dasunhegoda]

@nhatnm0612 : Can we move it to the eligibility tab when we are creating programs?

[nhatnm0612]

@nhatnm0612 : Can we move it to the eligibility tab when we are creating programs?

yes, it can be. Well, is it a question, or a task?

[dasunhegoda]

Yes, it's better if we can move it. So it's a task. I discussed the same with @gonzalesedwin1123 too.

[celinenilla]

I have discussed with Jeremi and this should be the expected behaviour:
There should be a separate tab called " Compliance". Below this tab there should be the selection to define the compliance criteria as:

• Default
• SQL-based
• Tag-based
  UI for this should comply with UI from tab "Configure the Eligibility Criteria".

Eligibility should be determined as today, upon enrollment into the program. As for compliance we may want to make the triggering customisable (either when creating the cycle or when creating the entitlements). For now we will implement a button to trigger the eligibility manually only.

[dasunhegoda]

Noted @celinenilla!
@nhatnm0612 : Let's make the change as above.

[adriancris]

This tickets needs to fixed first since it is causing an error when it is installed. To be reassigned to @gonzalesedwin1123

[adriancris]

@nhatnm0612
When using SQL Eligibility for Compliance Criteria, it does not filter out after clicking Compliance Criteria button in Cycle. Kindly check.

[adriancris]

@nhatnm0612
Cannot generate entitlements when Compliance Criteria toggle is off.

[adriancris]

QA Passed.
Working as expected.
TCs executed:
TSOS-130, 131
TSOS-153 to 159

[adriancris]

tested and approved but actions were needed