Workflow Conditions
Description of built-in workflow condition types that can be used with Policy Manager workflow.
Table of Contents
- Introduction
- General Conditions
- Authorization Conditions
- Service-Specific Conditions
- Contract-Specific Conditions
Introduction
The following tables list the built-in workflow condition types that can be used with Policy Manager workflow.
Note: Policy Workflow does not include conditions.
General Conditions
These workflow conditions can be used in any type of Policy Manager workflow.
Condition Type | Usage |
---|---|
isNull isNotNull |
Tests for the presence or absence of an object. This is most useful for testing variables or XML entities. Arguments
|
isEqual isNotEqual |
Tests the value of an object. This is most useful for testing variables or XML entities. Arguments
|
organizationHasCategory |
Checks to see if an organization's UDDI definition contains a specific category, and optionally checks the category value. Arguments
Note: The most useful form of this condition would be to use workflow variables in the organizationKey argument. For instance, ${service.scope} would test the categories of the service's organization. |
runScript | Run a script to check for a special condition. For more information, refer to Workflow Functions: runScript. |
Authorization Conditions
These conditions are used to perform authorization tests on the user performing a workflow action.
Condition Type | Usage |
---|---|
authorizeByPrivilege |
Tests to see if the workflow user has privileges on the object being managed by the workflow. Arguments
|
authorizeByRole |
Tests to see if the workflow user has been assigned to a role in the Policy Manager Management Console. Arguments
|
authorizeByOwner | This condition passes if the workflow user is the current owner of the workflow instance. The owner is set whenever an action's result is fired. |
Service-Specific Conditions
These workflow conditions can only be used in the Service Workflow definition.
Condition Type | Usage |
---|---|
isPhysicalService isVirtualService |
Returns true if the service falls into the specified category. |
isProxyService | Returns true if the service is acting as a proxy to another service (set via the Act as proxy admin action.) |
hasProxyService | Returns true if another service is acting as a proxy to this service |
isManagedService |
Returns true for Physical Services that are being managed by an Agent. (set via the Manage admin action.) |
isDiscoveredService |
Returns true if the Physical Service was created by the service discovery function of certain Agents |
isPublishedService |
Returns true if the service has had the publish workflow function applied to it. The use of publish is discouraged because it disabled workflow-controlled access control and its setting cannot be undone. |
isInOrganization |
Returns true if the service is in a specified branch of the Policy Manager organization tree. This condition is useful to perform different workflow paths for different parts of the enterprise. Arguments
|
hasCategory |
Checks to see if the service's UDDI definition contains a specific, category and optionally checks the category value. Arguments
|
proxiedServiceHasCategory |
Checks to see if the proxied parent service's UDDI definition contains a specific category, and optionally checks the category value. Arguments
|
isCompliant |
Returns true is all compliance tests run on a service completed with a status below a specified level. Also returns true if no compliance tests have ever been run for the service. Argument
|
isRunningComplianceTests | Returns true if compliance policy tests are currently executing for this service. |
Contract-Specific Conditions
These are the workflow conditions that are specific to Contract Workflow.
Condition Type | Usage |
---|---|
isAnonymousContract |
Returns true if workflow is operating on an anonymous contract. |