Form - Outcome Validation
Revision as of 20:09, 9 December 2014 by Philip Lacey (talk | contribs) (Philip Lacey moved page Outcome Validation to Form - Outcome Validation)
Revision as of 20:09, 9 December 2014 by Philip Lacey (talk | contribs) (Philip Lacey moved page Outcome Validation to Form - Outcome Validation)
Outcomes in bxp software (bxp) are incredibly powerful. One aspect of an outcome is the ability to validate data before it is saved.
Contents
1 All Forms
By default every form requires an outcome to be chosen.
2 Inbound, Outbound, Blended Forms
There is no further validation added to these form types.
3 Media Codes
When Media Codes are added and forced then then a Media Code must be chosen before the record can be saved.
4 Quality Forms
When a quality block is added to a form and set up properly in the quality options, a number of fields are automatically validated on all outcomes.
- Person: A QA has to be done against some account
- Assessor: Someone has to be adding the assessment.
- Created Date: There has to be a focus for the assessment.
- Assigned Date: Regardless there has to be some date for when the assessor knew they had an assessment to do.
- Assessed Date: The date the assessment was added to the system.