-
Sub-task
-
Resolution: Done
-
Major
-
False
-
False
-
Undefined
-
The use of Reason Codes, Baseline Scores and Partial scores needs validating.
There is rudimentary implementation of showing/hiding fields already committed; however there is no validation nor reporting of errors yet. This JIRA tracks implementation of
the missing parts as better explained in the "PMML Scorecard Validations" document
The following validations are covered:
- Model Setup: when Use Reason Codes is Yes, a baseline score is required in the model setup or in all the existing characteristics
- Characteristic: when Use Reason Codes is Yes inside Model Setup, all characteristics must have a reason code. Alternatively it's possible to provide a reason code for all the attributes of a characteristic and avoid providing it at the characteristic level.
- Characteristic: when Use Reason Codes is Yes inside Model Setup and a Baseline score is not provided there, a baseline score must be provided for all the characteristics
- Attributes inside Characteristics: if one attribute has a partial score then partial score must be provided for all the attributes of the same characteristic
- Attributes inside Characteristics: Reason code is required if the parent Characteristic doesn't have one and Use reason codes is set to Yes inside the Model Setup
Notes about disabled fields:
- Characteristics/Attributes: If Use Reason Code is No inside Model Setup, reason code fields inside Characteristics and Attributes are disabled because reason codes don't make sense in this scenario
- Characteristics/Model Setup: Baseline score was previously disabled/unavailable when Use Reason Code is No inside Model Setup. We discovered it's still possible to provide a score for Characteristics in this scenario, so baseline score fields are now always editable