Defining a workflow action that locks or unlocks objects

A Lock or unlock objects operation on an action either locks the object that a workflow is processing, or locks or unlocks one or more related objects.

Note: You can't use a workflow action to unlock the current object because a workflow can't start on a locked object. Unlock an object before a workflow on that object can start.

Before you begin

Define a workflow and add stages and actions to it. For information about how to define an action, see Defining a workflow action.

Procedure

In the GRC Workflow Designer, click the action that you want to edit.
The Action Properties panel opens.
Expand Validations and Operations.
Click New Operation. The Operations panel opens.
Set Operation to Lock or unlock objects.
Provide a Name for the operation.
Optional: You can define one or more conditions.
For more information, see Defining conditions.
Set Execute As System to False to run the action as the logged in user. Set Execute As System to True to run the action as the OPSystem user. The action can then perform operations that the logged-in user cannot. The history on the Activity tab shows OPSystem as the user who performed the action.
When you set Execute As System to True, all set field operations where Target Objects is set to Self run as the OPSystem user.
The setting of Execute As System doesn't affect the applicability check on the workflow.
Click Edit next to Target Objects. Establish what objects are locked or unlocked.
1. Select a Relationship Type:
  - Self
  - Direct Child
  - Direct Parent
  - Ancestor
  - Descendant
2. Select a Related Object Type if you chose any value other than Self. The list is filtered based on what you chose in Relationship Type.
3. Click New Condition to add conditions to the target object.
  For more information, see Defining conditions.
4. If you chose Ancestor or Descendant in Relationship Type, select a path in Relationship Paths.
5. Click Done.
In Lock/unlock, choose the option that you want to use.
Click Done.