DocumentationGuides & reference
Search across guides and reference articles. Try “email”, “API” or “conditions”.
Learn & build
Practical guides
Design journeys, connect data, build workflows and publish accessible services.
11 articles
In this section
- Design pages and navigationCreate a journey that asks for the right information in a clear order, and gives people a dependable way to move, review and return.↗
- Add and configure componentsComponents are the building blocks on a page. Use them to collect information, show guidance, structure complex content and help people complete a service accurately.↗
- Use conditions and branchingConditions let one service adapt to the information a person has already provided. Use them to show a relevant follow-up, skip an inapplicable page, require an answer…↗
- Add actions and workflowsActions make a service do work as a person moves through it. They can look up data, calculate or assign values, create documents, send a message, call an external…↗
- Build a task-list serviceA task list gives people a clear home page for a longer, multi-part service. It shows the work still to do, what is available now, and what has been completed. Use it…↗
- Connect data files and SharePointLibrary-level integrations let several services use the same controlled connection. Set up the connection once in the library, select it from the relevant service or…↗
- Use Markdown and HTMLUse formatted content to help people understand a service and complete it accurately. In content settings that support it, Markdown is the default authoring mode and…↗
- Test, deploy and maintain a serviceRelease a deliberate, tested service version through Prototype, QA and Production. Treat content, settings, conditions, actions and connected systems as one release.↗
- Design accessible servicesAccessibility is part of every design and release decision. Build a service that people can understand, navigate and complete with different devices, input methods,…↗
- API identifiers and coded valuesThe Builder uses friendly labels, while a service definition and API use stable identifiers and coded values. Understanding the distinction helps you configure…↗
- Payments: completion, recovery and caseworkA fee-paying response stays awaiting payment until collection is confirmed. Follow its payment status, resolve outstanding fees and keep staff decisions with the…↗
