Support / Change control
Workflows
How your company's stages and rules are configured.
A workflow defines the states a record passes through, who can move it between them, and what happens on the way. Administrators configure them; everyone else experiences them as the buttons available at a given moment.
What a workflow controls
- States — WIP and Released always exist; others can be added
- Transitions — who may move a record from one state to the next
- Conditions — required fields, mandatory approvals, checks that must pass first
- Actions — what fires automatically on a transition: notifications, exports, derivative generation, a revision bump
Why a button might not be there
If you can't move something forward, one of these usually applies:
- A required field is empty — the record will normally tell you which
- An approval is outstanding
- Your role isn't permitted to make that particular transition
- A linked record isn't ready — an ECO can't release while an affected part is still checked out
Workflows are versioned
Records in flight keep the workflow version they started under. Changing a workflow doesn't retroactively alter changes already under way.
Still stuck?
Email [email protected] and a person will pick it up. Include the part number and what you were doing — it saves a round trip.