Home Search

DriveWorks Pro 22
Store Specification

Send Feedback

Store Specification

The Store Specification Task stores a Specification, in a Paused State but leaves it open in the current Running State.

Implementing this task will allow a user to periodically store a Specification so it can be edited in the event of a crash or accidentally cancelling the specification.

Its intention is to provide assurance, for example when entering a large amount of data into user forms, that the specification can be stored at any point.

This task should only be used in a running specification.

If used when transitioning from a running state or during a paused state then an error will appear in the specification report.


Property NameDescription
State NameThe name of the state the specification will be stored in (after the task has been run and a subsequent issue occurs or the specification is cancelled). If nothing is selected then the previous state will be used.
TitleChanges the Title (not the name) of the task.


When this task is added the properties are static by default.
See How To: Change A Static Property To A Dynamic Property to enable rules to be built on these properties.

Property NameExample RuleExample ResultMeaning
State Name"Saved"SavedThe name of the state to store the specification in. If nothing is specified then the previous state will be used.

Implementing Store Specification

This task should be implemented on a Macro Button (see How To Create In Form Navigation for more information) or a Form Event (see the section User Form Properties in the topic Form Design for more information).

The task will not run on the Leave Event of a state unless the specification is being canceled.

Child Specifications

When the Store Specification task is required for a Child Specification that is not continuously synchronized (see Settings - About Synchronized Specifications) the Complete Child Specification task must be run before the Store Specification task.

Placing this task above the Store Specification task in the macro will accomplish this.

Using the Task in a Specification Macro

This task has different types of Outputs. For more information about Outputs see Specification Macros Task Node.

Outputs are only available within Specification Macros. Currently Outputs are not available for Specification Flow.

Status Outputs

This task supports Status Outputs. These can be used to perform different actions depending on what the status outcome of the task is. For more information see Status Outputs in the Task Node Outputs section of Specification Macros Task Node.

The status output navigation is as follows:


  • The Task was executed successfully, storing the Specification.

Success with Warnings

  • Should never be fulfilled.

Failed (one of the following occurred)

  • No State found with the name provided.
  • No previous State. (used when no name is provided)
  • Context is not running.