This is an internal documentation. There is a good chance you’re looking for something else. See Disclaimer.
From Evaluation_node to Evaluation¶
Our qualification structure is defined by a tree of
EventQualificationAction, these are transformed into concrete
Input entities. These two trees, while related,
are technically disconnected, so any changes to the definition tree are not copied to the concrete entities. Any such changes can easily lead
to issues when not adjusted manually.
New input action¶
The new input action in React replaces the old action. It has paging and customizable forms, both of which made the old action unwieldy and slow.
It is contained in the
input-edit package and communicates mainly through the
InputEditResource. The different input types are handled by
The evaluation, aggregation and checking of all input data is done through
EvaluationTask. For each participant, all the data is passed to Drools.
The average and sum calculation rules are defined in
Drools is integrated into qualification module through the
custom-rule-header.drl. The qualification module hands of control in
A lot of code in the qualification module works with wrappers around entities. These can be found in
Qualification reports should be written with our provided directives and methods, since they are optimized for traversing tree structures.
QualificationStructureMethod to load and traverse through such a tree.
EvaluationReportDataModifier so your report can work with
Evaluation_data entities the same way.
Only work directly with the relevant entities when unavoidable.
ch.tocco.nice2.optional.qualification.impl.resources.api contains resources to control the qualification module. Check Swagger for