Hey Tines Community! Here’s a quick round-up of recent platform updates from late July 2026. These include some major improvements to Cases, a new field type for Records, and better change control tracking.
Cases Get Full Visual Design in the Storyboard
You can now visually define every aspect of a case directly in the storyboard when using the create case tile. This means building case structure without leaving your workflow canvas. The new editor supports rich-text formatting for descriptions and content blocks, making it easier to create polished, readable cases.
This visual approach also sets the foundation for the formula support and change control improvements below.
Source: Visually create cases in the storyboard
Formula Support Across All Case Elements
Formulas now work throughout case creation, evaluated at runtime when the case is built. You can reference standard keys like INFO and RESOURCE, or pull in upstream event data, to dynamically populate any part of a case:
- Description and case blocks (via the
/formatting menu) - Primitives: case name, team, status, priority, assignees, tags
- Properties: fields and metadata
- Activity, relationships, and controls: case actions, linked record IDs, task names/assignees, requirement names/conditions
This makes cases far more flexible and adaptive to the workflows that create them.
Source: Formula support for case details
Docs: Case structure overview
Docs: Formatting and references
Change Control Now Tracks Case Changes
Change control has been updated to track every modification made to case elements in the storyboard. Each draft clearly shows changes to case content, structure, primitives, and properties, giving you full visibility and governance over how cases evolve.
This works alongside the new visual case editor to keep your workflows auditable and safe.
Source: Track cases with change control in the storyboard
JSON Field Type for Records
Records now support a JSON field type, letting you store structured data directly in a record without extra parsing. Use it to capture API responses, configuration objects, or nested metadata in a single field while preserving the structure for downstream use in stories and actions.
Note: JSON fields are not currently filterable and behave like large text fields in that respect.
Links & Resources
Original Updates:
- Visually create cases in the storyboard
- Formula support for case details
- Track cases with change control in the storyboard
- JSON in records
Documentation: