> For the complete documentation index, see [llms.txt](https://docs.ondeva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ondeva.com/workflow/steps-reference/presentation.md). # Presentation The **Presentation** category in Ondeva workflows is designed to let you visually interact with users through dialogs and UI refreshes. These steps are especially useful when coordinating between user actions and front-end responses, such as showing feedback modals, refreshing components, or closing overlays. ### **Reload Components** **Purpose:** Refresh components in the user interface—either within the main page or inside dialogs—so they reflect the latest data or state. **Key Options:** * **Component IDs**: Specify which component(s) should be reloaded (e.g., tables, charts). This field references the markup id of the component(s) you want to refresh. **When to Use:** * After updating data and needing to reflect it immediately on screen. * After a form is submitted and the UI must show updated totals, filters, or list items. *** ### **Show Dialog** **Purpose:** Opens a specific dialog modal to the user. **Key Options:** * **Dialog Dropdown**: Select the dialog to display (must be predefined in your application’s UI). **When to Use:** * For confirmations ("Are you sure?") * To show contextual actions or forms ("Edit user profile") * To provide feedback after a process ("Your request has been submitted") *** ### **Close Dialogs** **Purpose:** Closes any currently open dialog for the user. **Options:** No configuration needed. It simply closes the currently active dialog context. **When to Use:** * After a form is submitted or action completed inside a dialog * To return users to the main screen after a nested interaction *** ### Best practices * **Dialogs are reusable components** that can contain forms, summaries, or multi-step wizards. These steps let you orchestrate clean UI transitions between them. * The **reload mechanism is context-aware**, meaning only visible components are updated. Efficient for keeping UI fast and responsive. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ondeva.com/workflow/steps-reference/presentation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.