> For the complete documentation index, see [llms.txt](https://docs.oneweb.tech/oneweb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oneweb.tech/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/integration/integrate-process-with-ux-ui.md). # Integrate Process with UX/UI Process Flow can be easily integrated with both Smart Form as well as Page. **Process with Smart Form** \ Assume if you have a request form that needs to be approved by a supervisor. Once you click "submit" after completing the information, system should call workflow to send your request to the supervisor. And once the request is assigned to the supervisor, system should notify him and open the request form on UI for the supervisor to approve or reject. Thus you need to integrate the forms on App Designer with the business process on Process Designer to make it work. The first part of this scenario involves integrating smart form to process using Process buttons as explained in [6.3.6.1 Smart Form Integration with Process](/oneweb/design-and-develop-oneweb-apps/design-and-develop-ux-ui/ux-ui-integration-with-process-micro-flow-external-ui/smart-form-integration-with-process.md). The second part of the scenario is explained in this section as a step by step process. That is, from the Process to the Smart Form. Open Process flow that you want to integrate with an Entity. \ Click on the Human Activity node that you want to map with the Entity. \ Click on ‘Load Entity’ Tab in the configuration panel. \ Choose the Entity name that you want to integrate with this task. \ Choose the process parameter that is passed from process to Entity. \ Choose the field on Entity where the parameter value passed from BO is set. \ Click ‘Done’ to save your mapping ![](https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FCx4sXbo2s92VMsa8PdGK%2Fimage.png?alt=media\&token=a9d0d053-34c1-45d6-a470-92218e63f10a) Now once a task reaches this human activity and is assigned to a user, when the user selects this task to work on from his inbox, system will open the entity mapped to this human activity for the user to work on. **Process with Page** \ Assume if you have a mobile or web page that needs to be submitted to a supervisor, once you click "submit" after completing the information. For this we use Microflow as the integration gateway between Page and Process Engine, to submit details on page to the process and also to send data back from process to the page in the form of notification. Please check the details for integrating process using Microflow in the [Integrate Process with Microflow](/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/integration/integrate-process-with-microflow.md) section. Also please refer [6.3.6.2. Page Integration with Microflow](/oneweb/design-and-develop-oneweb-apps/design-and-develop-ux-ui/ux-ui-integration-with-process-micro-flow-external-ui/page-integration-with-microflow.md). Process can also be integrated with external UX/UI or can be integrated with other system by using the REST APIs provided by ONEWEB Process Designer. Please check the [Process Runtime REST API](/oneweb/design-and-develop-oneweb-apps/integration-with-other-systems/process-runtime-rest-api.md) for more information on the APIs --- # 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.oneweb.tech/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/integration/integrate-process-with-ux-ui.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.