# Integrate with App Runtime **App Runtime Integration** refers to how application components created in **App Designer** interact with the runtime environment, including **databases**, **business processes**, and **microflows**, during application execution. ONEWEB provides built‑in runtime integration capabilities that allow Smart Forms to seamlessly connect with backend logic and persistence layers **without requiring manual coding**. *** ### Smart Form Integration with Database (Built‑in Persistence) **App Designer** is used to create **Smart Forms**, which are tightly integrated with the database layer. Using App Designer, users can: * Create forms corresponding to database tables or views * Drag and drop a **Module** and map it to a database table or view * Add fields to the module and map them directly to table columns Once configured, ONEWEB automatically handles: * Data binding between form fields and database columns * Insert, update, and retrieval operations * Transaction handling during save operations This **built‑in persistence** eliminates the need to manually write code for saving or retrieving data from the database. *** ### Smart Form Integration with Business Processes App Designer also enables runtime integration with **Business Processes** created using **Process Designer**. This is achieved using the **Process Button**, which allows users to: * Drag and drop a Process Button onto a Smart Form * Select a business process to invoke * Configure parameter mapping between: * Smart Form fields * Process input parameters At runtime, ONEWEB manages the entire process invocation lifecycle, including parameter passing and execution flow. This type of integration is commonly used for: * Workflow initiation * Approval processes * Multi‑step business logic > For detailed steps, refer to:\ > **Smart Form Integration with Process**\ > *** ### Smart Form Integration with Microflow App Designer can also integrate Smart Forms with **Microflows**, enabling more **dynamic and reactive form behavior** at runtime. Using the **Microflow Interface**, users can: * Configure event‑based actions (for example, on change or on click) * Select a Microflow to invoke * Map: * Smart Form fields to Microflow input parameters * Microflow output data back to Smart Form fields This allows forms to dynamically: * Fetch data from external systems * Perform validations or calculations * Update fields based on backend logic Microflow integration is typically used when forms require **fast, service‑oriented interactions** rather than long‑running workflows. > For more details, refer to:\ > **Smart Form Integration with Microflow**\ > *** ### When to Use Each Runtime Integration Option | Integration Target | Use When | | -------------------------- | ----------------------------------- | | **Database (Persistence)** | Saving or retrieving form data | | **Process Designer** | Workflow‑driven, long‑running logic | | **Microflow** | Dynamic, service‑style interactions | Choosing the right runtime integration ensures both performance and maintainability. *** ### Summary **Integrate with App Runtime** enables Smart Forms to interact seamlessly with backend systems during application execution. With App Designer, users can: * Persist data automatically using built‑in database integration * Trigger business workflows through Process Designer * Add dynamic backend behavior using Microflows * Configure all integrations visually without writing code This runtime integration model ensures that ONEWEB applications remain **loosely coupled, scalable, and easy to maintain**, while supporting both business workflows and responsive user experiences. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.onewebstack.com/building-apps/integrations/what-is-oneweb-integration/integrate-with-app-runtime.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.