Setting

Definition

Node

Allows each node to be named according to a short naming convention.

Description

Allows a longer description of the node and its purpose

Decision tree to which node belongs

The Decision Tree for this node

Call and process this decision tree now

If populated, the decision tree specified is "called" and fully evaluated before continuing any further in the current tree.  The tree that is specified is considered to be a "subtree" and is "called" in much the same way a subroutine is called in programming.  If the subtree terminates with a Success severity code, then the node specified for a True outcome is run next.  Otherwise, the entire tree terminates (as the subtree encountered an issue that must first be addressed).

Workflow to be invoked

If the node will invoke a workflow, that workflow is defined here.

Use the record set resulting from this node for the workflow

By default, the data from the target record will be used to submit to the workflow.  However, it is possible to submit the record set that resulted from a test performed at a previous node.  Note that you must choose a node that will have already been performed before reaching this node (otherwise there will not be a record set).  An example of a test that may create a record set as a result is a test for duplicates.  All records found to participate in the duplicate test are recorded to the Decision Tree Thread's worklog.  When a record set is chosen from a previous node, a workflow thread will be created for each record in the record set.

Maximum time to wait for workflow

If the selected workflow must wait at any point for a response, then the tree will suspend activity and wait for the workflow to complete.  When more than one workflow is created (due to using a record set from a previous node), all workflow threads must complete before continuing.  If the workflow does not complete within the timeframe specified in this setting, the tree will terminate due to a timeout (or move to the node specified for handling timeouts)

Branch to this node when time expires

If the maximum wait time expires before the workflow completes, the tree will branch to this node.  If no node is specified, the tree will terminate upon timeout.

Forward the contents of this field as requestor's email

Each workflow thread carries the email address of the original requestor.  If the target record contains an email address, it may be forwarded as the requestor's email.  If not, a static email address may be entered in the next setting.

Use this value as the requestor's email

If the target record does not contain an email address that may be used, a static address may be entered.  This setting accepts tags.

Forward the contents of this field as approver's email

Each workflow thread carries the email address of the original approver.  If the target record contains an email address, it may be forwarded as the approver's email.  If not, a static email address may be entered in the next setting.

Use this value as the approver's email

If the target record does not contain an email address that may be used, a static address may be entered.  This setting accepts tags.

Forward the contents of this field to the workflow as V(n)

The next six settings allow specifying up to 6 fields in the target record whose values can be forwarded to the workflow thread.  Once in the workflow thread, those values can be referenced in many actions performed by the workflow.

Name of optional user variable to be sent to workflow (UvarN)

These two settings allow naming up to two additional user variables that may be forwarded to the workflow thread.

Forward the contents of this field to UVar(n)

The value of this field in the current target record will be submitted to the workflow as the value for the appropriate user variable.

Apply this condition to the target record

If specified, the target record will be tested against the defined condition.  If the target record meets the condition, the result will be True.  Otherwise, the result will be False.  Note that the thread's variables (v1 through v8) will be forwarded to the condition before it is evaluated.  Values for conditions accept General Tags.  Therefore, {%V1%} through {%V8%} may be used as the condition value, which allows the condition to be tested against data contained in the thread.

Join the result of condition to the test using

The result from the condition (if specified) will be logically combined with the result from the ensuing test using the logical operator defined here.  The logical combination will yield the result of the node.  In the case of no condition being specified, the result of the test will be used as the result of the node.  In the case of no test being specified, the result of the condition will be used.

Apply this test to the target record

If specified, the selected test will be applied to the target record.  Each test results in either a True or False result.  For example, the duplicate test will result in True if duplicates are detected, False if not.

Branch to this node if True

If the result of the condition (if applied), logically combined using the operator specified to the result of the test (if applied) yields True, then this setting represents the next node of the tree to be processed.

Branch to this node if False

If the result of the condition (if applied), logically combined using the operator specified to the result of the test (if applied) yields False, then this setting represents the next node of the tree to be processed.

This is a terminal node for this tree

Checked if the node is a Terminal Node (meaning there are no further nodes.)  If a node is reached and does not have a True or False node defined for the next node to be processed, and if it is not marked as a Terminal Node, an error will be flagged and the tree will terminate in error.  A Terminal Node must be marked as such.

Text to be written to target record for remediation advice

HTML text (usually remediation advice) that will be written back to the target record in the column defined in the Decision Tree settings.

Write this severity code to the target record

A severity code (used to categorize the severity of the issue represented by this terminal node) to be written back to the column defined in the Decision Tree settings.  This value can be used to narrow reporting to the more critical issues identified by the tree.