Pause and Resume

  • Updated
  • With long, involved decision trees, authors may want to allow end-users to complete the entire tree in separate sessions. So an end-user could start using the tree, go to lunch, and reopen the tree at a later time and finish the session. The state of the tree is saved at all times.

    To make this work, the URL that opens the tree needs to have a unique identifier attached to it, in the session_id parameter of the URL. So when you launch the tree, you will need to provide this parameter. And when the end-user relaunches the tree, the same URL needs to be used.  

    Important: The session_id needs to be unique across all Zingtree customers and sessions.

    For example, if your URL is this:

    https://zingtree.com/show/141123244


    You would create a unique session ID (like 141112232-xyz), and launch the URL like this:

    https://zingtree.com/show/141123244?session_id=141112232-xyz


    Please Note: In order for Pause and Resume to work properly, the tree ID must be the same in both the initial URL and the resumed URL.

     

    Resuming a Session from a Different Node

    You can move a session to a new node by simulating a click on the tree. You need to provide some "click text" as if a button was clicked, and a new node number where the session will resume. The click text will appear in the session history and button click reporting.

    For example, to move a session to node #99, as if a button named "Next" was clicked, you would add this to the URL along with the session ID:

    &click_text=Next&next_node=99

    Note that any spaces in the click text need to be replaced with + .


  • With long, involved decision trees, authors may want to allow end-users to complete the entire tree in separate sessions. So an end-user could start using the tree, go to lunch, and reopen the tree at a later time and finish the session. The state of the tree is saved at all times.

    To make this work, the URL that opens the tree needs to have a unique identifier attached to it, in the session_id parameter of the URL. So when you launch the tree, you will need to provide this parameter. And when the end-user relaunches the tree, the same URL needs to be used.  

    Important: The session_id needs to be unique across all Zingtree customers and sessions.

    For example, if your URL is this:

    https://zingtree.com/show/141123244


    You would create a unique session ID (like 141112232-xyz), and launch the URL like this:

    https://zingtree.com/show/141123244?session_id=141112232-xyz


    Please Note: In order for Pause and Resume to work properly, the tree ID must be the same in both the initial URL and the resumed URL.

     

    Resuming a Session from a Different Node

    You can move a session to a new node by simulating a click on the tree. You need to provide some "click text" as if a button was clicked, and a new node number where the session will resume. The click text will appear in the session history and button click reporting.

    For example, to move a session to node #99, as if a button named "Next" was clicked, you would add this to the URL along with the session ID:

    &click_text=Next&next_node=99

    Note that any spaces in the click text need to be replaced with + .


  • Throughout 2022 Zingtree will be upgrading customers to our new faster and more modern user experience! Here's how to tell which experience your Zingtree Authors are currently using.

    Log in to your Zingtree Author account and navigate to My Trees. How does your current My Trees page look?

    Zingtree Classic

    2022-02-25_12-24-51.png

    New User Experience

    mceclip0.png

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request