Build business applications with Inflow
These guides are for consultants who understand business processes and have average technical knowledge. They explain what each feature does, where to start in Studio, what to enter, what you should see and how to handle common mistakes.
Start with a complete example
Follow the Leave requests tutorials. Nadia builds the application, Mohammad requests leave and Sara handles the manager's task. The learning path connects people, records, rules, forms, application pages and a workflow in the order they are needed. Use the illustrated learning path for the reviewed screenshots and their limits.
For an introduction to the vocabulary, read how an Inflow application fits together. Then use the Interface Builder handbook when you start designing screens. The HTML handbook contents page links to separate illustrated chapters; keep the chapter folder alongside it for navigation.
Set up the project and its people
- Create and organize a workspace.
- Give people workspace and function access.
- Prepare users and groups.
- Choose application access and starting pages.
- Use Inflow Home as your work landing page, or read the Arabic Home guide. Related pages cover Ask App and Home publishing availability and candidate designs.
- Work with company sign-in.
Some administration steps belong to an authorized administrator. Each guide identifies that handoff; ordinary employees do not need builder or administrator accounts to use a released application.
Define information and business rules
- Create a data model and make it ready to use.
- Choose the right kind of field or input.
- Choose the right kind of rule.
- Write and test formulas.
- Enter, check and calculate Hijri dates.
- Practise generated forms before a record destination is ready.
- Use ready-made functions.
- Find records with Query Builder.
- Connect a screen to its data.
- Show, search and page through records.
Formulas are explained with sample values and business results. A saved record, a running request and somebody's task are different objects; the connected tutorials show how to link them deliberately.
Design forms and application pages
- Interface Builder handbook.
- Choose and configure controls.
- Place and configure installed interface controls.
- Choose useful icons.
- Check an interface before handover.
Start with the visual designer. The handbook explains fields, answer destinations, validation, navigation, preview and publication. Detailed programming and stored-property information is optional further reading.
Design and follow business work
- Design a process.
- Test a process.
- Publish a process.
- Follow a running request.
- Understand current work in Live.
- Design and complete human tasks — assignment, saved answers, one submitted decision, and separate case/record results.
- Choose automatic workflow steps.
- Automate application access and group membership.
- Follow automatic steps and handle failures — version-aware inspection, retry ownership, uncertain outcomes and a business-output worksheet.
- Build useful process reports.
The guides explain publication and running-work differences in business terms. Use the current Live experience when inspecting work; a manager's decision and a separate record update remain distinct results to check.
Add documents, connections and AI
- Organize application documents.
- Add a document library to a page.
- Create PDFs from Word documents.
- Connect to another system.
- Build, test and publish an integration.
- Share a business API safely.
- Prepare approved AI capabilities.
- Build an AI task, with a marked screenshot explaining the model-setup prerequisite.
- Add a helpful AI summary to Leave requests: follow the fictional request, check the prerequisites and keep the manager decision separate.
- Understand and use Virtual Fabrics.
- Work with Ask Inflow.
- Choose between Ask Inflow, App Chat, AI Tasks and integrations.
- App Shell Chat guide: configure the app-level chat entry point, understand permission-scoped answers and task review, and check operator boundaries.
- Configure application access and App Chat for employees.
- Build permission-scoped App Chat for published guidance and permitted records/tasks.
Use fictional information while learning. Your ability to view a record does not automatically permit sharing it with another system or an AI service. The guides explain when to involve the information owner or administrator.
Release the application
Read prepare and move a release, then follow the release and handover tutorial. Agree the target, its prepared services and the ordinary-user checks before delivery. The current direct package-import screen refuses releases that require governed deployment; the tutorial explains how to retain the signed release and keep delivery pending until an authorized supported route is confirmed.
Platform administrators can use Plan application availability with your administrator to separate release destinations, existing Inflow node operations and the infrastructure they operate. The guide helps prepare an architecture discussion; it does not provision or validate a deployment topology. Its specialist node reference now maps every current node role to its worker phases and explains the separate worker-loop and document-extraction lifecycles.
References for specialists
The technical reference library is for platform administrators, integration developers and plugin authors. It preserves detailed contracts, source explanations, configuration and programming information separately from the consultant lessons. Control authors can also use the interface-control SDK and manifest reference for the browser lifecycle contract, compatibility range, examples and trust boundaries.
- Administer interface-control plugins: review installed packages, external-provider configuration, upgrades, disablement, and certified developer-kit downloads.
- Build an interface control: follow the task-based browser-control developer guide and its sample projects.
Developers can start with the repository setup instructions, engineering workflow and documentation maintenance. Existing design policies, historical specifications and evidence remain available at their original scope.
Try alternative approval paths in the Simulation Studio lesson before checking the real user journey.