Zingtree Tags: decision tree logic

Decision Trees with Logic Nodes

In order to make decision trees that can help solve real-world problems, sometimes you need the ability to do more than just choose a path based upon a finite set of choices. For these reasons, we’ve introduced Logic Nodes into Zingtree.

In addition, we’ve found that many of our customer’s integrations are passing data variables into Zingtree, and there are situations where they would like to act on the value of those variables. Logic Nodes make this easy.

If you’re an existing Zingtree author, Logic Nodes replace Scoring Nodes from previous versions. Any tree that is using Scoring Nodes is automatically migrated to this new system, without losing any functionality or you having to do any updating of your trees.

Here’s How Logic Nodes Work

When you edit or create a Logic Node, you’ll see something like this:

Logic Nodes test the value of your Zingtree variables with a series of rules and jump to a node when a condition is met. The rules are applied in order, so once a rule condition is met, the node assigned to the rule opens next. You can also assign a default node to jump to in case no rules apply.

In the example above, if the variable fruit equals banana, then Zingtree will open node #8, the “Banana” node. If fruit is watermelon, then the default “Something Else” node opens.

About Variables

Variables can be numeric or text, and the comparisons work for either data type. You can bring variables into your trees in several ways:

Note: Your choice of variables is shown in a drop-down list. If Zingtree hasn’t encountered a variable yet in one of the above scenarios, then it won’t appear as an option.

Editing Rules

When editing your Logic Nodes, you can edit your rules as follows:

  • Reorder rules by dragging them up and down with this tool: Reorder Logic test
  • Delete a rule by clicking on this: Delete logic test
  • Select any existing variable from the Variables drop-down.
  • Select an operator (=, ≠, <, >, ≤, ≥ ).
  • Enter a value to perform the test upon.

You must also enter a default node to jump to if no conditions are met.

Zingtree Logic Nodes give your decision trees a bonus option for adding extra intelligence to your processes and troubleshooters. Do you have a cool application for Logic Nodes you’d like to share with us? Reach out and tell us your story!

This article was originally published on May 8, 2017.

New Data Entry Form Updates and More

Besides turning Scoring Nodes into more powerful Logic Nodes, we’ve done a lot of little improvements and fixes in the last 30 days.  In particular, we’ve had a few requests for enhancing Data Entry capabilities.

Here’s what’s new:

  • New: Logic nodes
  • API: delete_form_data returns better error message if deleting already deleted form data (Jay H.)
  • Fix: Link nodes now wait for session data to save before linking out. Makes API calls from linked node work 100% reliably.
  • Fix: SSO URLs are now REST compliant (no & or ? characters) (Priya)
  • New: Added browser_language built-in variable (Eric J.)
  • Update: Logic node editor can set root node.
  • Update: Tree nodes can be set as root node (Chris P.)
  • Update: Only allows letters, numbers and underscores in tags. (Morgan A.)
  • Update: Edit Content Node shows advanced options by default if tags or any other advanced option is set (Bill Z.)
  • Update: Simple Overview shows node tags on each line (if they exist). (Bill Z.)
  • Update: Link nodes now show a “please wait” message, in case new page is slow to open. Also improves email-session-info.php experience.
  • Fix: No longer able to inadvertently create node #0 from Document Node editor. (James W.)
  • Update: Tree search (and search in Zingtree FAQ) now shows node title and tag matches first. This gives more relevant results for tree searches.
  • Fix: host-trees integration URL with a space in the agent name source= parameter now gives correct results (Juan C.).
  • Update: Create Tree for Excel, Sheets options now includes direct links to Excel, Sheets example files.
  • Fix: Blank lines in bulk agent submit no longer show an errant error message. (Allen J.)
  • Fix: removed extra white space at the bottom of embedded trees (Josh S.). (Requires getting new embed code.)
  • Fix: Now saves form data when jumping to a new tree and not continuing past the first node (Diana T.).
  • Fix: Session List CSV export now uses local time.
  • New: Session List (All Trees) Report (for Koltyn)
  • Fix: Agent feedback button didn’t show or work properly in embedded trees (Morgan).
  • Update: Button labels can now be 255 characters.
  • Update: Increased database performance by moving to SSD storage.
  • Fix: Now allows tags to be entered without having to press ENTER.
  • Update: Default tag choices that appear in tag list drop down in Settings, My Agents are from all agents and trees, and only from current organization.
  • New: Email and password field types now included in Data Entry Forms (Imran, Maximiliano)
  • Update: Now supports “required” option for radio buttons in data entry forms (Imran, Diana T.)
  • Fix: Tooltips now always appear
  •  Fix: Preview for authors with apostrophes in their name now works properly (Joe O’)
  • Fix: Nopermalink now gets passed as a parameter for host-trees.php (Jenn V.)
  • Fix: Uses https:// for hosting when going from https://zingtree.com/host-trees.php (Jenn V.)
  • Update: SSO restriction is set by default for new trees if SSO is set up for organization (Jenn V.)
  • Update: Better CSS for panels style tree rendering.
  • Update: Spaces in search parameters sent to host-trees.php turn into underscores so tag matching can work properly (Jenn V.)
  • Fix: Clicks and Usage report wasn’t showing true engagement due to using last click time.
  • Fix: Empty scoring variables no longer cause JS errors when rendering trees (Bob H.)
  • Fix: Emailed session transcripts from multi-tree sessions now get the proper questions before the tree jump (Travis A.)
  • Fix: Webhooks with no returned data no longer make JS errors while rendering tree (Bob H.)
  • Fix: Editing data entry fields – can now properly set Required attribute for multiline text fields (Bob H.)
  • Fix: Launching trees from host-trees.php now properly passes along agent name (Juan C.)
  • New: /api/get-history-data.php for use with updated Zendesk Support app
  • Update: Agent feedback now includes link to session transcript (Katheryn P.)
  • Update: Added last_click_time fields to get_session_data API call (Ricardo)

Phew!

As always, let us know if you have any suggestions, comments, or brilliant ideas!