Select Page

Map View Search

In addition to the automatically drawn flowchart in Yonyx Map View, the search capability offers a very powerful tool for Authors. All search takes place across the expanded nodes of a guide. So if you wish to search across the entire guide, make sure you expand the guide completely by choosing “Expand” option from the root node. There are multiple search criteria supported Sign up for a demoStart a trial

Search nodes containing specific text

Full-text-search feature in Map View enables Authors to search for any word or phrase that may appear in one or multiple nodes of a guide. Author can search across all sections (Title, Body, Follow-on question or Author Notes) of all (expanded) nodes of the guide by choosing “All” from the search option. Author can also confine the search to take place across only the Title, Body, Follow-on question or Author’s Notes sections of all nodes by choosing the corresponding search option. All full-text searches are case insensitive. Examples of some search terms are shown below:

  • Yes – will show all nodes containing the keyword “Yes”
  • Yes it is – will show all nodes containing the phrase “Yes it is”

Search result may contain one or multiple nodes. Author can hop through each matching results by using Next and Prev options.

Search nodes containing notes

Node that contain Author’s notes are highlighted with a red boundary line. Notes section can also be used by an Author to communicate messages to other Co-Authors. For e.g. an Author could mark some acton items for a Co-Author (with initials JWG) by adding notes like these:

  • JWG: Please add a picture here.
  • JWG: Please check if the language here seems easy to understand?
  • JWG: Can you please record a video for this process and then embed it here?

The Co-Author can easily search for nodes whose “Notes” section contains JWG to find notes left for him/her.

Search Nodes Containing Flags

Flags are like breadcrumbs that an Author can drop on any node of a Yonyx guide. Flags are only visible to Authors & only in Map View. A few use cases for Flags are:

  • A Bookmark for Authors: Authors can use flags as a bookmark of the node(s) they were last working on. They can now easily discover the node(s) of interest when they come back to work on the guide again.
  • A tool for guide review: Flags are used by a guide reviewer to mark the nodes that have already been reviewed.
  • A tool for guide translation: If a guide has been cloned and is being translated to another language, Flags are used to keep track of the nodes that have been translated.

Flags are available in six colors for your convenience. You can also search for nodes containing flags of a certain color (or nodes containing no flags) from Map View Search.

Search Nodes Containing Placeholders

Placeholders are variables inserted in guidance steps that get substituted with values obtained from a container app (such as a CRM system, a Website, a Mobile App, an Order Management system etc.) or with data captured in an earlier guidance step traversed by the user. Placeholders are commonly used for personalizing guide content with customer name, Agent name, a serial number or account number provided by customer, a product model name looked up by a container app etc.

Placeholders are defined by Yonyx Admins and inserted in the body section of guidance steps by Authors. The software code to implement the placeholders is written by developers. Authors can search for guidance steps containing a specific placeholder from Map View. Searching with a blank text field shows all nodes containing any placeholder.

Search Nodes Containing Commands

Commands are at the heart of Yonyx Enterprise Data Integration capability.Commands are instructions inserted in guidance steps that help establish bi-directional data communication between a guide user and the container app (such as a CRM system, a Website, a Mobile App, an Order Management system etc.).

When a user traverses through a guidance step containing a command, a corresponding instruction is passed to the container app. Commands may be used for capturing data from users (e.g. displaying a form for user to provide a device serial number), reading data from the container app (e.g determining whether a customer is pre-paid or post-paid customer) or updating container app data (e.g. updating a ticket status in a CRM).

Commands are defined by a Yonyx Admin, implemented by a developer & are inserted by Authors in guidance steps. Each command has some return values. Commands are executed by the container app and the return value is passed back to the Yonyx guide. This return value is used to automatically move forward from the current guidance step along a user response whose auto-traverse conditions are satisfied by the return value.

Authors can search for guidance steps containing a specific commands from Map View. Searching with a blank text field shows all nodes containing any command.

Search Nodes Containing Auto Traverse Conditions

Each command has some return values. Commands are executed by the container app and the return value is passed back to the Yonyx guide. This return value is used to automatically move forward from the current guidance step along a user response whose auto-traverse conditions are satisfied by the return value.

Authors can also search for nodes containing specific auto-traverse conditions. Blank text in the search field matches all user response nodes with any auto-traverse conditions. Author can use the Next and Prev buttons to hop across all matching nodes.

Search Nodes Containing Redirects

Search Orphan User Responses

Search User Responses with Manual Sort Order

Search Hidden User Responses

Search Leaf Guidance Steps

Let us help you evaluate.

Start your 30-day free trial. No credit card required. No strings attached. Sign up for a demoStart a trial