Skip to main content

Quick Navigation

Workflow Overview

Workflows in TestAuto2 govern two primary artifact types:
  1. Documents (LiveDocs) — Requirements, HARA, FMEA, control plans, and verification documents follow state-based workflows with review and approval gates
  2. Risk Specifications — HARA hazards, FMEA failure modes, and risk records progress through assessment and mitigation states
Both workflow types support:
  • Role-based transitions (author, reviewer, approver, safety engineer)
  • Mandatory field validation at state boundaries
  • Audit trails recording all state changes
  • Notification triggers for pending reviews
Workflows integrate with Polarion’s built-in document lifecycle and support custom review processes configured per project. Risk specification workflows are managed through risksheet cell validators and state enumerations.

Key Workflow Concepts

ConceptPurpose
StateCurrent position in the workflow lifecycle (Draft, In Review, Approved, Published)
TransitionMovement between states, triggered by user action or automated rule
GuardMandatory field or validation that must be satisfied before state transition
ReviewerRole responsible for approving work before state change
Audit TrailHistorical record of all state changes with timestamp and actor

Document Workflow States

Most documents in TestAuto2 follow this progression: diagram
  • Draft — Initial creation; author makes changes freely
  • In Review — Submitted for review; locked against author edits
  • Approved — Reviewer approved; ready for publication
  • Published — Final state; immutable copy for traceability
  • Rejected — Review rejected; returns to Draft with feedback
  • On Hold — Paused pending additional information or resolution
Not all transitions are permitted from every state. For example, you cannot move directly from Draft to Published without review approval. Check Document Workflow States for detailed transition rules by document type.

Risk Specification Workflows

Risk specifications (hazards, failure modes, risk records) progress through assessment and control effectiveness states:
  • Identified — Initial hazard or failure mode detected
  • Assessed — Severity, occurrence, and detectability evaluated
  • Controlled — Risk controls assigned and linked
  • Verified — Control effectiveness demonstrated through testing
  • Accepted — Risk acceptable per ASIL target
See Risk Specification Workflow for detailed state definitions and control effectiveness assessment patterns.

Common Tasks