Page Comparison

...

The PCA currently does not support In-app creation of custom Program Rules, meaning that the standard Program Rules management in the DHIS2 Maintenance App is required for this. However, the custom Program Rules are displayed in the PCA as described in the Checking Existing Program Rules page.

...

The Excel Template is the main way to define Program Logic in H2 Assessments, allowing for easy configuration of Parent Questions (Hide/Show logic), label creation, scoring calculations, and
much more (see Image 2). You can check how to use the Excel Template here.

...

After importing the Excel Template with the desired changes, the Program Rules can be generated by using the Set Up Program button.

...

The configuration is mostly the same as the Hide/Show Program Rules, basically only changing the Program Rule Name and the Program Rule Actions (see Images 8 and 9).

...

Also, the condition would be the same as the Hide/Show rules without inverting the logic (see Image 10) without inverting the logic.

...

With that new set of Program Rules, Mandatory Child Questions are no longer an issue.

...

The first one being used for calculating and debugging, and the second one being used to present the result to the supervisor during the Assessment.

Competency Class

If a H2 Program has been configured to include Competency Classes, the PCA will also generate five additional Program Rules to handle the Competency Class definition and assignment (see Image 17).

...

Three of the rules are used to define the Competency Class and assign it to the Competency Class Data Element located in the Critical Steps Calculations section. The rules are named as follows:

To learn more about the contents of these Program Rules please refer to the H2 Competency Classes page.

Another Program Rule is generated to assign the value stored in the Competency Class Data Element into the Competency Class Attribute of the Tracked Entity Instance (see Image 18).

...

The rule is named as follows:

Then, the PCA generates another Program Rule to Hide the Global Score and Competency Class

...

WIPAttributes of the Tracked Entity Instance if the Critical and Non-critical Scores are not defined. The rule is named as follows:

If a H2 Program hasn’t been configured to use Competency Classes, the previous Program Rule will be generated to hide only the Global Score Attribute, and will be named as follows:

Overall Score

The Overall Score isn’t a calculation like the Critical and Non-critical Scores, it is basically a copy of the value contained in the Critical Steps or Non-critical Steps.

...

This rule assigns either the Critical Steps or the Non-critical Steps value to the Global Score attribute of the Tracked Entity Instance (see Image 1719).

...

Compositive Score

The Compositive Scores are scores that group questions by using the Feedback Order, for example, Compositive Score 1 is calculated using every question or Sub-score derived from the Score 1, which means that:

...

The PCA will generate all the necessary Score Calculations Program Rules by using the Feedback Order, Score Numerator and Denominator and Answer Value of each answered question (see Images 18 20 and 1921). This means that if a question has been left unanswered, it won’t be taken into account for the Score Calculation.

...

Then, another Program Rule is generated for each Score, used for rounding the Calculated Score and storing it in a Data Element present in the Assessment (see Images 20 22 and 2123).

...

These rules are named as following:

...

The PCA uses Program Rule Variables to reference Data Elements contained in the Assessment, and also to store temporary Calculated Values such as Scores (see Image 2224).

...

Similarily to the Program Rules, the variables are identified as scripted when the variable name starts with a underscore (_). The Variables follow some naming conventions:

...

...