Back Forward Lock

PRPC has several locking mechanisms:

RuleSet version locking

When a rule belongs to a locked RuleSet version, a lock icon appears at the upper left of the form.

See RuleSet Form — Completing the Security tab and RuleSet form — Completing the Versions tab.

Securing a RuleSet or RuleSet version is reversible. A password may be require to unlock a locked RuleSet or RuleSet version.

Object locking

A PRPC requestor can lock an open instance if the instance belongs to a concrete class that has Allow Locking? selected in the class rule and it has ever been saved and committed to the PegaRULES database. Locks are retained until a Commit method occurs.

Object locks are implemented separately from the locking mechanism supplied by the database software (such as Oracle) that supports the PegaRULES database.

To view object locks held by your own requestor session, select> Process and Rules > Tools > Work Admin > My Locks.

Testing for locks

To test whether a work item is locked, an activity can call the standard activity Work-.WorkLock, which attempts to lock the work item. If it fails to acquire a lock, the SuccessInfo parameter is negative, indicating that the work item is already locked. The FailureInfo parameter provides additional detail.

To test whether an object (other than a work item) is locked, use one of several methods in the PublicAPI LockManagerInterface.

Definitions soft lock
Related topics About application rules
About RuleSet Versions
Concepts — Understanding object locking
Commit method
Understanding locking and transactions in flow executions

UpDefinitions — L