As part of our strategy to stay ever-vigilant about security threats (especially in the light of recent news with other companies), we’ve been spending extra cycles hardening and triple-checking our security and server infrastructure, while also doing our best to continue to improve our product. So while this quarter’s list of updates may be shorter than usual, we’re doing quite a bit behind the scenes to ensure the continued safety and reliability of our service.

New Stuff

Here’s what’s new since our last updates post:

• Added final node result status to global form data report
• Added German to the list of language options
• Added MFA support to SSO
• API for doing “AND” keyword searches
• Default My Trees sort by My Rights, then by Last Modified
• Default super-user view in My Trees to “All Authors”
• During signups, new user will be asked if they want to join an existing organization if applicable.
• Export as JSON all trees belonging to an organizational
• For score variables, we now allow embedded variable references
• Improved Event Log diagnostics for Zendesk integrations
• List Boxes now have “required” option
• Node mass-redirect tool (with support from updated overview UX)
• One step push live activation
• Option in Session Detail page to hide top and bottom chrome
• Third type of conditional view content (hide both end-user and agent content).
• Updated Create Tree page with simpler flow
• New Publishing Links page: Walk authors through choices of publishing links
• You can now add variables in the agent feedback option email address

Fixes

Here’s a list of things we fixed:

• [[USER-ONLY]] content now show in hosted tree when SSO is enabled
• Clicking persistent button from a subtree with no corresponding node in main tree no longer throws JS error
• Clicking Restart no longer erases all variables even if setting to keep them is ticked
• Document nodes with lots of conditions no longer trigger errors
• Editing Logic node buttons in Designer no longer destroys evaluation order, causing some evaluations to fail
• Fixed Error occuring when setting node escalation to “new node”
• Fixed bug preventing PDF forms from working properly in some circumstances
• Fixed timeout issue during excessive load
• Google Sign-in now properly tracks agents
• Importing a file no longer disables Push Live
• In Agent tree view, history label appears better.
• Node Picker shows friendlier text when node returns to previous tree
• Removed “new node to create later” from the escalation node choices
• Restarting a tree reruns apps/webhooks in root node
• score and score_var attributes no longer stripped by node content editor
• Copy Tree option from Gallery fails now appears when logged in
• Copy Node no longer ahows LIVE trees as a destination
• FAQ and Gallery headers show logged-in status
• Link node preview in node picker fails wraps long URL
• Single quotes in link node URLs handled properly in content node editor
• Variables tool no longer allows adding variables to LIVE version

As always, we continue to listen to your feedback, and we log every request. So if you have an insight on how we can make Zingtree better for you, drop us a note.

The post Fall 2020 Updates first appeared on Zingtree Updates Blog.

For decision trees that have proprietary content, Zingtree offers a means to make the flows and data in these trees private. By ticking “Require login via user credentials or API Key” in the Settings tool for any tree, you can restrict access to just the following methods:

• Authorization Header with API Key
• Basic Authentication (username:password)
• Logged-in Agent or Author

Here’s how to enable authentication in the Settings tool:

You can see sample code for all three options on this demo page.

Authorization Header with API Key

In this example, your API Key is passed into the header via X-APIKEY. Here’s JQuery code that shows how this is done with one of the Zingtree demo Gallery trees:

function show_apikey() {
   $.ajax({
      type: "GET",
      url: "https://zingtree.com/deploy/tree.php?z=embed&tree_id=589132969",
      beforeSend: function (xhr) {
      xhr.setRequestHeader("X-APIKEY", "6a103737e44e4aa6e1e4b6b0bcb46f83")
      },
      success: function (data) {
         var iframeDoc = document.querySelector('#myiframe').contentWindow.document;
         iframeDoc.open('text/html', 'replace');
         iframeDoc.write(data);
         iframeDoc.close();
      }
   });

}

Substitute for your own tree ID and API Key for the bolded items.

Basic Authentication

The Basic Authentication standard requires a base 64 encoded username:password sent in the header, as demonstrated in this JQuery code:

function show_basic_auth() {
    $.ajax({
        type: "GET",
        url: "https://zingtree.com/deploy/tree.php?z=embed&tree_id=589132969",
        beforeSend: function (xhr) {
            xhr.setRequestHeader("Authorization", ""Basic c2hlcnlsLmFnZW50QG15Y29tcGFueS5jb206YWdlbnQx")
        },
        success: function (data) {
            var iframeDoc = document.querySelector('#myiframe').contentWindow.document;
            iframeDoc.open('text/html', 'replace');
            iframeDoc.write(data);
            iframeDoc.close();
        }
    });

}

For this demo tree, the username:password is sheryl.agent@zingtree.com:agent1. The part after “Basic” is the base64 encoded username:password.

Make sure to use your own Tree ID.

Logged-in User

The final way to access trees set as Make Private is to just be logged in as an agent or author in the organization which contains your tree. You would launch the tree with the standard hosted URL or embedded iFrame code, or just like so:

function show_normal() {
    $.ajax({
        type: "GET",
        url: "https://zingtree.com/deploy/tree.php?z=embed&tree_id=589132969",
        success: function (data) {
            var iframeDoc = document.querySelector('#myiframe').contentWindow.document;
            iframeDoc.open('text/html', 'replace');
            iframeDoc.write(data);
            iframeDoc.close();
        }
    });

}

Like the above examples, be sure to use your own Tree ID.

The post Adding Security Authentication to Decision Trees first appeared on Zingtree Updates Blog.

Zingtree integrates with Salesforce using the most advanced Lightning Web Components technology. With this integration, you can offer these benefits to your agents:

• Convenient: Launch scripts right from within any Salesforce object.
• Two Way data Transfer: Salesforce Object data can be displayed in the script, or used by a Logic Node to automatically branch. And data gathered in Zingtree can instantly update Salesforce.
• Pause and Resume lets you transfer Cases (or any other object) from one person to another, and retain context and tree browsing history.
• Flexible Configuration: Different decision tree scripts can appear for each object type, or even a specific record in each object. Or a different tree can appear based upon a field in Salesforce.

Salesforce lets you add apps to any part of a page layout. Here’s one way your decision trees can appear in Salesforce.

Installing the App

The first step is to install the Zingtree App into Salesforce from one of these links:

• Production Version
• Sandbox Version

Once you install, you will be taken to the following page on SFDC

Click on one of the “install for” options, “I acknowledge…”, and then click on Install. You will get the following pop-up:

Check the box to grant access to the third-party website and click on Continue.

The installation will finish, and you will receive an email once the installation is complete, which may take a couple of minutes.

After the successful installation, you will see the following:

Click on Done. You will be taken to the following page where you can see the Zingtree app.

Apply Zingtree Package Permission Sets

Important: For using the App as someone who is not an Admin, you’ll need to set up Permission Sets for the App to work properly.

When you install the Zingtree package for Salesforce (SFDC), a number of new components are installed and prepared for you to use. Before you roll this out to your team, you’ll need to give access to the correct pieces of configuration. If you don’t, your users might have trouble actually interacting with the embedded trees.

Be sure to follow the following steps for applying the Permission Sets so that your users can access the various package components.

Permission Sets Included:

• Zingtree Admin – For all Admins that will be configuring the Zingtree package/components. (E.g., SFDC System Administrators)
• Zingtree User – For all Users of the Zingtree package (E.g., Support Reps, Salespeople, etc…)

How to Assign the Permission Sets

1. Validate that you’re logged in as a Salesforce Administrator, or at least someone with Setup / Configure permissions in SFDC.
2. Navigate to Setup > Home > Permission Sets:
   
3. Find and click on the name of the appropriate Permission Set (Zingtree Admin or Zingtree User).

4. Click on Manage Assignments.

5. Click on Add Assignments.
   

6. Add whichever users you’d like.

Configuring the App

Zingtree needs just two parameters for launching a specific tree:

• The Zingtree Tree ID.
• Your Zingtree API Key

To start, you can set global parameters for all objects that launch Zingtree. After that, you can override these defaults from the object’s page layout, or even add a Tree ID field to your object to have different trees appear for each record.

Here’s how to set the global configuration:

1. Choose the Zingtree App from the top left of Salesforce.

2. Pick Zingtree Configuration from the top of the page.

3. Enter the API Key.  If you are logged in to Zingtree, you can find your API Key here.
4. The hostname should always be https://zingtree.com unless you have a custom Zingtree server.
5. Enter the default tree ID. This is the tree that will appear if you haven’t set a different tree ID at the object or record level.

6. Make sure to click Submit when finished.

Add the App to a Layout Page

Once installed, you’ll need to add the App to one or more object layouts.

1. Go to Salesforce Setup.
2. Click on Object Manager.
3. Choose the type of Object to which you’d like to attach a decision tree.
4. Click on Lightning Record Pages.
   

5. Pick the Record Page to modify:

6. Click Edit:

7. Drag the Zingtree Agent Script component onto the layout wherever you like it to appear.

8. If you want to override the global default tree ID, click on the component to configure the new Tree ID to show.

9. Make sure to click Save when finished.

Overriding the Tree ID from an individual Record

You can have different trees appear based upon a custom field in any record – this will override and object level or global level configurations you’ve set. Here’s how to do it:

1. Add a custom field named Zingtree_Tree_id__c to your object. It should be a 12 character text field.
2. If there’s a value in this field, it will be used as the tree ID instead of any other configuration. If it’s blank, the configuration ID is used instead.

Mapping Data Fields

The Zingtree Agent Scripting app can read data from Salesforce and show it in the script, or automatically branch using that variable in a Logic Node. Also, it can update your Salesforce object record instantly, either from a data entry field, or a button click. This works by setting up a simple field mapping. For example, if the Salesforce field is called name, the corresponding field in Zingtree would be called sf_name.

In this example, we’ll show how to update a Salesforce case record from a button click. This will update a field called Product in Salesforce.

First of all, you’ll need to get the Salesforce API name of the field.

1. In Salesforce, go to Setup, Object Manager, and click on the object type – here we’ll choose a Case:

2. Click on Fields and Relationships:

3. Copy the field name next to Product. In this example it’s Zingtree__Product__c 

4. The corresponding field name in Zingtree will be sf_Zingtree__Product__c.
5. Now, open your tree in Zingtree, then go to the node where you want the field assignment to occur.
6. Under the Content Tab, make sure Set Variable on Button Clicks is ticked, then enter the mapped field name that begins with sf_ (sf_Zingtree__Product__c in this example), and set the corresponding values next to each button.

7. Make sure to save the changes.

Now, when the Acme Dynamite button is clicked, the Product field in the Salesforce Case will be filled with Dynamite.

Note that this technique also works for Data Entry Fields.

Predefining Variables to Map

Important: If you are just displaying fields from Salesforce inside of Zingtree, you will need to predefine them using the Zingtree Variables tool. Here’s how:

1. From your tree in Zingtree, go to Tools, Variables.

2. Click Add Predefined Variable.

3. Enter a variable name that begins with sf_  (sf_name in this example).

4. Click Add Variable when finished.

The post Decision Trees in Salesforce - Lightning Web Component first appeared on Zingtree Updates Blog.

Over the past few months, we’ve been busy improving our platform to help you build decision trees – faster, better, and smarter on Zingtree. These improvements are based on the feedback we’ve received and gathered from you, and we’re thrilled to be updating our product to make your authoring experience easier. 

Today, we’re excited to share what’s coming soon, but this is only the beginning. We’re looking at all the ways we can improve your Zingtree experience, so join us in our upcoming webinars to learn more and let us know what you think! 

Building trees faster with more visibility 

Easy All-in-one View 

We know you’re busy, so it was important to start from the beginning when reimagining a faster workflow to create decision trees. As soon as you click “Create New Tree,” instead of an overview page, we now drop you into the page to start editing your first node. The node fields are the same as the classic version, but are now accessible in an accordion style on the same page. This lets you easily see and edit information in that node all at once. 

Faster Navigation to Edit Nodes 

It’s often the case when you make changes to one node, you need to change other nodes. Now the left column of your node editing page shows all of your nodes. You can simply click on the node you want to edit, and it will immediately switch to that node’s editing page. There’s no need to go back and forth to an overview page to access your other nodes. If you have a lot of nodes, you can also filter and search for nodes from here. 

Jumpstart Your Next Node 

If you create an Action Button for a node, we now auto-suggest a name and create that next node for you. It’s a small but powerful way to help you create and connect nodes, and lets you focus on what’s most important: providing the right content for each node. 

Side-by-side Editing with the Visual Designer 

Sometimes seeing how each node connects to other nodes is the easiest way to understand how your tree works. That’s why we built the original Visual Designer tool. We’ve upgraded it in this new version to let you access, edit, and see the node changes all on the same page. This visual representation makes it easy for you to check your work and make sure everything is working the way you want.

Automatically save your work as you go 

We’ve all been there. Hours of work down the drain because it wasn’t saved. Maybe it was a sudden power outage, your computer decided it was time to restart itself, or your cat spilled tea on your laptop. Whatever the reason, we don’t want you to experience that when you’re using Zingtree. When you’re editing your trees and nodes, you’ll see this beautiful message pop up frequently to give you the peace of mind that your work is safe with us. 

Join us live to learn more 

There’s a lot to be excited about coming your way. We want to make sure you’re able to use these features like a pro, so we’re offering live sessions to have our team walk you through the updates. You’ll have an opportunity to ask us questions and get hands-on tips from our power users, and tell us what you think! You can register for our upcoming live sessions here:

• April 27 at 1pm ET: Register now
• May 4 at 10am ET: Register now
• May 19 at 1pm ET: Register now