Centercode Release Notes
Back to all updates

Weekly Patch - June 14, 2026

by Tony Fisher
New Features

New Features

Embed Interactive HTML Prototypes Right in Your Content

What we fixed: Want to drop a self-contained HTML prototype into your content? You can now upload it as an External Embed asset and reference it inline, and it'll render in its own isolated frame. No more crashes on save or rendering hiccups from pasting big chunks of prototype HTML into the content body.

See it in action:

  1. Head to the External Embed header-assets block and upload your HTML file.
  2. Reference it inline in your embed code.
  3. Publish and watch your prototype come to life in a tidy, sandboxed frame. 🎉

Good to know: This works best with a single self-contained file. A split HTML + CSS + JS set won't resolve its relative links, so bundle it all into one file for the smoothest results.

Fixes

Feedback

Your Display Name Stays Your Display Name in AI Summaries

What we fixed: When the AI summarized a feedback discussion, it was sometimes calling participants by their real first name (pulled from their profile) instead of the display name shown right there on the ticket. A little confusing, and not great for folks who set a display name specifically to control how they show up. We tracked it down to the summary reading names straight from the user profile and rebuilt it to respect the ticket. AI summaries now stick to the display name, just like the rest of the platform.

See it in action:

  1. Open a feedback ticket where the original poster has a display name that's different from their profile first name.
  2. Generate the AI summary on the discussion.
  3. Check the name in the summary. It'll match the display name on the ticket, no surprises.

Good to know: This keeps name-masking consistent everywhere, so participants always show up the way they expect to.

Data Engine & Custom Reports

Excel Exports No Longer Trip Over Long Element Names

What we fixed: Excel caps sheet names at 31 characters, so we shorten long report element names to fit on export. If that shortened name happened to land on a character Excel doesn't allow at the end (an apostrophe, for example), the whole export would fall over. We've smoothed that out, so long names won't break your export anymore.

See it in action:

  1. Build a report with an element that has a long name (bonus points for one with an apostrophe right around the 31st character).
  2. Export to Excel.
  3. Watch it export cleanly instead of throwing an error. 🎉

Integrations

What we fixed: If you set up a custom Public Link Base URL for an external Jira destination, the in-site "pill" links used it, but the "Jira link" dynamic tag in workflow and feedback macro emails was still pointing at the original Jira URL. The same record could send people to two different places depending on whether they clicked in-site or in an email. Now both surfaces use the same configured URL.

See it in action:

  1. In an external Jira destination, set a Public Link Base URL that's different from the technical base URL.
  2. Check the Jira "pill" link on a feedback record in-site.
  3. Trigger a workflow or macro email with the "Jira link" dynamic tag for the same record. The email link now matches the in-site one.