Incident reporting workflow fails to trigger corrective action tasks after approval

QMS MasterControl Quality Excellence
, , , , , , , ,
1

Our incident management workflow has a serious gap. After an incident report goes through review and gets approved, the workflow should automatically create corrective action tasks and assign them to the appropriate department owners. However, these tasks are never being created.

I’ve confirmed that incidents are being approved successfully and moving to ‘Approved’ status, but the subsequent task generation step isn’t executing. This is creating an audit gap because we have approved incidents with no documented follow-up actions.

The workflow template has a task creation step configured after the approval step, and I can see the task assignment rules are defined. Could this be an issue with how the workflow template steps are sequenced, or is there something wrong with the user group activation for task assignment?

2

Check if the transition from the approval step to the task creation step has the correct conditions. The transition might be configured to skip the task step if certain criteria aren’t met. Go to your workflow template and examine the transition rules between ‘Approved’ and ‘Create Tasks’ steps.

3

Also verify that your task template is properly configured. Go to Admin > Task Templates and open the template referenced in your workflow action. Make sure it has:

  • Valid task type selected
  • Due date calculation formula (e.g., +7 days from creation)
  • Required fields defined
  • Task priority set

An incomplete task template can cause silent task creation failures even when everything else is configured correctly.

4

Good catch! I found that the ‘Create Task’ action exists and is enabled, but the ‘Assignment Method’ dropdown shows ‘No user groups available’. This must be the problem - the task can’t be created if there’s nowhere to assign it. How do I configure the user groups for task assignment?

5

I’ve seen this before - the task creation action might be configured but not actually enabled. In the workflow step properties for your task creation step, there should be an ‘Actions’ section. Verify that:

  1. ‘Create Task’ action exists
  2. The action is enabled (checkbox)
  3. Task template is selected
  4. Assignment method is configured

If any of these are missing, tasks won’t be created even though the workflow step executes.

6

I’ll walk you through a complete solution that addresses all the components needed for automatic task creation in your incident workflow.

Workflow Template Steps Sequencing: First, let’s ensure your workflow template has the correct step sequence and transitions:

  1. Navigate to Admin > Workflow Templates > Incident Management Workflow

  2. Verify your workflow has these steps in order:

    • Submit Incident
    • Under Review
    • Pending Approval
    • Approved (current end point)
    • Create Corrective Actions (missing or skipped step)
    • Closed

  3. Check the transition from ‘Approved’ to ‘Create Corrective Actions’:

    • Transition Name: ‘On Approval’
    • Trigger: Automatic (not manual)
    • Condition: Status = ‘Approved’ (no additional conditions that might block execution)
    • Delay: None (should execute immediately)

  4. If the ‘Create Corrective Actions’ step doesn’t exist, add it:

    • Click ‘Add Step’ after the Approved step
    • Step Type: ‘Action Step’
    • Step Name: ‘Create Corrective Actions’
    • Entry Action: ‘Create Tasks’

Task Assignment Rules Configuration: Now configure the task creation action within the workflow step:

  1. Open the ‘Create Corrective Actions’ step properties

  2. Navigate to the ‘Actions’ tab

  3. Click ‘Add Action’ > ‘Create Task from Template’

  4. Configure the task action:

    • Action Name: ‘Generate CAPA Tasks’
    • Task Template: Select your corrective action task template (or create one)
    • Assignment Method: ‘Based on Incident Field’
    • Assignment Source Field: ‘Incident_Department’ or ‘Affected_Area’
    • Assignment Target: ‘User Group’
    • Number of Tasks: Set based on your process (1 for simple incidents, multiple for complex)

  5. Advanced Assignment Options:

    • Enable ‘Create separate task for each department’ if incidents can affect multiple areas
    • Set ‘Task Priority’ to inherit from incident severity
    • Configure ‘Due Date Calculation’: Use formula like WORKDAY(Approval_Date, 14, ‘Holiday_Calendar’) for 14 business days

  6. Task Dependencies (if using CAPA integration):

    • Link task to parent incident using ‘Related_Incident’ field
    • Enable ‘Block incident closure until tasks complete’
    • Set task type to ‘Corrective Action’ to integrate with CAPA module

User Group Activation: This is your primary issue - user groups aren’t available for task assignment. Here’s the fix:

  1. Navigate to Admin > User Groups

  2. For each department group that should receive incident tasks (Quality, Engineering, Manufacturing, Safety, etc.):

    a. Edit the user group

    b. Go to ‘Module Access’ tab

    c. Enable these modules:

    • Incident Management (read/write)
    • Task Management (read/write)
    • CAPA (read/write if you’re linking to corrective actions)

    d. Go to ‘Task Settings’ tab

    e. Enable ‘Can receive automated task assignments’

    f. Set ‘Maximum concurrent tasks per user’: 10 (or appropriate limit)

    g. Enable ‘Notification on task assignment’

    h. Select notification template for task assignments

  3. Verify group membership:

    • Each user group must have at least one active user
    • Users must have ‘Task Owner’ or ‘Task Assignee’ role
    • Users must have valid email addresses for notifications

  4. Save each group configuration

Critical for MC 2022.1: After enabling module access for user groups, you must refresh the workflow template cache. Go to Admin > System Maintenance > Clear Workflow Cache. This makes the newly activated groups available in the task assignment dropdown.

Now go back to your workflow template’s task creation action and verify that your user groups now appear in the ‘Assignment Target’ dropdown. Select the appropriate groups for automatic assignment.

Task Template Configuration: Ensure your task template is complete:

  1. Navigate to Admin > Task Templates

  2. Open or create ‘Incident Corrective Action Task’ template

  3. Required fields:

    • Task Type: ‘Corrective Action’
    • Task Name: Use variable like ‘CA for Incident {Incident_Number}’
    • Description: Include incident details using variables
    • Priority: Inherit from incident or set default
    • Due Date: Formula-based (WORKDAY function recommended)
    • Assigned To: Will be populated by workflow
    • Related Record: Link to incident using {Incident_ID}

  4. Add custom fields if needed:

    • Root Cause Analysis Required (checkbox)
    • Effectiveness Verification Date
    • Preventive Action Needed (checkbox)

  5. Configure task workflow if tasks need approval before completion

After implementing all these changes:

  1. Create a test incident
  2. Submit and approve it through the workflow
  3. Verify that tasks are automatically created when the incident reaches ‘Approved’ status
  4. Check that tasks are assigned to the correct user groups
  5. Confirm task assignees receive notification emails
  6. Review System Logs (Admin > System Logs > Workflow Execution) to verify no errors

If tasks still aren’t created, check the workflow execution logs for error messages. Common remaining issues include:

  • Task template has required fields that can’t be auto-populated from incident data
  • User group has no active members at the time of task creation
  • Workflow step is executing but action is failing due to permission issues (verify workflow runs as system account with task creation permissions)