DriveWorks Pro 15: Concept: Specification Flow (KB12121004) [send feedback...]


Specification Flow is a feature in DriveWorks that gives you the ability to fully customize the DriveWorks specification process. By default a project in DriveWorks is created with a default specification flow which guides a specification through four basic States - Running (i.e. the user is filling out forms in the specification), Saved, Pending, and Completed.

Each one of these states has links to certain other states which the end-user uses to move from one state to another. For example, a specification in the Saved state can be moved into the Running state, and a specification in the Running state can be moved into the Pending state (by clicking Finish), or the Completed state (by clicking Release). These links between states are called Transitions.

Each state also has certain Operations that can be performed on it, but which do not move to another state, for example, a specification can be deleted, or copied.

DriveWorks provides the ability to add and remove any states, transitions, and operations, so that you can setup the specification process to work effectively for your product.

Example Uses

There are lots of reasons why you may want to look at customizing your specification flow, here are a few examples.

  • You may have a quoting process which involves generating a general-assembly drawing - all before releasing to manufacture and before the full manufacturing information is generated.
  • You may have additional requirements during the specification process such as copying a document to another machine which otherwise would involve complicated macros.
  • You may simply want to change the text that is displayed on the "Finish" button to be something like "Quote" 

Knowledge Base Article Ref:KB12121004

Specification Flow is a powerful feature that gives you full control over the specification process. Specification flow can be tailored to give specific users and teams permissions to initiate certain characteristics during the life cycle of the specification.

A term used with Specification Flow. States are used to control what actions should be taken if an operation or transition is started, or in the event of entering or leaving a state.

A term used with Specification Flow. A specification transitions from state to state when the user clicks the corresponding navigation button on the user form.

A term used with Specification Flow. Operations are actions that can be performed on a specification that has entered a state. Operations trigger task sequences that apply the required action.

Table of Contents