Use the Dynamic Defaults tab of the Edit Step dialog box to set the value of one property based on the value the user selects for another property. For example, using dynamic defaults, if the user sets the Severity of a change request to High, the value of Responsibility can be set to Jack automatically.
For each property in the property list, you can place one or more of its values in the When Equals Value list. The value <otherwise> substitutes for any values not explicitly specified in the When Equals Values list.
For each value in the list, you can specify one or more other properties and the values to which they should be set. For example, suppose you add Severity to the Property list. While it is selected, you add High and Low to the When Equals Value list. While High is selected, you add Responsibility/Jack as the property/value pair to the Assign Values To Other Properties list. While Low is selected, you add Responsibility/Jill and a Short Comment “As time permits” to the Assign Values To Other Properties list.
The result is that when a user sets the Severity to High, the Responsibility property is automatically set to Jack. When the user sets the Severity to Low, the Responsibility is automatically set to Jill and the Short Comment property becomes “As time permits”.
A common use of dynamic defaults is to set a revision comment for the revision created at each step. For example, when the workflow control property for a change request is set to “1. New”, the comment can be set to “Status: 1. New”. Users can then see the steps in the history pane when they select the item in the application and review the revision comments.
The user can change the settings created by dynamic defaults. The idea is that, normally, these are changes that the user would be making and, therefore, setting them dynamically saves the user time.
You cannot use a date/time property as the triggering field for a dynamic default.
To set properties based on the user’s changes to other properties:
the type of the selected property). Select one of the following:
If you use the workflow control property in the Dynamic Defaults tab, avoid confusion by never using it as a property to be changed. That is, avoid placing the workflow control property in the columns entitled Assign values to other properties. When you use the workflow control property in the leftmost column (the Property column), always set it to the value that corresponds to the step. Otherwise it will be ignored. For example, in the step “5. Testing”, you can set dynamic defaults for the workflow control property when it has the value “5. Testing”. If your dynamic defaults specifies a change to the Comment field (for example to “Workflow Status is 5. Testing”), that comment would appear in the history for the item and indicate which revisions had that status.