This article gives a synopsis of the default specification flow and looks at modifying it to suit a particular requirement during the specification process.
Specification flow always starts with the Specify state. This can be renamed but the name of this state is never visible to any user.
The default specification flow has three States the initial Specify state can enter. To enter these states the specification will pass through a Transition. The default States and the transitions they pass through are as follows:
|Transition from Specify state||State|
|Release (ReleaseLocal when using DriveWorks Administrator or DriveWorks User/ReleaseAutopilot when DriveWorks Autopilot is installed)||Completed /Released to Server|
The default specification flow progresses from the Specify State to:
States have OnEnter and OnLeave events which can trigger tasks that will be run when these events take place. Additionally tasks can have conditions that must be met for the task to run.
The default Pending State triggers the following Enter State Events
The Completed State triggers the following Enter State Events
The Saved State triggers the following Enter State Events
Once at the state any number of operations could happen to the specification. These will be listed under the Actions heading, once the specification is selected from the specification explorer window.
Operations can have Teams assigned that allow access to that operation based on who has logged onto the DriveWorks session.
Operations can also have conditions set that must be met for the operation to be available.
The default Pending State has the following Operations that can be applied from the Specification Explorer window
The default Completed State has the following Operations that can be applied from the Specification Explorer window
The default Saved State has the following Operations that can be applied from the Specification Explorer window
No Conditions are set on any of the above Operations in the Default Specification Flow.
We can see from the Default Specification Flow Overview that it allows a specification to be saved (if the user is interrupted), have documents generated (if the user clicks Finish) or have documents, models and emails generated (if the user clicks Release).
To start modifying the default specification flow:
The Next and Previous buttons that appear during specification when more than one user form appears in the navigation are mandatory and cannot be modified. The save, finish and release buttons however can be modified.
The new name for the transition will now appear on the corresponding button during Specification.
The name of all of the default states can be modified, all states in the specification flow must have unique names.
Once a specification has passed through a transition the name of the state it currently resides will appear in the specification explorer.
When states are deleted all transitions to and from the state are also removed. Any remaining state that has transitions without a target will be highlighted in red. All transitions must have target states for the specification flow to be complete.
This exercise involves adding a new state that will create a document requests more information to allow the specification to proceed.
Our user forms also require some additional information to make the exercise work so this is where we will start.
The small black arrows at the top and bottom of the state icon (once expanded) allow the list to be scrolled through by hovering the mouse over the arrow.
Once the specification has entered the Information Requested state we need to consider what we would like our users to be able to do to the specification from the specification explorer window.
As the state created is clearly awaiting information it is logical that we want to be able to Edit the specification once the requested information is received.
The Events that need to take place on the state now need to be considered. Unlike the Saved state, where the specification is stored and no action taken to produce data, we do need data generating. Once the Request Info button (transition) has been clicked, by the person specifying, we need the information request document to be generated.
|Knowledge Base Article Ref:||KB13022603|