| Print Open PDF Version of Online Help

#### Restricting Workflow Rules to Specific Channels or Roles When you create a workflow rule with any trigger event other than Scheduled Event, you can restrict the rule to specific channels or roles by adding a condition to the rule. To prevent a channel from invoking a workflow rule Use the ExcludeChannel() function in the condition expression. For example, to prevent a large import operation from triggering a workflow rule, use the following condition in the workflow rule: ExcludeChannel ("Import") For more information about the ExcludeChannel() function, see ExcludeChannel. To restrict a workflow rule to a specific role Use the UserValue() function with the <Role> attribute in the condition expression. For example, to restrict a workflow rule so that it is invoked only when the role of the user whose action triggers the rule is Administrator and the Priority on the record is set to High, use the following condition in the workflow rule: UserValue('<Role>')="Administrator" AND [<Priority>]="High" For more information about the UserValue() function, see UserValue. NOTE: The language-independent field names and the field-name syntax used in any example expressions in this topic are the field names and the field-name syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These examples are still valid. However, if you select the corresponding fields for an expression from the Fields list in Expression Builder in Release 29 Service Pack 1 or later, then the field names and the field-name syntax will be different from those shown in the examples. It is recommended that you always select the fields for your expressions from the Fields list in Expression Builder, so that the field names and the field-name syntax are always correct. For more information about the field names and the field-name syntax in expressions, see About Expressions.

Published August 2022 | Copyright © 2005, 2022, Oracle and/or its affiliates. Legal Notices.