Difference between revisions of "Administer Versioning"

From LongJump Support Wiki
imported>Aeric
imported>Aeric
m (Text replace - 'permission rights' to 'permission')
Line 10: Line 10:
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]].
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.  
However, users in roles with Administer Versioning permission 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.
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 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>
<noinclude>


[[Category:Administrative Permissions]]
[[Category:Administrative Permissions]]
</noinclude>
</noinclude>

Revision as of 21:02, 16 October 2012

This permission grants a userthe 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 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 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.