You have created a walkthrough with a step that is attached to an element in your application that appears when the user clicks on a link. However, that step doesn't appear when you preview the walkthrough. This happens because the target element for the next step has not loaded when the next step fires. If a walkthrough step can't find the target element it is associated with, that step will be skipped. You can account for the time it takes for the target element to appear by configuring the Delay field.
In our example we are going to create a walkthrough demonstrating how to add a link in the Global Navigation area. Step 1 will be to instruct the user to click on “Edit Links”:
Step 2 will be to instruct the user to click on “(+) link”, however there is a short delay before the part is displayed:When the user clicks on “(+) link”, there is another delay before the final dialogue is displayed, which is where Step 3 will appear:
In the Edit screen, create the three steps and associate them with a target element:
In the Advanced Properties screen, toggle Advance When Target Clicked to "Yes" and set the Delay to 300:
The delay is counted in milliseconds. “1000” will delay the action by 1 second, “500” will delay by ½ second, etc.
For step 2, in Advanced Properties, toggle Advance When Target Clicked to “Yes” and set the Delay to 800:In the Advanced Properties for step 3, set the delay to 600. This is the last step of the walkthrough so we don’t need to toggle Advance When Target Clicked:
Set the X-Offset field to 100 to move the bubble closer to the center of the section: