> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-ifs-cloud-development-guidelines.md). # Flow IFS Cloud Development Guidelines Read me Flow IFS Cloud Development guidelines extends OData connector documentation from . Guidelines is a collection of ideas, best practices and more detailed help to different tools to make development smoother, faster and of greater quality. Some sections describe real life issues (=problems) that have been discovered in first IFS Cloud projects to help developers to recognize them and how to cope with them. Guidelines is a living document which welcomes new content from all OData developers. **Please send thoughts and/or feedback to:** [**project.office@novacura.se**](mailto:project.office@novcaura.se) --- # 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.novacura.com/flow-ifs-cloud-development-guidelines/flow-ifs-cloud-development-guidelines.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.