Oracle® Beehive SOAP Web Services API Reference
Release 2 (2.0.1.7)
Policy
specifies a plan of actions to govern the lifecycles of the entities.
The plan of actions are defined by rule-based policies and workflows. The policies may be
placed in the enterprise,organization or workspace to let the policy authors collaborate to update the policies
under full access control and version control.
A Policy can be created from the PolicyTemplate
or just created on its own with out
attaching to any template. When a policy is created from the policy template it can import
a subset of the rule defintions from the template. At that time the client is prompted to provide
the attribute values for which the attribute definitions are define with in the ruledefinitions.
A Policy is always attached to the container and it sits in that container. This means the parent and the scope of the policy are the same.
Show inherited members
ProjectionsName | Type | Required | Description |
---|---|---|---|
attributes |
the property values of the corresponding AttributeDefinition defined in the PolicyTemplate and PolicySchema are returned. Attribute Application values are not applicable if the policy is not created from PolicyTempate. | ||
description |
Description of the policy | ||
enabled |
returns true if the policy is enabled, otherwise false. Policy is applicable and enforced only if the policy is enabled. | ||
extensible |
|||
rules |
rule[] |
The rules of a policy are either created in the policy itself or copied from the policy template | |
scope |
The level at which the policy is defined. It could be Enterprise, Organisation, Workspace | ||
template |
Policy template can be option at the creation time of a policy | ||
type |
Inherits From
Inherited By