What are the available Display and Advanced options for Guided Tours?

Display options for Guided Tours - Tour Setup

• Scroll to Each Step: Enabling this option would automatically scroll your users to each guided tour step
• Open Links in New Window: Enabling this option would open any links either in the content or 'take me' button in a new page 
• Persist Tour on URL Change: Enabling this option would continue to present the tour even if the URL changes (this option would be best useful in scenarios where you would like the same tour step to show up on multiple URLs of your application)

Display options for Guided Tours - Tour Steps

• Darken Background: Enabling this option would darken the background of your end-users screen to highlight the Tour Step (See example below)
  
  

• Step Resolution: This option determines what happens to the messages, for example, if your page renders slower at certain times, you should click the Wait for it box so the message does not appear before the item it's pointing to displays. If your end-users have access to limited portions of the application based on subscription tiers, and you would still want to create only one tour that fits all, you can use our Skip It option to skip a specific step if a user does not have access to a part of the application where the tour step is being displayed. Center it option would just display the tour step in the middle of the page.

Advanced options for Guided Tours - Tour Setup

• Delay Presentation: You can delay your guided tour presentation by 'x' seconds if you select this option (this option would be very useful if the load time of your web-app is slower than usual on certain URLs. Enabling this option and setting the tour to start after 6 seconds would make sure the tour would only start after your page load is wholly completed)
• Show More Than Once: If you would like to display this tour to your users more than one time, please enable this option, and select the number from the scrollbar below (you can also configure the time interval between the presentation of the tours). Please be advised that your engagement will not be presented again if you have fully completed the tour (i.e. if your user has clicked on an "End" type button on the last step of a tour). The tour would only be presented again if your user has a status of "Presented" or "Dismissed" as the Action Taken.
• Reset Impressions: This option would be best useful for presenting a tour once every 'x' days - indefinitely until you pause the engagement. Enabling this option could be very dangerous - Ex: if you have enabled this option to reset engagement impressions once every '2' days, this engagement would be presented to your end users once every 2 days (indefinitely until the engagement is paused), even if the user has already seen the engagement. One other important point to note is that - if you configure to reset impressions once every 'x' days, the engagement results for that engagement would also be removed after the 'x' day period–meaning, there won't be a historical list of results unless you export the engagement result data once every two days

Advanced options for Guided Tours - Tour Steps

• Partial Visibility: This option would be best useful if your tour step is attached to a UI element that is not completely visible in UI on the initial page load of your web-application (for example, a UI element that is present on a pop up window)
• Pin to Window: If you would like the guided tour step to stay in it's position even when you are performing several actions on a specific page of your app, this option would be best useful
• Advance on Click of Element: This option is selected by default, and would essentially take your users to next step if your end-users were to click on the UI element to which the tour step is attached to.
• Step URL: You could also provide a different URL to each step within a tour if needed (only if your app is framed i.e. contains iFrames).
• Step anchors (selectors): Step anchors (selectors) can be leveraged for advanced tour configuration if your tour steps are not being attached/tethered to the right UI element with either of the options mentioned above. These anchors (selectors) contain the information required by us to identify the element that your tour step is supposed to be attached to (if it is supposed to be attached to an element). An anchor would typically look like the following:
  

  :nth-child(3) > .layout-align-start-start > #layout-fill > :nth-child(7)

  The anchor displayed above denotes a path to reach the desired UI element that you are trying to attach/tether your tour step to. An anchor could also contain just
  

  .layout-align-start-start

  or
  

  #layout-fill

  depending on what element you are trying to attach your tour step to. Please note that we automatically populate anchor information as soon as you attach/tether a tour step to your UI element using our Admin Panel (UIQ bubble), and do not recommend any modification unless the tour step is not attaching to the desired element.
  
  There are three anchors (selectors), namely: Primary, Secondary, and Tertiary. If you would like to modify these anchors, please be advised that the priority order in which these anchors would be respected is Primary > Secondary > Tertiary i.e. we are going to try and attach the tour step to the Primary anchor, and if that does not exist on page, fall back to Secondary anchor or Tertiary anchor.
  
  We use Sizzle JavaScript to capture the anchor information and if you would like to learn more on how to best use these anchors to your advantage, we advise you to refer to their documentation here: https://github.com/jquery/sizzle/wiki.
  
  However, if you are not a developer/technical resource, please open a request with the UserIQ Customer Success team, and we will assist you. Get help by logging a ticket at our helpdesk here.