Execution Process

once a list is activated , it can be executed the list application supports four execution scenarios step 1 trigger a list can be triggered in two ways method description manual an operator or supervisor triggers the list directly automatic the order cockpit triggers the list as part of a routing step see the configured triggers documentation for customer specific trigger definitions step 2 first execution the operator opens the list and answers all checks after answering the system validates that all checks are answered if not, the operator must complete remaining checks if all checks are answered, the system evaluates whether all answers are within tolerance/expected values step 3 checks successful? result scenario next step ✅ yes 1 execution scenario list is completed ✅ yes 2 execution scenario system triggers second execution ✅ yes approval scenario system routes to approver ❌ no any scenario list is closed with failed status step 4 second execution (if applicable) a second operator (different role or same role, per configuration) answers all checks independently the same success/failure logic applies on success, approval is triggered if configured step 5 approval (if applicable) the approver opens the execution record and validates all answers approved → execution is finalised not approved → execution loops back to the first execution step