> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/creating-and-running-projects/project-validation.md). # Project Validation One of the key features of appRules is that the system provides several options for validating activities on the designer, functions, expressions, data source metadata and other items used in the development of your projects. ## Design Time Validation When using appRules Designer, at design time, appRules flags all activity errors on the designer (using a red border). You can mouse over the error flag to view the error message. As each error is corrected, the error flag is removed. ## Detailed Validation of appRules Projects At any time, you can perform a detailed validation of your projects. To perform a detailed project validation, display the Project Validation modal as follows: Click the Validate button from appRules project toolbar for validation the current project. The project is validated and the results are displayed in a dedicated window. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/creating-and-running-projects/project-validation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.