Text Exists
Component definition
This component evaluates a string type variable to see if it has any content. The Text Exists component is a rule component that decides if a text variable is null or has value, and it routes the process accordingly. If the variable includes any value (including a space character) the component recognizes it as value. This component does not handle arrays.
Component icon
Description of component output paths
Unknown
The component output paths are described in the following table:
Property |
Description |
|
exists
|
Unknown
|
|
does not exist
|
Unknown
|
Description of component tabs and their properties
The properties on the Evaluation tab in the Text Exists component are listed and described in the following table:
The properties on the Settings tab in the Test Exists component are listed and described in the following table:
Connection information
Not applicable
Component settings
Unknown
Use cases
An example for the Text Exists component is as follows:
Form field email
Scenario: A company has a customer service survey form on its website. The form has an optional "Comments" box for customers to use to comment on their customer service experience. Any time a customer uses this box, the customer service department Supervisor receives an email that contains that information.
Process: This process is built in a Forms (Web) Project type.
The following screen shot shows the process:
The process begins with the Form Builder component. The process evaluates the Comments box to determine if text exists. The output from this box populates a variable named Comments.
The following screen shot shows the configured form:
After the customer submits the form, the Text Exists component looks at the Comments variable to see if it is populated with text. The component is configured by setting the input variable for it to evaluate.
The following screen shot shows the Text Exists editor:
If text exists, the process follows the "text exists" path out of the Text Exists component. An email containing all of the form data, complete with the contents of the Comments variable, goes to the Supervisor of the customer service department.
If text did not exist in the Comments variable, then the "does not exist" path is taken. An email containing only the required form data (first name, last name, and customer service rating) goes to the customer service department administrator.
Other components in this example are as follows: