Configuring Project Edit Locking
You can configure to:
- Always give a user the choice to break an edit lock, if they try and access a project that is locked for editing by another user. For more information, see "Always Allow Breaking Locks".
- Include additional custom fields that can only be edited if a user has an edit lock for the parent project. These could be user-created fields or PSA fields that are not locked for editing by default.
To include custom fields in project edit locking:
- From Setup, in Create | Objects, view the object that contains the custom field you want to include. You can only include fields on the project task, project task assignment, and project task dependency objects.
- On the Field Sets related list, click New.
- Define a new field set containing the fields you want to include in project edit locking by dragging fields in and out of the
In the Field Set container. You can add any field from the Available for the Field Set container. Make a note of the API name of your field set.
- From Setup, in Develop | Custom Settings | Task Management Settings, click Manage and then Edit.
- Enter the API name of your field set on either the PT Require Lock Fieldset, PTA Require Lock Fieldset, or PTD Require Lock Fieldset setting. Choose the setting that corresponds to the object your custom field is on.
- Click Save.
- Optionally, repeat steps 1–7 for other custom fields.