All modules

Ruleworks

Make follow-up rules your admins can maintain.

Turn recurring record-driven work into rules your administrators can understand. Define the conditions, choose the action and inspect what happened.

Pre-release · Collection launch target: January 2027

Conditions your team can read

Combine conditions into a rule that describes when work should happen. Record changes, date offsets and manual runs cover different ways a follow-up can begin.

Implemented · release acceptance pending

One condition, clearly expressedThe trigger and grouped conditions behind one account follow-up rule.Screenshot placeholder
Reserved for an approved product capture. No demonstration is available here yet.

See why a rule would run

Inspect the condition trace and proposed action with a selected test record. Use the result to explain the rule before making it part of a live process.

Implemented · release acceptance pending

The reason behind the resultA dry-run trace that explains the condition result and proposed action.Screenshot placeholder
Reserved for an approved product capture. No demonstration is available here yet.

Reuse the pattern, inspect the history

Portable rule packs support repeatable setups. Run logs and the schedule queue give administrators a place to investigate what happened and what is waiting.

Implemented · release acceptance pending

Where could this
help your team?

Starting points for a fit discussion. These are use-case ideas to evaluate against the supported scope, not packaged industry solutions.

Account follow-up
Explore a task when an account meets a defined condition, with the reason visible to the administrator.
Date-based work
Evaluate a reminder relative to a record date, including the configured business-day rules.
Partner delivery
Package a repeatable rule pattern for another customer implementation; resolve environment-specific references during setup.

Current scope

  • Record, date-offset and manual triggers
  • Conditions, activity/record actions, tokens and business-day dates
  • Test/preview, logs, schedules and portable rule packs

The engine and admin interface are implemented. Live acceptance and release checks are still underway.

Plan around the boundaries.

A draft test is not production acceptance. Email actions, record writes and activation require a controlled environment and release verification.

Recurring Dataverse rules and follow-up patterns. Power Automate remains useful for broader cross-service orchestration.

Check compatibility and release status
Ruleworks overview · Capture planned
A rule you can read. A result you can explain.Rule editor, actual test result and a follow-up action, in one walkthrough.Video placeholder
Reserved for an approved product capture. No demonstration is available here yet.

Plan your rollout with us. This module is not on sale yet. We’ll confirm supported features, requirements and availability before purchase. Core is included; Microsoft licenses and implementation services are separate.

Read the administrator guide or explore the developer reference.

What do you keep rebuilding?

Bring us one rule, import or form challenge. Let’s find the right next step.

Discuss your use case