The Dynamic Entry Tree Workflow Element provides the Dynamic Entry Tree functionality.
This workflow element is able to generate a virtual directory tree hierarchy by using attributes found in entry leaf nodes.. For example, if users are present as uid=scarter,ou=people,dc=example, the Dynamic Entry Tree workflow element can insert new hierarchy using data present in the entry of the user, such as: uid=scarter,ou=accounting,ou=people,dc=example.
The Dynamic Entry Tree Workflow Element component inherits from the Simple Workflow Element
A description of each property follows.
| Basic Properties: | Advanced Properties: |
|---|---|
| ↓ base-dn | ↓ java-class |
| ↓ enabled | |
| ↓ next-workflow-element | |
| ↓ patterns |
| Description | Indicates the base entry below which the Dynamic Entry Tree functionality applies. |
|---|---|
| Default Value | None |
| Allowed Values | A valid DN. |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | No |
| Read-only | No |
| Description | Indicates whether the Workflow Element is enabled for use in the server. If a Workflow Element is not enabled, then its contents are not accessible when processing operations. |
|---|---|
| Default Value | None |
| Allowed Values | true false |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | No |
| Read-only | No |
| Description | Defines the next workflow element in the chain of workflow elements. |
|---|---|
| Default Value | None |
| Allowed Values | The DN of any Workflow Element. |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | No |
| Read-only | No |
| Description | Identifies the matching pattern and the attribute used to build the virtual tree hierarchy. The syntax for the pattern parameter value is attr[=%entryattr%[(SUPPRESS|value]],... The components of the pattern that do not contain the equal sign are used to identify the entries which will be modified by the workflow element. The components of the pattern that contain the equal sign specify how the virtual hierarchy is built. For instance, the pattern uid,ou=%department%(contract),ou configures the workflow element to operate on entries with a DN matching uid=*,ou=* and inserts an additional node "ou" with the value of the "department" attribute, or with the constant value "contract" if "department" is not present in the entry. A second pattern cn,ou=%code%(SUPPRESS) would match objects that have a DN starting with cn and insert an additional node "ou" with the value of the attribute "code", or filter the entry if code is not present is the entry. Multiple patterns can be defined. |
|---|---|
| Default Value | None |
| Allowed Values | A String |
| Multi-valued | Yes |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | No |
| Read-only | No |
| Description | Specifies the fully-qualified name of the Java class that provides the Dynamic Entry Tree Workflow Element implementation. |
|---|---|
| Default Value | org.opends.server.workflowelement.ovdplugin.dynamicentrytree.DynamicEntryTreeWorkflowElement |
| Allowed Values | A java class that implements or extends the class(es) : org.opends.server.workflowelement.WorkflowElement |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | Yes |
| Read-only | No |