Back to Dev Blog Sprint 2026.13

Post Verification, Showroom Rework & Smarter Merge Fields

August 2026 | Solution Center Dev Team

Sprint 2026.13 is about being sure. A new Verify on Post setting lets you require that a field was genuinely reviewed — so "Unknown" becomes a real answer instead of a blocker — and unmet post requirements can now be fixed right on the Financial Summary. The Showroom builder trades keyword guessing for real filters on material, category, and couch style, and obsolete showrooms can finally be removed. Merge fields consolidate into one canonical set that behaves identically in Connections 2.0, Arranger 2.0, and your email and text workflows. Forms print at the size you designed them instead of one small fixed size, older cases keep showing the staff who handled them, and the analytics feed finally ties to the contracts it came from.


Verify Before You Post

Post requirements have always asked the same thing of every field: put something in it. But some answers genuinely are "unknown," and a requirement that can't be satisfied honestly just teaches staff to type a placeholder. This sprint splits the two ideas apart — a field can now be required to be reviewed rather than required to be filled in.

  • Verify on Post — Mark a field as needing verification and the arranger is prompted to confirm it at post time, with "Unknown" remaining a perfectly valid answer
  • A Record of Who Confirmed What — Each confirmation is recorded, so a posted case shows who verified which field rather than leaving it to memory
  • Fix It Where You See It — Unmet post requirements are now editable in place on the Financial Summary, instead of sending you off to hunt down the screen that owns each field
  • Custom Fields That Can Actually Be Satisfied — A custom field marked Required to Post now recognizes the value you entered, so those cases can be posted
  • Consistent Everywhere — Posting now checks eligibility the same way no matter how the request arrives

A Rebuilt Showroom Builder

Building a showroom meant typing keywords into a search box and hoping you remembered how a casket was named. Now you pick from what the products actually are.

  • Filter, Don't Guess — The item picker's keyword search is replaced with real filters for material type, category, and couch style
  • See What You've Chosen — Selected items carry an unmistakable ribbon, so a long build no longer needs double-checking
  • A Simpler Flow — The redundant Close button is gone and the filter clears after items are added, ready for the next selection
  • Retire Old Showrooms — Inactive showrooms tuck behind a Show Inactive switch, and administrators can permanently delete one that is genuinely finished with

Merge Fields That Mean One Thing

Merge fields had grown up three separate times — once for Connections 2.0, once for Arranger 2.0, and once for email and text workflows — so the same piece of information could have three different names depending on where you were standing. They are now one set.

  • One Canonical Set — Decedent and case fields share a single list across Connections 2.0, Arranger 2.0, and Email/SMS workflows, with the names you already use kept working as aliases
  • Gathering Details — New fields for the arrangement conference, funeral ceremony, visitation, and graveside service, including their addresses
  • Invite Families Directly — The Family Connections link and access code can be dropped straight into an email or text
  • The People on the Case — Funeral director, next of kin, and authorizing agent fields, plus the cremation date
  • Nothing to Rewrite — Existing templates keep working exactly as they are; the older names simply resolve to the same values

Paperwork That Prints the Way You Designed It

If you took the trouble to lay a form out at fourteen point, the form should come out at fourteen point. It didn't. Generated forms were being forced to one small fixed size no matter what the form's author had configured, and narrow fields could bottom out at four points — small enough that a printed permit was genuinely hard to read. This is fixed properly, not papered over.

  • Your Size, Not Ours — Forms render at the font size configured on the form itself; the application no longer overrides it
  • "Auto" Actually Scales — A field set to size automatically now sizes to the amount of text in it, the way it did in the previous generation of the product
  • Big Text Boxes Too — Multi-line free-text fields were skipped entirely by the old sizing pass; they're now scaled along with everything else
  • A Readable Floor — When a value genuinely has to shrink to fit, it stops at six points instead of four
  • The Same Form Everywhere — Forms & Reports, Arranger paperwork, and the Menu used to disagree about sizing, so the same form looked different depending on where you generated it. They now agree

Cases and the People on Them

Staff change, and a case that was arranged three years ago should still be able to tell you who arranged it. This sprint closes a set of gaps where the record and the reality had drifted apart.

  • Turnover Doesn't Erase History — A staff member who has since been disabled stays visible on the cases they were assigned to, so an older case still shows who handled it
  • People Roles That Save — Editing an existing person's roles now persists, the Payer role shows as selected when it is set, and roles that come from a case assignment are shown rather than appearing blank
  • Signed, and by Whom — The signature package history records which user performed each action, so the audit trail names a person instead of leaving it to memory
  • Clearing a Disposition — Clearing the disposition returns the case to Not Specified instead of raising an error, and clears the disposition type with it

Reporting You Can Reconcile

A report you have to explain is a report nobody trusts. This sprint went after the remaining places where the analytics feed and the contract in front of you disagreed.

  • Discounts That Add Up — Package discounts no longer inflate the contract total in the Daily Sales feed, and contract adjustment rows now carry a description instead of exporting blank
  • Present Discounts Your Way — A company can choose how discounts appear in the feed, so the numbers line up with how you already report them
  • Miscellaneous Sales & Veterans — Off-contract sales and veteran detail now flow into Daily Sales, closing two gaps between the feed and the books
  • Sync That Tells You — A company-level sync that can't run now says so instead of quietly reporting success

Faster Price List Screens

The general price list screens are where administrators spend their afternoons. This round is about not fighting them.

  • Search Where You Need It — GPL Pricing and Visibility both get the persistent magnifying-glass search that Merchandise already had, and it filters what's actually on screen
  • Page How You Like — Visibility gains an items-per-page control to match Pricing, and changing the page size no longer warns about unsaved changes or leaves you on a blank grid
  • Real Spreadsheets — Price list downloads arrive as proper Excel files, with a spinner while a large one is being built
  • Show On GPL Up Front — The Add Multiple Services screen includes the Show On GPL toggle, so services no longer have to be reopened and edited one by one
  • Readable Packages — The package name column no longer clips its text on first load

Page Builder & Arranger Polish

A round of fit-and-finish on the components families see and the editor you build them in.

  • Photo Aperture Frames — Decedent Info can present the photo in an aperture frame, for a more finished look on the family-facing page
  • Nicknames, Cleanly — A Show Nickname toggle displays the nickname when there is one and leaves no stray quotation marks when there isn't
  • Bigger Attachments — The upload limit rises from 5 MB to 30 MB, with every check in the application resolving from one place
  • Drop It Where You Want It — Components now land where you drop them in the page editor instead of drifting to another position
  • No More Flicker — The Selection Guide loads its tabs up front, so casket images stop reloading each time you page through
  • Stale Selections, Flagged — A product that no longer applies after an answer changes is marked "No longer applies" with one-click removal, rather than sitting there looking selected

Under the Hood

The largest piece of this sprint you will never see is the ability to answer "what happened to that order?" without guesswork:

  • Order Audit Trail — Every step of an order is now recorded on request: the payload as it was built, the call out to the vendor with how long it took and what came back, and the confirmation email including whether the order number was actually present when it was sent. An order that went out wrong stops being a matter of reconstruction from memory and becomes a record you can read. It is off by default and switched on through configuration, so support can turn it on for a customer who is reporting an intermittent problem without waiting for a release — and enabling it can never interfere with a checkout
  • Honest Order Numbers — The order number field no longer receives diagnostic text when a vendor rejects an order, and every message the vendor sends back is now logged with its real severity, so a successful order stops being labelled an error
  • Procura Orders — Internal notes and item pricing condition are captured on Procura orders
  • Addresses in Every Tenant — Obituaries published to CFS and FuneralTech, and Connections 2.0 case events, now resolve service addresses correctly regardless of how a tenant's address lookups are numbered
  • Training Tenants — Training accounts no longer provision real analytics datasets

Bug Fixes

  • #10925: Generated forms print at the font size set on the template, and narrow fields stay readable
  • #10989: Advancing a case that runs more than one workflow moves the workflow you clicked, and Funeral Director field triggers fire
  • #10882: Field Value Changed triggers no longer cross-fire between fields that share a name
  • #10906: Clearing the disposition selection in the Arranger no longer raises an error
  • #10887: A person marked Disabled stays visible on the cases they are already assigned to
  • #10899: Editing an existing person's roles saves, and case-assigned roles are shown
  • #10902 / #10903: The product information popup closes on its X in both the Catalog and the Arranger
  • #10367: Corner selections render on the Affinity and Stafford casket families
  • #10875: Product image uploads from the product edit page complete instead of being rejected
  • #10982: The Answer Binding list in Page Builder includes Disposition Type and Disposition Category
  • #10987: The delete option on a corporate guide matches what the user is actually allowed to do
  • #10986: Components land where they are dropped in the page editor
  • #10968: The Selection Guide no longer reloads casket images on every page change
  • #10976: The Miscellaneous Sales print matches the standard receipt layout
  • #9731: The contract history shows an arrow between the old and new value
  • #9734: The package name column no longer cuts off text on first load
  • #10960: Show On GPL can be set while adding multiple services
  • #10966: Obsolete showrooms can be removed instead of accumulating on the overview
  • #10996 / #10997: Changing the items-per-page on GPL Pricing neither prompts about unsaved changes nor blanks the grid
  • #10990: DOMO Daily Sales no longer inflates contracts with package discounts, and adjustment rows carry descriptions
  • #10915: A company-level analytics sync that cannot run is reported rather than passing silently
  • #10919 / #10920: Published obituaries and Connections 2.0 events include their service addresses in every tenant
  • #10972 / #10973: The Family Link screen labels its action New Embed Code rather than New Integration
  • #10984: A custom field marked Required to Post is satisfied by the value entered
  • #10589: A selected product that no longer fits the family's answers is flagged instead of silently remaining
  • #10721: The Case Numbers settings labels read "Current" instead of "Next"

What's Next?

Verify on Post gives us a pattern to build on — expect the same idea of "reviewed, not just filled in" to reach further into the paperwork and the posting process. Now that merge fields are a single set, adding a new one means adding it everywhere at once, so the list should grow faster from here. And the order audit trail turns questions about a specific order into something we can answer from the record rather than from inference.

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

— The Solution Center Dev Team

Questions or Feedback?

We'd love to hear from you.

Get in Touch
An unhandled error has occurred. Reload X