The Skip To Form task will jump to the given form during specification.
DriveWorks moves to the selected form by fast forwarding or re-winding through the navigation that has been applied.
Therefore any form that is included in this task must be part of the main form navigation (i.e. It must lie between the Start and Finish flags in the Form Navigation stage and cannot be a dialog form).
|Defer||TRUE to defer the execution of the macro until after the specification has been saved. FALSE to run immediately.
When a Specification is created a copy of the Project file (.driveprojx file) is stored alongside it in a hidden folder. This file is saved when a Specification is transitioned to a non-running state. The Defer property ensures the Task runs after everything else has happened in that Transition, Operation or change in State.
When transitioning a Specification to a paused state, and set a Task to be deferred, it will run after all the changed values have been saved to the Project file.
When a Task is set to be deferred in an Operation then all other Specification Tasks on that Operation would be run first before the Deferred Task is run.
|Form Name||The name of the form to skip to.|
|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|
|Defer||FALSE||FALSE||FALSE means this action will be run striaght away.|
|Form Name||"Summary"||Summary||Will skip to the form named "Summary".|
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.
This task does not currently support Status Output Navigation.
Please check the Specification Report for details of Success/Warnings/Failure.