Complete this tab to define locking for instances of concrete classes associated with this class group. See Concepts — Understanding object locking.
| Optional. Identify a property or properties that form the lock for all classes
associated with this class group.
For a class group that defines a work pool, enter the single property .pyID here. Each work item in the work pool has a unique work item ID.
If this field is blank, the objects in this class cannot be locked, or the system determines the lock string from information in the Keys array of each class rule (on the Basic tab). Ensure that these form a unique value for each distinct possible instance associated with the class group.
| Select the Allow locking check box to allow the system
to lock instances of classes associated with this class group. Select except in rare
and unusual cases where locking is unnecessary.
If selected, a user cannot save or delete an instance within the scope of this class group unless that user holds a lock on the object. Typically, activities are coded to acquire locks as the instances are opened to the clipboard, and are released later by the Commit method.
If you select the Allow locking check box, then when you use the Obj-Open, Obj-Open-by-Handle or Obj-Refresh-and-Lock method in an activity to open an instance within the scope of this class group (with intent to update and save the instance), select the Lock check box parameter for the method.