System form - Completing the Production tab

Enter a production level value that characterizes the need for access security on this system.

5 = production, highest security

4 = preproduction

3 = test

2 = development

1 = experimental, lowest security

A high production level number implements a restrictive security scheme for production use with few people empowered to change rules. A low level (of 1 or 2) enables developers to experiment by creating and updating rules on development systems.

The System instance (the single instance of the Data-Admin-System class) contains the production level of your system. The current level is recorded as the value of the pzProductionLevel property on the Process page.

This production level and access roles together determine class access — which users can create, update, delete, and otherwise operate on objects of specific classes through Access of Role to Object rules ( Rule-Access-Role-Obj rule type).

To change the production level of a system, open and update the Production level field and save the System form. The change takes effect (for a node) the next time that a node is started.

After this period, the system can mark this lock as soft, meaning that the lock is available to other users who request it. Soft locks help to prevent bottlenecks. (The other user is sometimes said to steal the lock.) However, even after a lock is marked as soft, the lock holder retains the lock and can save and commit the updated instance.

For example, if user Harry opens and updates work item W-1000 but then does not save the updated work item for more than 30 minutes, another user — Martha — can open the (unchanged) work item, stealing the lock from Harry. Harry's changes are lost. However, if neither Martha nor any other user open W-1000 during this 30 minutes and Harry has not signed off, then Harry can still save W-1000 with his changes.

When browser-based users exit Pega Platform by closing the browser window rather than by logging off properly, locks held by the requestor remain until the session is later deleted. These locks block access by other requestors. Reducing this Lock Timeout value can reduce such bottlenecks. See PDN article Adjust time-out settings to reduce locking issues when users do not log off.

Do not confuse the lock timeout interval — a single system-wide value — with the authentication timeout value in an access group, which may vary from user to user. No relationship is required between these two intervals.