Every P&C developer or business analyst knows the drill: A simple rule change that should take hours turns into weeks of release cycles. From an eligibility tweak to a referral-threshold adjustment, hard‑coded rules are the bottleneck of modern insurance. As a developer, you are required to keep the workflows agile to meet changing business needs.
Guidewire Rules Service
Introducing Guidewire Rules Service, a purpose-built, fully-managed cloud native service on Guidewire Cloud Platform that provides centralized, low-code authoring and execution of business rules for Autopilot workflows in ClaimCenter and PolicyCenter. It enables you to decouple decision logic from core applications, ensuring faster changes and consistent outcomes.
Rules Service integrates natively with Autopilot Workflow Service, serving as its core decision support mechanism. This tight integration enables real-time rule execution within workflows while providing the flexibility to update decision logic independently. It serves as the single source of truth for all the Autopilot workflow decisions, providing enterprise-wide governance and ensuring consistent rule application across all insurance processes.
By leveraging the industry-standard Decision Model and Notation (DMN) framework, Rules Service provides a common, visual language for both business and IT teams. The externalization of decision logic accelerates speed-to-market and ensures consistency, allowing you to rapidly implement decision logic for workflows automated by Autopilot Workflow Service in ClaimCenter and PolicyCenter.
Fig. Design rules using the industry-standard Decision Model and Notation (DMN)
Key Features
These are the key features of Rules Service that help replace hard-coded rules with API-first flexibility to improve workflows:
- Low-code, high-control designer: The rules designer provides a low-code framework for authoring and reusing decisions and data nodes.
- Standards-based modeling (DMN/FEEL): The service uses Decision Model and Notation (DMN) to give business analysts and developers a shared language to author rules. You can model decisions using Decision Requirements Diagrams (DRDs), decision tables, and Friendly Enough Expression Language (FEEL) expressions.
- API-first approach: Decision services are exposed as an API and are discoverable by Autopilot Workflow Service immediately upon creation.
- Native Autopilot integration: Rules Service is natively integrated with Autopilot Workflow Service. Autopilot workflows for ClaimCenter and PolicyCenter can invoke decisions synchronously to guide straight-through processing.
Want to see these in action? Watch this demo video for a comprehensive walkthrough of creating and invoking your first decision service.
Usage Patterns
These are common usage patterns for Rules Service:
- Decision support for Autopilot: Centralize routing, eligibility, and threshold decisions that drive straight‑through or assisted flows in ClaimCenter and PolicyCenter.
- Custom rules in InsuranceSuite applications: Externalize frequently changing custom rules to provide business users visibility and control. For example, claim rejection rules, policy integration rules and so on. Please note that you will be required to write the Gosu code to call Rules Service for custom rules in InsuranceSuite applications, with clear caveats regarding latency and the overhead of writing this integration code. Complex server‑side decisions for Jutro: Execute non‑UI decisions on server data (such as eligibility, offer selection, and so on) to keep client applications thin and consistent.
Developer Experience Highlights
- Low‑code authoring: The rules designer offers a visual, low-code interface for creating, modifying, and reusing decision models and their associated data definitions without extensive programming.
- Traceability and auditability: All decision artifacts are version-controlled, and comprehensive execution logging enables full traceability of which rules were applied, when they were executed, and what outcomes they produced.
- Separation of concerns: Business logic is decoupled from process workflows. Workflows handle orchestration and sequencing while complex decision-making is delegated to Rules Service, reducing complexity and improving maintainability.
- Business-IT collaboration: Business analysts can directly define and modify rules, while you focus on system integration, testing, and deployment pipelines.
Stay tuned for more exciting features coming up, including AI-assisted decision modeling and Decision auditing & analytics.
Ready to get started? Partner with your business teams to pinpoint a high‑impact decision inside your current workflows, then model it in the rules designer. Publish your first decision in Rules Service and connect its endpoint to the Autopilot workflow in PolicyCenter or ClaimCenter.
Visit the official Developer Documentation for more details, or reach out to me at smadishetty@guidewire.com with any questions.
Subscribe to our Developer Newsletter for future release highlights delivered directly to your inbox.