This task will add a security team to a specified Transition on a specified Specification Flow State. This can be useful for giving different teams specific permissions depending on your Specification Flow.
|Title||Changes the Title (not the name) of the task.|
|Team Name||The Team Name that you want to add to a State's Transition.|
|Transition Name||The Transition Name that you want to change on the State.|
|State Name||The name of the State where this Transition is located.|
|Constant Name||The Constant used to report on the success of the Specification Task. This if for reference only.|
When this Task is added the properties are static. To be able to build rules on a static property see How To: Change A Static Property To A Dynamic Property.
|Property Name||Example Rule||Example Result||Meaning|
|Team Name||"Engineering"||Engineering||This will add the Engineering team as a a security team for the specified Transition.|
|Transition Name||"Send For Approval"||Send For Approval||Send For Approval is the Transition that the team security will be added to.|
|State Name||"Specify"||Specify||Specify is the state that contains the transition Send For Approval.|
|Constant Name||"DWConstantAddTeamReport"||DWConstantAddTeamReport||This is the Constant that the Task will report to.|
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 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:
Success with Warnings
Failed (one of the following occurred)