Product Presentation yuuvis® Momentum 2026 Summer

Core (Andreas, 20 min)

Groups become a first-class permission subject in yuuvis Momentum, propagated

from the identity provider through the JWT into role sets, alongside roles.

Audit entries capture more context (deletion reasons, content references,

impersonator info for cross-tenant operations) and can be cleaned up in a

date-bounded way via Commander.

Check-In / Check-Out introduces an exclusive editing lock, deletions also

remove attached relations, and document imports support an idempotency

header for safe retries.

Image PDFs are OCR'd with a hidden text layer for the Kairos AI integration,

and embedded ZUGFeRD XML lands automatically in the system:invoice SOT.

Webhooks carry more context (both MIME types, trace IDs in the User.info

webhook), and users can sign in with Entra ID accounts in the project context.

The catalogue concept from Spring is in production: uniform interface across

system and project types, registry-side value validation, and warnings on

ambiguous property references.

A mapping layer lets any number of tenant-specific schemas run in parallel

on shared Elasticsearch fields; existing tenants migrate without data loss.

CaseM 2.0 Client

Based on yuuvis® and the “Apps-in-a-Shell” approach, CaseM 2.0 is currently being developed. Further development of the CaseM 2.0 client:

Document Locking
- When a user locks a document, both its content and metadata are exclusively editable by that user; other users can cannot edit it.
- Main Users/Tenant Administrators can unlock any document.
- Each user has a dedicated view listing all documents they currently have locked.

Role based Dashboards
- Main Users/Tenant Administrators can define and manage default Dashboard templates per role.
- Users see a dashboard based on their role, showing only content assigned to or owned by them.