The Store Specification Task stores a specification and leaves it open.
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.
If used when transitioning from a running state or during a paused state then an error will appear in the specification report.
|State Name||The 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.|
|Title||Changes 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 Name||Example Rule||Example Result||Meaning|
|State Name||"Saved"||Saved||The name of the state to store the specification in. If nothing is specified then the previous state will be used.|
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.
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.