Difference between revisions of "Administer Versioning"

From LongJump Support Wiki
imported>Aeric
 
imported>Aeric
Line 1: Line 1:
The Administer Versioning permission right grants users in a [[Role]] the ability to view ''[[Versioning Logs]]'' and perform a ''[[#Force Commit|Force Commit]]'' action.
This permission grants users in a [[Role]] the ability to view ''[[Versioning Logs]]'' and perform a ''[[#Force Commit|Force Commit]]'' action.


;Considerations:
;Considerations:
* The Administer Versioning permission right is enabled by default for the System Administrator in [[Default Roles]]
:* The ''{{PAGENAME}}'' permission is enabled by default for the System Administrator in [[Default Roles]]
* Administer Versioning permission rights are set in [[Available Permission Rights|Administrative Permissions]]
:* The ''{{PAGENAME}}'' permission is set in [[Administrative Permissions]]
* Versioning is enabled in '''Settings > Administration > Company Information > Versioning Settings'''
:* Versioning is enabled in the [[Company Information]] settings


==Force Commit==
==Force Commit==
Line 13: Line 13:


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.
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.
<noinclude>
[[Category:Administrative Permissions]]
</noinclude>

Revision as of 22:50, 29 July 2011

This permission grants users in a Role the ability to view Versioning Logs and perform a Force Commit action.

Considerations

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.