Changes you make to the WBS or the Gantt itself are stored as pending edits until you explicitly save or discard these changes. The edits on a project persist beyond a session for a specific user. These edits include edits to the rollup fields which are recalculated only after a save is performed. For example, if you extend the date for a subtask, the parent task dates are not extended until you save the change.
Pending edits include the following types of edits in the WBS:
The following actions outside the WBS are unavailable while there are pending edits. Save or discard your edits to enable these actions:
Whereas changes outside the Gantt view are saved directly to the database, pending edits are saved temporarily until you accept or discard these changes. If you do not save or discard your changes, the pending edits are discarded when your session expires.
When you start making edits in the Gantt view, the project is automatically locked. If someone else already locked the project, the lock icon appears on the toolbar. If you hover over the lock icon, it displays the user who locked the project.
Only the current project is locked. Subprojects are not locked.
All project pages are locked as they are when you open the project in an external scheduler. The pages are locked for all users including the user who locked the project. The Gantt view is an exception to this rule. The current user with the lock can edit in the Gantt view. If the project management setting Allow Edit of Allocations when Investment is Locked is selected, any user with resource management rights to the project can add staff to the project.
As soon as you or the user who locked the project saves their edits, the project is unlocked.
Administrators with the Administration – Application Setup right can unlock the project.
If you open the project in an external scheduler, the Gantt view is locked for all users including the current user.
Copyright © 2013 CA.
All rights reserved.
|
|