Power Apps

Power Pages

Fabric

Dataverse

Workflow Engine

Configure intake, assessment, approvals and portfolio ranking for government and enterprise across Power Platform and Fabric. Your organisation owns the delivered source code.

See workflow screens

Discuss your workflow

Change the process without a new release

Guide requests from intake through assessment and approval to portfolio ranking. Administrators update forms, rules and approval paths as configuration. Versioned forms keep each submission tied to the template it used.

Explore the workflow screens

Follow a request from intake to a ranked portfolio

Explore intake, routing, assessment, portfolio and authoring in the NSW showcase. All people, records, decisions and dates are synthetic. Select a stage or open a screenshot full size.

Intake form

The form is rendered from a definition, not hand-built

Labels, help text, control types, options, defaults and validation all arrive as metadata. A new question is a configuration record, which is why the process can change without a release.

NSW Design System Persona: Alex MorganSynthetic data Open the NSW showcase

Routing review

Where the request will go, before it is submitted

The routing decision is put in writing up front: every assessment team the answers resolved to, what each of them covers, and whether that route is required or selected. The requestor confirms with the destinations on screen.

NSW Design System Persona: Alex MorganSynthetic data Open the NSW showcase

Assessment

The reviewing team sees its own queue, and nothing else

Inside a request a reviewer gets its progress, the other teams involved, the demand health brief and any information they have asked the requestor for. Work outside their scope is absent from the view rather than greyed out.

NSW Design System Persona: Sam WhitfieldSynthetic data Open the NSW showcase

Demand portfolio

Every request ranked, with its pathway and forecast date

Everything in flight is ranked by priority score, with a recommended pathway of fast, standard or complex beside a forecast date. The ranking is not a black box: the criteria, their weights and the pathway thresholds are explained on the screen that applies them.

NSW Design System Persona: Jordan LeeSynthetic data Open the NSW showcase

Template builder

The administrator changes the process, not the code

Form builders configure reusable templates, dynamic fields, validation checks and messages beside a live preview. Conditional rules control which fields appear and when answers are required. Publishing activates that version for new forms; forms already in flight keep their original version.

NSW Design System Persona: Casey NguyenSynthetic data Open the NSW showcase

Try a request in the workflow showcases

These Data-Driven AI product demonstrations use synthetic people and records. They are not government systems or production deployments. The state marks identify each design-system treatment, not government endorsement.

All showcases use the same engine and form templates. The government design treatments demonstrate the styling options; the engine also supports enterprise workflows.

Keep form changes and decisions traceable

Build and publish reusable templates

Form builders create sections, fields, answer types, labels, help text and options. Dynamic fields and validation can show, hide or require answers and check lengths, ranges, formats and other responses. Authors write the messages: errors block submission; warnings let people continue.

A live preview uses the same renderer and rules as the finished form. Authors save drafts and publish a selected version for new forms. Forms already in flight and submitted records keep their original template version.

Search approved catalogue entries

Type-ahead search covers approved products, projects, services, assets and people. A “not listed” path lets a request proceed when the catalogue has no matching entry.

Route work to the responsible teams

Route requests to one or many assessment teams, manage review queues, and support delegated approval and escalation. Configured criteria and weights explain each request’s score and portfolio ranking.

Review activity and diagnose failures

The public demonstrations use browser-local audit logging for supported request, assessment and template actions, with timestamps, outcomes and before-and-after changes. Demo events identify a browser session. We scope authenticated user attribution, central audit storage, retention and access controls for your deployment.

The engine logs screen rendering failures to the browser console and offers a retry action on the affected screen. We scope central log collection, monitoring and alerting with your platform team.

Fit the engine to your Microsoft environment

Choose the host and data layer

The same React and TypeScript frontend runs in Power Apps code apps, Microsoft Fabric apps and Power Pages. People use consistent navigation, form controls, validation feedback and workflow steps.

The Power Apps code app uses Dataverse for configuration and records. Fabric apps and Power Pages need data and access connections fitted to those hosts. We scope sign-in, permissions, attachments, notifications, reporting and environment promotion with your platform team.

The engine contains no department names or organisation-specific logic. Automated build checks enforce that separation.

Match the design system and access needs

The design system is a build-time choice. The NSW showcase loads the NSW Design System, Queensland uses the Queensland Government Design System, and Victoria is Ripple-styled with token values transcribed from a pinned release.

The NSW and Victoria builds have been tested for keyboard, landmark and reflow behaviour from 320 to 1920 pixels.

An assistant panel answers questions about requests and routing on screen and names the record behind each answer. It has a documented path to a Copilot Studio agent grounded on your own Dataverse.

Start with one workflow you can check

Bring its form, its rules, its assessment teams, and what currently goes wrong.

Discuss your workflow

View all solutions

Want to learn more?

Explore the rest of the site or get in touch with the team.

Back to home

Workflow Engine

Change the process without a new release

Follow a request from intake to a ranked portfolio

The form is rendered from a definition, not hand-built

Where the request will go, before it is submitted

The reviewing team sees its own queue, and nothing else

Every request ranked, with its pathway and forecast date

The administrator changes the process, not the code

Try a request in the workflow showcases

Keep form changes and decisions traceable

Build and publish reusable templates

Search approved catalogue entries

Route work to the responsible teams

Review activity and diagnose failures

Fit the engine to your Microsoft environment

Choose the host and data layer

Match the design system and access needs

Start with one workflow you can check

Want to learn more?

Explore

Get in Touch

Evidence & Community

Office

Assurance and credentials