Defining Walkthrough trigger options
From the Adopt Editor left-side panel, access the Properties of a Step and open the Triggers tab:
Define when a Step is started.
Spot/Unspot triggers work for elements visible on the page, while Present/Unpresent refer to elements that exist but may not be visible on the page—set as
hiddenin the CSS, for example.Spot in viewport triggers the Step when the element is visible on the employee screen.
Fill select/value and move on triggers the Step for interactions with input fields on the page, such as typing a word in a search bar or selecting an option from a dropdown.
Element loses focus triggers the Step when clicking away from a focused page elements. For example, click away to disable typing from a search bar.
Set a timer for the Step to appear after previous Step completion, measured in seconds.
Define custom external commands to receive as a trigger for Step appearance.
Define a list of other Guides, causing the Step to apear only when those Guides are completed.
You must create custom external commands in the Triggers tab of the previous Step configuration.
Define when a Step is completed.
When the user presses the Next button.
Optionally, add a Next or Done label.
When the user presses the Previous button.
Optionally, add a Previous label.
Spot/Unspot triggers work for elements visible on the page, while Present/Unpresent refer to elements that exist but may not be visible on the page—set as
hiddenin the CSS, for example.Spot in viewport triggers the Step when the element is visible on the employee screen.
Fill select/value and move on triggers the Step for interactions with input fields on the page, such as typing a word in a search bar or selecting an option from a dropdown.
Element loses focus triggers the Step when clicking away from a focused page elements. For example, click away to disable typing from a search bar.
Set a timer for Adopt to end the Step, measured in seconds.
Define custom external commands to receive as a trigger for Step completion.
Define whether the Step sends a custom external command on completion, and create the command.
Define whether a Step persists after completion:
On URL address change causes the Step to persist after the Guide navigates to another page.
On page reload causes the Step to persist after users refresh the page.
Going back in history causes the Step to persist after users return to a previous page.
Any option causes the Step to persist when any of the above criteria is met.
Last updated
Was this helpful?
