What's new in Jutro Digital Platform for Qusar

Context sharing for the Microfrontend SDK

The Jutro Microfrontend SDK now supports context sharing between a micro frontend and its shell app, enabling richer cross-module communication and a more seamless, integrated user experience. This enhancement brings the iframe-based Microfrontend SDK closer to the other micro frontend embedding options and delivers a robust context sharing solution for non-Jutro shell apps that embed Jutro micro frontends.

For more information, see Exposing and embedding with the Microfrontend SDK.

Official support for embedding Jutro micro frontends in InsuranceSuite apps

Embedding Jutro micro frontends in InsuranceSuite applications is now officially supported through the Microfrontend SDK. Because the SDK is not coupled to React, it integrates cleanly with InsuranceSuite apps and covers the key embedding scenarios in the base configuration, including authentication, loaders, and iframe resizing.

For more information, see Exposing and embedding with the Microfrontend SDK.

New support for overriding the iframe title in isolated micro frontend mode

Added support in isolated micro frontend mode to override the iframe title using jutro.iframeAttributes.title. By default, the iframe title remains scopeName (the internal micro frontend scope identifier), but applications can now provide a clearer, user-facing accessible name when needed. This is a backward-compatible accessibility enhancement across both the React MicroFrontend API and the MicroFrontend SDK render path.

For more information, see Exposing and embedding the MicroFrontend component with context isolation.

New Workers' Compensation Injured Worker template

A new Workers' Compensation Injured Worker template is now available in the Jutro Web Apps template library. This is a digital solution that gives injured workers a unified, self-service portal for tracking their workers' compensation claim, recovery journey, payments, and related activities.

Key benefits include:

• Provide injured workers with secure, role-based access to claim details, payment history, documents, and recovery information in a single experience.
• Offer guided intake and follow-up interactions that help injured workers complete required tasks and stay informed about their case.
• Use documented components, services, and design assets to implement and customize the template while preserving the intended user experience.

For more information, see Workers' Compensation Injured Worker template.

Automation rules

This release introduces the Automation rules feature including the Auto-deploy rule. The Auto-deploy rule lets you automatically build and deploy Jutro Web Apps when changes are merged to your chosen source control branch. This reduces manual steps and helps keep non-production environments up to date with the latest configuration and code.

With the Auto-deploy rule, you can:

• Configure branch-based triggers for builds and deployments.
• Target specific environments for each automation rule.
• Monitor recent automation runs and review basic status information.

For more information, see Automation rules.

Jutro updates

This release introduces self-service Jutro updates so you can adopt new Jutro versions on your own schedule. From a single view, you can see which Jutro versions are available, review high-level changes, and start an update from your current version.

With Jutro updates, you can:

• View available Jutro versions and their release summaries.
• Trigger an update workflow from your current Jutro version.
• Coordinate updates with your own testing and change-management processes.

For more information, see Jutro updates.

Support for FEEL rule definitions

{
  "generators": [
    {
      "name": "PcSdk",
      "target": "PC",
      "targetUrl": "<your-policycenter-url>",
      "requestFEELRules": true
    }
  ]
}

Developer Assistant for Jutro is now generally available

Developer Assistant for Jutro has left Early Access (EA) and is now generally available. For more information, see Overview of Developer Assistant MCP.

Developer Assistant CLI

The Developer Assistant CLI exposes Developer Assistant tools and resources as shell-invocable subcommands, providing an alternative to accessing them through an MCP client. This is useful for:

• Running Developer Assistant tools inside a CLI pipeline, shell script, or any environment without an MCP client.
• Building automations that need access to Jutro documentation or component data from the command line.
• Providing a fallback path for AI agents with shell access but no MCP transport.

For more details on the Developer Assistant CLI, see Overview of Developer Assistant CLI.

Developer Assistant security usage guidelines

Developer Assistant operates within an agentic IDE, where an AI assistant can read files, edit code, and run commands with your user privileges. New security usage guidelines describe how to configure your IDE to preserve this usefulness while limiting the potential impact of unreviewed commands, whether they originate from a prompt-injected dependency, a compromised file, or a model error. The guidelines cover:

• Core principles such as least privilege, human-in-the-loop for execution, and avoiding broad approvals.
• Hardening your IDE's tool permissions, including a recommended baseline allow/ask/deny configuration for Claude Code.
• Isolating Developer Assistant by using a DevContainer to limit the scope of impact.
• Additional practices for handling credentials, generated code, and untrusted inputs, plus a quick checklist.

For more details, see Developer Assistant secure usage guidelines.