Arranger 2.0, Visual Page Editor & Environment Tools

Sprint 2026.3 is a big one. The Arranger 2.0 framework got major enhancements including page flows, templates, and opening/closing screens. The visual page editor received continued polish, and we shipped a new environment persistence feature for backing up and restoring workflows and webhooks.

Arranger 2.0 Enhancements

The next-generation arranger experience took a major step forward this sprint. Page flows, templates, and customizable opening and closing screens give funeral homes full control over how their arrangement process looks and feels.

What's new:

• Page Flow System - Define custom page sequences for different arrangement types
• Templates - Save and reuse page configurations as templates across locations
• Opening & Closing Screens - Customizable welcome and completion screens for each arrangement
• Component Library Expansion - New data entry, selection, and display components
• V1/V2 Version Toggle - Seamless switching between legacy and new arranger experience

Visual Page Editor Improvements

The visual page editor continues to evolve, making it easier for administrators to design and manage arrangement pages without touching code.

• Drag & Drop Refinements - Smoother component placement with improved drop zone handling
• Component Properties Panel - Inline editing of component settings and styling
• Preview Mode - See exactly what your page will look like before publishing
• Hierarchical Page Assignment - Pages can be assigned at FuneralHome, Company, or Corporation level

Environment Persistence

A new backup and restore feature lets administrators export and import workflows and webhooks between environments. No more manual reconfiguration when setting up a new environment or recovering from issues.

• Export Workflows - Save workflow definitions as portable JSON files
• Export Webhooks - Back up webhook configurations alongside workflows
• Import with Validation - Imported configurations are validated before applying
• Environment Comparison - See differences between environments before syncing

Contract Summary Refactoring

The contract summary received significant refactoring to improve handling of adjustments and deductions.

• Adjustments & Deductions - New dedicated handling for contract adjustments and deductions
• Improved Calculations - Refactored pricing logic for better accuracy
• Deduction Settings - Configurable deduction rules per funeral home
• Updated Contract Display - Cleaner contract summary layout with proper totals

Localization Expansion

The localization push continued with several more modules brought under the multi-language umbrella:

• Corporate Module - All corporate administration pages now support localized strings
• Assets Module - Asset management pages localized
• Catalog Module - Additional catalog components localized
• Freshdesk Integration - Support ticket interface improvements

Infrastructure & Stability

• Token Refresh Fix - Resolved race conditions in JWT token refresh that could cause intermittent auth failures
• Circuit Disconnection Handling - Improved Blazor SignalR circuit reconnection reliability
• MATTSEC Compliance - Updated authentication flow to meet new security requirements
• User Sync Improvements - More reliable user role and permission synchronization
• QA Performance - Fixed performance degradation in QA environments
• Logout Reliability - Resolved intermittent logout failures

Bug Fixes

• Fixed Page NullReferenceException when loading pages with missing component definitions
• Fixed section duplication issue in workflow designer
• Fixed contract deduction settings not persisting correctly
• Fixed branding kit import/export at corporation level
• Fixed V1/V2 routing issues when switching arranger versions

What's Next?

Sprint 2026.4 is shaping up to be another big one. We're kicking off the Connections 2.0 infrastructure, continuing to enhance the Arranger 2.0 component library, and working on paperwork enhancements including sorting and favorites.

As always, if you run into issues or have feature requests, let us know.

— The Solution Center Dev Team