Occasionally, you or one of your end users may encounter an error without your Zapp. Called a "Context Not Found" error (or CNF), they are indicated by a default screen such as this.
Feedback is automatically captured for each CNF to be used by the Capriza Support team for debugging purposes.
While errors may sometimes be due to network or source application issues, they more often are due to user views or workflows not accounted for during the Zapp Building process. This article provides an overview of the most common causes of CNFs and how to remedy them.
CNFs may arise when the web application loads a page that was not captured within the Zapp. This type of issue may be identified by opening the Feedback screenshot to see the page displayed by the web application. If the rendered page is not included in the Zapp, you can remedy the issue by editing your Zapp and capturing this page.
CNFs due to missing pages can be avoided by following several best practices during the Zapp building process:
- Involve All Stakeholders: Ensuring all relevant stakeholders are involved in the Zapp use case and design process will help ensure sub-workflows are accounted for.
- Consider Edge Cases: Always consider edge cases when defining the Zapp workflow. Poor user experience caused by missing connections for even a subset of users will impact adoption.
- Test Across User Groups and Types: Including users from different groups or with different roles within the source application in testing helps to identify potential edge cases and eliminate CNFs before the Zapp goes to Production.
CNFs may also be due to conflicting connections. The Designer will proactively notify you of conflicting connections as you navigate through the Zapp in Simplify mode. As a best practice, always resolve any conflicts prior to Zapp Testing or Publishing.
Conflicts can be resolved by defining Rules for when each each page should be loaded. Please see Resolving Conflicts and Configuring Connections for more information.
Another leading cause of CNFs are missing controls which leave the Runtime unsure of which page to display. Missing controls are usually caused by one of two factors:
- Optional Controls Marked as Mandatory
Incorrectly marking a control as always appearing on a page will lead the page to fail to load should it not appear. This type of error can easily be resolved by toggling the answer to this Fact from Yes to No within the Identification tab in the Designer.
- Weak Controls
Sometimes insufficient identifiers are present for Capriza to adequately identify a control and, therefore, the appropriate page. Strengthening the control by providing additional Facts, Anchors, or an XPath will resolve the error. Please see Strengthening Basics, Strengthening Best Practices, XPath, and Advanced Configuration Options for more information.