Difference between revisions of "Administer Versioning"
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
This permission grants | This permission grants a userthe ability to view ''[[Versioning Logs]]'' and perform a ''[[#Force Commit|Force Commit]]'' action. | ||
;Considerations: | ;Considerations: | ||
:* The ''{{PAGENAME}}'' permission is enabled by default for the System Administrator | :* The ''{{PAGENAME}}'' permission is enabled by default for the System Administrator | ||
:* The ''{{PAGENAME}}'' permission is set in [[Administrative Permissions]] | :* The ''{{PAGENAME}}'' permission is set in [[Administrative Permissions]] | ||
:* Versioning is enabled in the [[Company Information]] settings | :* Versioning is enabled in the [[Company Information]] settings | ||
Revision as of 23:58, 7 June 2012
This permission grants a userthe ability to view Versioning Logs and perform a Force Commit action.
- Considerations
-
- The Administer Versioning permission is enabled by default for the System Administrator
- The Administer Versioning permission is set in Administrative Permissions
- Versioning is enabled in the Company Information settings
Force Commit
Users who modify Objects via the platform browser user interface (UI) or the Developer Suite tools and APIs will see the [Checkout]/[Commit] buttons, as described in Versioning.
However, users in roles with Administer Versioning permission rights have an additional option, called [Force Commit]. This button appears to these users when a platform element has been checked out.
It provides the ability to Commit the element by force (that is, without the knowledge or consent of the user who has checked out the element). Because users in roles with Administer Versioning permission rights are often acting as the System Administrator, it is necessary that they have the ability to commit changes to the code, regardless if the person initiating the change is available to complete the Commit action.