You are here: Configuration > Pages, Configuration Flows, and Search Flows > Search Flows

Search Flows

OVERVIEW

The primary purpose of Search Flows is to help buyers find appropriate products.

Suppliers benefit from creating Search Flows because they know buyers have assistance in locating complex products in a less error-prone way than with manual selection.

Buyers benefit from Search Flows because they can find the best products for their needs quickly and accurately. Search Flows usually appear to buyers when they click Advanced Search oin the Search page.

A Search Flow typically contains selection attributes whose values can be used to determine a set of products. Selection attributes are configurable attributes that can be displayed to the buyer in steps as a flow or all at once.

Using flows, you can add logic to the search process by displaying ”next” steps based on previously set values. With some extra planning, search flow attribute values can carry over to the product Configuration process. For this to work, 2 conditions must exist:

  1. The attribute name and type (for example, float, integer, non-numeric) in the Search Flow must match up exactly with the corresponding attribute used in the Configuration Process.
  2. The attributes whose values should pass along to the Configuration Process must be included in the Search Flow's post-calculation.

A Search Flow rule has a condition and an action. The values of the condition attributes determine the result of the condition, which, when true, triggers an action. The action is to pick up the right Search Flow to be displayed on the Selector Configuration page. If more than one Search Flow rule exists and has its condition evaluating to true, then the first flow is selected based on the flow selection logic mentioned below.

ClosedFlow Selection Logic when Multiple Flows are Applicable

When more than one flow is applicable at the same time, the flows are sorted based on the following criteria (in sequence) to pick up the first flow:

  1. Descending order of validity of flows
  2. Ascending order of nodeType.
  3. Descending order by number of rule inputs

    Rules with single inputs are evaluated last.

  4. Ascending order by rule order number

    See the Reordering Rules section in the topic Configuration Rule Overview.

Following is the precedence order for flow nodeType:

  1. Start Node
  2. End Node
  3. Start and End Node
  4. Transitional Node
  5. Primary Start Node
  6. Primary Start and End Node

The rule for selecting node types for flows is that the first flow has to be one of first four node types listed above for the flow to be picked up and showed on the Model Configuration page. Otherwise the attributes are displayed using the default wizard.

If more than one flow is defined, then the first flow has to be any one of first three nodes listed and the last flow has to be of type NODE_TYPE_END for all the flows to show up.


ADMINISTRATION

ClosedCreating a Search Flow

  1. ClosedNavigate to the Selector List page.

    1. Click Admin to go to the Admin Home Page.
    2. Click Catalog Definition in the Products section.

      The Supported Products page appears.

    3. Confirm that Product Families is listed in the Navigation column, and click List.

      The Supported Product Families page appears.

    1. For the Product Family you are interested in, select Search Flows from the Navigation drop-down and click List.

      The Selector List page appears.

  2. Click Add.
  3. Specify the Name, Variable Name, Description and Status of the rule.
  4. Specify the Selector Type. There are three options:
  5. Select Product Line(s) for the Selector.

  6. Click Add.

    The Selector List page appears.

  7. Click List in the Rules column.

    The Search Flow Rules List page appears.

  8. Click Add.

    The Search Flow: Search Wizard page appears.

  9. Enter the Name, Variable Name and Description of your rule.
  10. Select the Status of the rule: 
  11. Select the Start/End Dates for which the rule is valid (if applicable).
  12. Select the Conditions for the rule.
  13. In the Wizard Node Type drop-down, select any type that has an End Node, such as Start and End Node.

    The Search Flow Results Action section appears on the Search Flow page.

  14. Select the Result Type: 
  15. Click Update and Back.

    The Search Flow Rules List page appears.

    1. Search Flows can only be created at the Product Family level.

ClosedSelector Pop-Up: Define Function (Search Flow Results Action)

Selector Pop-ups provide a way to improve the performance of the Search Results page, because they introduce the ability to invoke calculations on a need-by basis.

By clicking the link/button, the user launches a pop-up dialog with the desired calculations. The calculations can be tailored to individual model/product line(s) returned as search results. The calculations can access dynamic values on the Search Results page.

  1. ClosedNavigate to the Search Flow page.

    1. Click Admin to go to the Admin Home Page.
    2. Click Catalog Definition in the Products section.

      The Supported Products page appears.

    3. Confirm that Product Families is listed in the Navigation column, and click List.

      The Supported Product Families page appears.

    1. For the Product Family you are interested in, select Search Flows from the Navigation drop-down and click List.

      The Selector List page appears.

    2. For the Search Flow to which you want to add a Selector Pop-Up , click List in the Rules column.

      The Search Flow Rules List page appears.

    3. Click the name of the rule to which you want to add a Selector Pop-Up.

      The Search Flow page appears for the rule you are editing.

    4. If necessary, select a Wizard Node Type that has an End Node, such as Start and End Node.

      The Search Flow Results Action section appears on the Search Flow page.

  2. Choose Define Function as the Result Type.

  3. Click Edit Function.
  4. Define the function and include a call to the pop-up function.

    ClosedClick here to see syntax.

    <?xml version="1.0" encoding="UTF-8"?>

    <Item>

    <Company hidden="yes">testCompany</Company>

    <Description>

    <GroupName title="Product Line"r;>bigWidgets</GroupName>

    <Name hidden="no" title="Model"r;>W1</Name>

    </Description>

    <Attributes>

    <Attribute title="SIZE"r;>40</Attribute>

    <Attribute title="r;Color">RED</Attribute>

    <Attribute>

    <![CDATA[

    <table cellspacing=0 cellpadding=0>

    <tr>

    <td class=button-left><img src="/img/button10.gif" width=10 height=22></td>

    <td class=button-middle>

    <a class=button-text href="javascript:popupFunction()>Calculator</a>

    </td>

    <td class=button-right><img src="/img/button10.gif" width=10 height=22></td>

    </tr></table>]]>

    </Attribute>

    </Attributes>

    </Item>

  5. Inputs to the popupFunction: 
  6. Output of the popupFunction
  7. Syntax of popupFunction

NOTES

RELATED TOPICS

Related Topics Link IconSee Also