Process Hub · Workflows and approvals
Create non-conformity work from failed answers
Identify failed checks and map them into a corrective-action record with evidence and ownership.
On this page
Before you start
- Deploy a destination non-conformity process with the required repeated Failed checks section and compatible fields. Have edit, automation and publication access.
Numeric ranges
Choose the exact comparison the business requires. An outside-range rule treats its configured range as inclusive. Test both boundary values and values immediately beyond them.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Open the source process → Fields & questions → the field Settings → Failure detection. Enable Identify failed answers.
- Define failure for the supported type: the failed Yes/No answer, failed Choice options, or the appropriate numeric comparison/range for Number, Rating or Slider.
- Keep required-answer validation separate. Test failed, passed, unanswered and hidden/branched-out questions; unanswered or inapplicable questions do not count as failed answers.
- Open Workflow chains and configure a Non-conformity on failed answers link to the deployed destination. Choose one non-conformity containing all failed checks or one per failed answer.

Identify which answers count as failures and map the follow-up evidence to the intended destination fields. - Map source context to header fields and failed-answer evidence to repeated Failed checks rows. Configure enabled follow-up work, assignment and due date; select any optional evidence behaviour deliberately.
- Save and publish/release the chain, and publish/deploy any changed source failure settings. Submit a test source record with two failures and inspect the destination rows and assigned work.
- Submit a passing record and save a failing draft without submitting. Confirm neither creates the failed-answer follow-up expected only on successful submission.
Example: packaging quality check
NovaNest checks “Seal intact?” and “Label correct?”. Configure No as failure for each. Submit No/No and expect one non-conformity with two Failed checks rows in the default grouped mode, assigned to Quality. Submit Yes/Yes and expect no non-conformity.
What you should see
A successfully submitted record with failed checks creates the configured non-conformity work and preserves which answers failed.
If something goes wrong
Draft saves create no corrective work
The failed-answer flow runs on successful submission, not every draft save.
Several unrelated forms do not combine into one follow-up
Group AND/OR rules operate within the same workflow run and distinct participating processes. Unrelated Add New records are not automatically paired.
A required blank answer creates no failure row
Blank validation and business failure detection are different. Correct the missing required answer before submission.