List Creation Process

in mantsu's checklists module, the full list creation lifecycle follows a structured review and approval workflow step 1 create new version the creator creates a new list version and fills in the trigger the id of the checklist the description the system auto generates a version number the creator can link the checklist to an equipment class , an equipment or a location once saved, the system sets the status to draft and stamps the date and author step 2 fill in version details the creator adds metadata and content delay between questions (optional) sequential execution toggle (whether checks must be done in order) attached documents execution mode one of 4 execution possibilities (see execution process docid\ cufumwqq belx9t0woxme ) individual checks unlimited checks can be added, each with different answer types an optional barcode link (for scanner use) optional text and picture fields in the answer at least one valid answer per check is required step 3 save & version check on save, the system validates completeness if incomplete → status remains draft and the system shows what is missing if complete → status moves to for review step 4 validator review the validator opens the checklists module and reviews pending actions two outcomes are possible outcome status change action approve → reviewed creator is notified reject → draft creator receives rejection notes step 5 activation the approver (or authorised user) requests activation the system checks whether a previous active version exists if so, asks for confirmation to deactivate it on confirmation, moves status to activated and the previous version to deactivated step 6 post activation change if an activated list must be changed a new draft version is created the active version remains available for execution until the new version is activated only one active version per checklist id is allowed at any time