Workflow and ServiceDesk Community

 View Only

Matches Rule 

Jun 13, 2012 09:47 AM

Matches Rule

Component definition

This component takes in a data variable from the process data and compares it to a user-defined list of constant values. If the data variable matches one of the items in the list, the component follows the appropriate outcome path. If no match is found, the component follows the "no matches" outcome path.

With this component, you can use any kind of data - text, numbers, or symbols.

Component icon

Description of component output paths

Unknown

The component output paths are described in the following table:

Property

Description

no match

The variable does not match any item in the list.

[List Item]

Each item in the Compare To List becomes an output path. If the variable matches an item, the workflow follows that output path.

Description of component tabs and their properties

The properties on the Evaluation tab in the Matches Rule component are listed and described in the following table:

Property

Description

Case Insensitive

This property lets you make comparisons case insensitive. By default comparisons are case insensitive. Uncheck Case Insensitive to make comparisons case sensitive.

Compare To List

The list of values to compare to the Compare To Variable option.

Compare To Variable

A variable from within your Project which contains the value you compare.

The properties on the Settings tab in the Matches Rule component are listed and described in the following table:

Property

Description

Component Class Name

The class name of this component. This property is not editable, but useful if you call Symantec support.

Description

The description of this component. This property lets you describe how the component is used. You can use it to provide any wanted documentation for this component.

This description is included in the model reports that are created when you click Plugins > Generate Business Model.

Location

The physical location of the top left point of this component on the workflow model.

Name

The name of this component. You can change the name.

If you changed the component name when you double-clicked it on the workflow model, the changed name appears here.

Override Background Color

This property lets you change the background color of this component.

To Do

This property lets you record what you still need to do with the component. Use this property to help you remember the configuration that you want to apply to this component.

The text that you enter for this property appears at the bottom of the component editor. If you enter text for this property, a checklist symbol appears on the component in the workflow model.

Is Enabled

This property lets you enable or disable the component. By default, components are enabled. When a component is disabled, it has no effect on the Project. Clear the Is Enabled check box to disable the component.

  • Execution Outcome

    If a component with more than one outcome path is disabled, you must select which outcome path you want the component to take. Click the Execution Outcome drop-down list and select the outcome path for the workflow to follow.

  • Disabled Mapping

    If the component has output parameters, you must configure all output parameters with fixed data to pass on. This configuration can be performed in the Disabled Mapping option.

Connection information

Not applicable

Component settings

Unknown

Use cases

An example for the Matches Rule component is as follows:

  • Phone number lookup

    A Matches Rule component matches a form submission to an employee's name.

Phone number lookup

Scenario: Employees can click a link on an intranet site to look up phone numbers for other employees. The employee looking up the phone number enters the name of another employee in a Web form and submits the request. The Web form returns with the requested phone number.

Process: This process is built as a Forms (Web) Project type.

The following screen shot shows the process:

A Form Builder Textbox component begins the process and is invoked when an employee clicks the intranet link. The Form Builder component presents the employee with a Web form that includes a component. Users enter the name of another employee in this text box, and the text box outputs a data variable called EmployeeName.

A Matches Rule component follows the Form Builder component. The Matches Rule component takes the variable EmployeeName variable and compares it with a list of employee names that are defined inside the component. If it finds a match, it routes the process along the appropriate output path. If no match is found, the Matches Rule component sends the user back to the form.

One of the Terminating Form components then displays the phone number to the user, and the process ends.

Other components in this example are as follows:

  • Form Builder

  • Terminating Form Builder

  • Exception Trigger

Statistics
0 Favorited
1 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Related Entries and Links

No Related Resource entered.