Zapp Inspector

The Zapp Inspector is a tool included in the Capriza Designer that can help you debug issues with Strengthening and Connections in your Zapp. This article provides an overview of how to use the Zapp Inspector and interpret the various data fields it contains.


Accessing the Zapp Inspector


The Zapp Inspector is accessed via the Capriza Designer. First, click the gear icon in the upper right hand corner of the Designer.




Then, select "Zapp Inspector."




A dialog will open.




Parts of the Zapp Inspector


The Last Action the user performed on the web (or mobile if in Simplify mode), such as Button Click, Start Point, etc., is displayed underneath the "Why do I see this Mobile Page?" text. Beneath this, the Zapp Inspector is divided into two sections: Mobile Page Candidates and Matchers. You can also paste support log data into the Zapp Inspector for analysis by clicking the “Paste support data from log” button at the bottom of the window.


Mobile Page Candidates


The Mobile Page Candidates section describes why Capriza is displaying the current mobile page as opposed to others included in the Zapp. The following columns are included:

  • Mobile Page: Lists the possible mobile page candidates according to their context number (e.g. ctx589). Hovering over any of the contexts will display a thumbnail image of the page for easy reference.



  • Page: The name of the page within the Zapp. 
  • Status: The status of the page connection. Possible values for pages with outgoing connections from the last action taken are "Success, " "Failed," or "Partial" (if some of the required controls are found). Zapp pages without any connections to the previous action are marked as "Unknown."




  • # Controls: The number of controls included on the Zapp page that were successfully match to controls in the source application.

  • Connected: Indicates whether or not the page is connected to the last action taken within the Zapp (e.g. clicking a button, selected a value from a dropdown, etc.). Possible values are "true," "false," or "source" (if the page represents the previous page).
  • Probability: The probability score and percentage for each possible match between the web and mobile pages.
  • Rules: References any Rules applicable to that Connection that are used to resolve Conflicts.
  • Failed: Describes why the connection failed. Possible reasons include the Page Match value being below the 60% threshold, Conflicting (if page probabilities are within 4% of each other), or a missing required web control, as indicated by its code (e.g. wc5665).



Debugging Using the Zapp Inspector


As a best practice, you should follow these steps when using the Zapp Inspector to debug errors.

  1.  Check the Page Connections

Is the intended page connected to the last action? Are additional pages connected that shouldn't be? Check the values in the "Connected" column to verify. Visit the Connections Menu for the control last acted upon to add a new connection or remove redundant connections. Please see Configuring Connections for more information.


  1. Check for Page Conflicts

Pages within 4% probability of each other are considered too similar by the Capriza Designer and will be tagged as "Conflicting" in the "Failed" column. If you have Conflicting pages, add Rules to the Connections to better define when each one should be used. Please see Resolving Connection Conflicts for more information.




  1. Check Controls

If the page status is "Failed" or "Partial" due a a control, as indicated by its web control number (e.g. wc5070), click into the status box and hover over the control’s name to obtain more information on the page's controls.



The resulting popup has four columns:

  • Control: The name of the control, as indicated by its web control code (e.g.wc4765). 
  • Score: A number indicating the probability that the control has been correctly identified. Possible values range from 0.0 to 0.99.
  • Required Score: The minimum score required for the control to be considered as identified on the page. The minimum score for mandatory controls is 0.18 while the minimum score for optional controls is 0.27.

  • Optional: Indicates whether the control's presence on the page is required (i.e. is the control always present on that page?). "True" and "False" are possible values. If a control is optional (i.e. it’s marked as “True” in the column), then the Zapp page may still be considered a valid page match even when the control is not found. All mandatory controls (i.e. controls marked as “False”) must be identified/located in order for a Zapp page to be considered a valid match.

You can also hover over the control’s name to obtain a preview of it.





Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.