We’re experiencing a critical issue with our quality inspection workflow in GPSF 2021. When incoming material fails a quality check, the system is not automatically triggering the nonconformance record creation process.
The workflow event mapping appears correct in the workflow editor - we have the inspection result handler configured to evaluate the pass/fail status. However, failed inspections just complete without generating the required NCR. We’ve verified that the inspection results are being recorded properly in the quality-mgmt module, but the workflow transition to nonconformance handling never fires.
This is creating significant compliance risks as failed materials are potentially moving forward in production without proper documentation. We need to understand why the event mapping between inspection results and nonconformance record creation isn’t working as designed.
That makes sense. Where exactly would I configure the data output format for inspection results? I’m looking in the quality-mgmt module settings but not finding the specific option for workflow data mapping.
In GPSF 2021, you’ll find this under Quality Management > Inspection Configuration > Result Attributes. There’s a section for workflow integration where you can map inspection result fields to workflow context variables. Make sure the ‘InspectionStatus’ attribute is mapped and set to publish on completion. Also verify that your workflow is subscribed to the correct event type - it should be listening for ‘InspectionComplete’ events, not just generic quality events.
I’d also recommend checking the event subscription filter on your workflow. Sometimes the issue isn’t with data mapping but with event filtering that’s too restrictive. Your workflow might be filtering out failed inspections unintentionally.
Based on the symptoms you’re describing, here’s a comprehensive solution addressing all three critical areas:
Workflow Event Mapping Fix:
First, verify your workflow is subscribed to the correct event. Navigate to Workflow Editor > [Your Workflow] > Event Triggers. Ensure you have ‘InspectionComplete’ as a trigger event, not just ‘QualityCheckComplete’. The distinction matters because inspection results publish to a different event stream than general quality checks.
Inspection Result Handling Configuration:
Go to Quality Management > Inspection Configuration > Result Attributes. You need to configure the data mapping for workflow integration:
- Locate the ‘InspectionStatus’ attribute
- Enable ‘Publish to Workflow Context’ checkbox
- Set the mapping name to ‘inspection_result_status’
- Ensure ‘Trigger on Value Change’ is enabled
- Add ‘FAIL’ to the list of trigger values
This ensures that when an inspection fails, the status is properly published to the workflow engine with the correct attribute name.
Nonconformance Record Creation Link:
In your workflow editor, examine the transition from your inspection evaluation node to the NCR creation node. The condition should be:
- Condition Type: Attribute Evaluation
- Attribute: inspection_result_status (matching the mapping name above)
- Operator: Equals
- Value: ‘FAIL’
- Action: Trigger NCR Creation Process
Additionally, verify that the NCR creation node has ‘Auto-populate from Context’ enabled so it can pull inspection details into the nonconformance record automatically.
Validation Steps:
After making these changes:
- Run a test inspection with known failure criteria
- Check workflow execution logs (Workflow Monitor > Execution History)
- Verify the event was received and the condition evaluated correctly
- Confirm NCR was created with proper linkage to the failed inspection
The root cause is typically the mismatch between how inspection results publish data and what the workflow expects to receive. By aligning the attribute mapping and ensuring proper event subscription, the workflow will correctly trigger nonconformance handling for failed inspections.
This sounds like a common issue with result data mapping. The inspection module needs to publish the result status in a format the workflow engine can consume. Check your inspection result configuration - specifically the data output format. The workflow is probably not receiving the pass/fail flag in the expected attribute. You might need to add a custom data mapping rule in the quality-mgmt configuration to ensure the result status is properly exposed to workflow event handlers.