Use App states as much as you can

Making too many callouts under the same single app state causes all to be evaluated at the same time and results in poor performance.

Conditional elements are not pre filtering out callouts for evaluation the same way that app states do and affects performance. Should be used as fallback only when app states is not enough and in combination with as many app stats as possible.

✅ App states are good for performance, use it as much as possible.

💬 Report missing app states as (improvement request or direct to R&D) when missing and the product will improve quickly.

✅ App states are good for performance, use it as much as possible.

Don't guide users from all views

...

✅ Always use Show inside of function when creating guides in 3DDashboard. NOTE: Show inside of function is shown only when there are at least 2 applications at the dashboard. Always add some other application when creating guide so this function is shown and can be used.

...

Using

...

XPATH elements

What to avoid when using Xpath elements:

XPATH is a fallback technology and should be used when no green supported targets exist. Should be avoided if possible and you should know what you are doing.

✅ Always check Xpath which you selected and make sure there is no too specific ID in path because guide may not work on other or newly created elements/apps.

✅ Make sure Xpath is specific enough or callout may be shown multiple times/on first matching element.

💬 Report missing common targets and we will make supported green targets

...