Use Live Edit in Diagnostics

Consider that you have created a Beacon and configured Visibility Rules at the step level. When you preview the Beacon, it doesn’t appear as expected. You try to debug it but are unsure what went wrong or how to fix it.

Previously, when a content issue was identified using Diagnostics, you had to do the following:

1. Return to the Dashboard

2. Locate the content

3. Perform a Launch Live Edit action

4. Get redirected to the target application

5. Manually reselect the target element to resolve the error.

This added unnecessary steps and increased resolution time.

Diagnostics reduces your manual effort by enabling you to edit content directly within the Diagnostics in Studio. This makes it easier to act on recommended fixes without switching platforms, thereby saving you time and helping you troubleshoot and resolve content level issues more efficiently.

Note:

Live Edit in Diagnostics is supported for all content types that can be edited using Studio such as Flow steps, Launchers, Beacons, and Smart tips. For other widgets such as Pop-ups, Task lists, and Self Help, editing remains available only through the Dashboard.

Here's an orientation video on Live Edit in Diagnostics.

Here’s how to troubleshoot and resolve content level issues using Diagnostics:

5. Click the Beacons accordion and click Diagnose on the Beacon segment you want to troubleshoot.

   Info:

   Whatfix evaluates Beacon widgets on the page and displays the status as Evaluated or Not Evaluated.

   

6. Click Beacons to view all the Beacons in the collection.
   
   

   Note:

   Under Visibility Rules, expand the accordions for Where, When Start, When End, and Who to troubleshoot any widget Visibility Rule issues.
   

   For more information on Advanced Visibility Rules, see Understand Advanced Visibility Rules.

   Info:

   Whatfix Diagnostics uses different statuses to describe the current state of each step or content.

   Expand the accordion to understand the workflow in Diagnostics.

   Understand the workflow in Whatfix Diagnostics

   Once you enable Diagnostics, Whatfix begins evaluating the content and widgets configured for the page.
   As you interact with the content, Whatfix updates the status at each step, helping you understand what is working and what is not.

   
   Success path: When the content or step works as expected

   Status	What does this mean?
   Searching	Whatfix searches for the target element on the page. It tries to locate the UI component the content or step is linked to.
   Found	Whatfix has successfully located the target element and is waiting for interaction to display the associated tooltip.
   Completed	Whatfix marks the step as completed, showing that the content can now be interacted with. For example, clicking a tooltip, completing a Flow step, or clicking a Beacon.

   
   Not Found path: When content does not appear

   Status	What does this mean?
   Searching	Whatfix starts searching for the target element on the page. It tries to locate the UI component the content or step is linked to.
   Not Found	Whatfix is not able to find the target element. This happens due to reasons such as an incorrect URL or missing page tags.

   Note:

   If a Beacon shows the status Not found, it means Whatfix could not locate the target element on the page.

7. Click the Beacon. Diagnostics shows a detailed error message along with an explanation and suggested fix.
   
   

8. Click Element Precision to see how the rules are evaluated.
   
   

   Note:

   You see an error message stating that the CSS selector configured for the step has failed.
   

9. Click Edit step.
   
   

10. On the edit page, click Edit step.
    
    

11. Click Element Precision.
    
    

12. Verify and update the CSS selector as required. For more information on Element Precision Rules, see Element Precision Rules for Beacons.
    
    

13. Click Save.
    

14. Click Save Beacon to apply the changes.
    

15. Click Go To Diagnostics.
    
    

16. Click Refresh to refresh the application and see the changes.
    
    
    The Beacon appears as expected.