The Change Child Specification State task will change the state of the child specifications as defined by the properties of the control.
This task can be used to Transition Child Specifications from one State to another. This can be used on any Transition in the Parent Specification.
If the Child Specification creates documents on this State, make sure the parent Transition is not being run by DriveWorks Live and IIS.
|DefinitionNames||Only child specifications for the given control names will be changed. Use a pipe bar '|' to separate multiple control names, or a '*' to apply to all controls.|
|ProjectNames||Only child specifications based on projects with the given names will be changed. Use a pipe bar '|' to separate multiple project names, or a '*' to apply to all projects.|
|StateName||The name of the target state to which to change matching child specifications.|
|Title||Changes the Title (not the name) of the task.|
Ensure that the DriveWorks user has permissions to the relevant State in the Child Project.
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||Example Rule||Example Result||Meaning|
|DefinitionNames||"ChildSpecList1|ChildSpecList2"||ChildSpecList1|ChildSpecList2||DriveWorks will run this task for controls called ChildSpecList1 and ChildSpecList2|
|ProjectNames||"Project1|Project2"||Project1|Project2||DriveWorks will look for Projects named Project1 and Project2 in the previous controls.|
|StateName||"Completed"||Completed||DriveWorks will change all Projects to this State if it can be found or accessed by the current user.|