Multiple activities, and even multiple objects, may be modified simultaneously.
To do so, select the desired objects on the canvas by drawing a box around them with the Select Tool
or by selecting them individually with the Multi-Select Tool
.
Next, click from the menu bar. The Set Global Properties window opens.
Each object type has its own tab that contains properties that can be modified globally.
Notable exclusions include unique properties, such as descriptions and IDs. Any change made will override the individual settings for all objects selected, but only for the given type.
For example, if the box next to Float is checked in the Activity tab, every activity selected will have its float displayed on the canvas, but not every milestone. The box next to Float would have to be checked in the Milestone tab as well.
Thus, changes can be made to different types of objects selected on the canvas all from within this window, just by switching between the appropriate tabs and making the desired changes.
Three-state checkboxes control the majority of properties. The default state is a ‘minus’ sign, which represents no change to be applied to the selected objects for that given property.
If a checkbox is clicked when in the mixed state, it then becomes blank. The blank state indicates that the applicable property will not apply to any of the selected objects.
If a checkbox is clicked when blank, it then becomes fully checked. This means that the applicable property will apply to all of the selected objects.
Clicking once more will cycle the checkbox back to the mixed state, which will leave the property for all applicable objects the way it was prior to entering the Set Global Properties window.
Once all desired selections are complete, click the OK button to apply the changes and to close the Set Global Properties window.
If the outcome is not as desired, click Undo
or press Ctrl+Z on the keyboard to cancel the last set of changes.
Expected Behavior for Setting Constraints
Applying start or finish constraints may have a different effect, depending on whether or not any of the selected activities currently have or previously had start or finish constraints set in the past:
Start Constraints
If an activity has never had a start constraint before and Start Constraint is checked, no constraint will be set.
If an activity has never had a start constraint before, but both Start Constraint and Planned Dates are checked, then an NET constraint will be applied at its current start date.
If an activity currently has a start constraint and Start Constraint is checked, there will be no change.
If an activity currently has a start constraint and both Start Constraint and Planned Dates are checked, then the existing NET constraint will be reset to the activity’s current start date.
If an activity used to have a start constraint set and Start Constraint is checked, then an NET constraint will be applied at whatever date the constraint was last set at unless the activity’s current start date is earlier than its last constraint date, in which case no constraint will be set.
If an activity used to have a start constraint set and both Start Constraint and Planned Dates are checked, then an NET constraint will be applied at its current start date, regardless of whether or not its earlier.
If both Start Constraint and Planned Dates are unchecked, their most recent constraint dates will still be remembered internally.
Finish Constraints
If an activity has never had a finish constraint before and Finish Constraint is checked, no constraint will be set.
If an activity has never had a finish constraint before, but both Finish Constraint and Planned Dates are checked, then an NLT constraint will be applied at its current finish date.
If an activity currently has a finish constraint and Finish Constraint is checked, there will be no change.
If an activity currently has a finish constraint and both Finish Constraint and Planned Dates are checked, then the existing NLT constraint will be reset to the activity’s current finish date.
If an activity used to have a finish constraint set and Finish Constraint is checked, then an NLT constraint will be applied at whatever date the constraint was last set at unless the activity’s current finish date is later than its last constraint date, in which case no constraint will be set.
If an activity used to have a finish constraint set and both Finish Constraint and Planned Dates are checked, then an NLT constraint will be applied at its current finish date, regardless of whether or not its later.
If both Finish Constraint and Planned Dates are unchecked, their most recent constraint dates will still be remembered internally.