Why Are Task Groups Created Automatically When a QM APP Is Started?

Environment

• Product: SOLABS QM10
• Feature: Task Management / QM APP Workflow

Issue / Symptoms

Users may notice Task Groups being automatically created whenever a Quality Management Application (QM APP) is initiated in SOLABS QM10, without any manual action on their part. This may raise questions about whether these Task Groups require user intervention or configuration.

Cause

This behavior is by design. SOLABS QM10 automatically generates Task Groups as part of its core QM APP workflow architecture. These Task Groups serve as containers for secondary tasks associated with the QM APP and its individual steps.

Resolution

No action is required. Automatic Task Group creation is an expected system behavior and does not require any configuration or intervention from end users or administrators.

For informational purposes, the mechanism works as follows:

1. When a QM APP is started, the system automatically creates a main Task Group associated with that QM APP.
2. For each step within the QM APP, an additional Task Group is created under the main Task Group.
3. Any secondary tasks created within a given step are automatically placed under the Task Group corresponding to that step.
4. An automated mechanism manages Task Group accessibility, releasing secondary tasks to their assignees based on the requirements of each QM APP.

Note: These Task Groups are not visible through the user interface and do not appear in standard Task Group listings.

Additional Information

• Automatic Task Groups are a core function of the SOLABS QM10 workflow engine and cannot be manually modified or deleted by users.
• This feature is designed to eliminate the need to manually create Task Groups for each QM APP, streamlining task assignment across workflow steps.
• If unexpected behavior is observed in relation to task visibility or assignment, contact your system administrator or SOLABS Support for further investigation.