Known limitations¶

This page lists things FedMS does not currently do, with links to the tracking issues. It is a deliberate transparency document — prospects, users, administrators, and developers should know where the boundary is.

Federation¶

The federation transport is not implemented yet¶

The data model is federation-ready (field_gitlab_id, field_sync, group hierarchy, status base field on group_relationship), but the transport layer that actually exchanges data between FedMS instances is in design.

Tracking: fedms/components/federation issues #22–#39.

User-identity bridging across instances is open¶

When the same person has accounts on two federated FedMS instances, the framework does not yet have a canonical way to recognise them as the same person. This is part of the federation transport design.

Conflict resolution is not specified¶

When the same field is edited concurrently on two federated instances, the current design does not specify the conflict resolution rule.

Notifications¶

A consistent notification subsystem is not yet shipped¶

Email templates exist (via Easy Email + the Send Email recipe), but the patterns, recipient resolution, scheduled delivery, and audit trail for notifications are not yet a unified system.

Tracking: fedms/components/federation#23, #24, #25, #27, #29.

Calendar invites are not yet supported¶

fedms/components/federation#33.

Tasks¶

Successor chains are linear, not graphs¶

A task pattern can declare successor patterns, which form a chain when an upstream task is completed. Cycles are not detected — if you create one, it will loop. This is intentional; the framework does not try to be a general workflow engine.

Tracking: fedms/components/tasks#15.

Task completion triggers are not all implemented¶

Different target types have different "completion" semantics (viewing a node vs. submitting a webform vs. downloading a media item). Not all variants are fully wired up.

Tracking: fedms/components/tasks#5.

Successors for book pages and embedded objects¶

Successor patterns currently work on top-level nodes / media / attachments, not yet on book sub-pages or embedded paragraph objects.

Tracking: fedms/components/tasks#25, #26.

Permissions¶

The permission matrix is provisional¶

The role × permission mapping in fedms_federation/config/roles_permissions.yml covers the common cases but does not yet fully express the per-role UX requirements. The roles Attendee, Speaker, Moderator, Service Provider, Observer currently have minimal role-specific permissions beyond the baseline member.

Tracking: fedms/components/profile#10.

Group-level permissions not yet driven by Roles Permission Builder¶

Site-wide permissions are built declaratively from roles_permissions.yml via the Roles Permission Builder module. The group-level permissions still need the module to be extended to support groups.

Tracking: same issue as above.

UX¶

Editing entities in modal dialogs is problematic when the entity contains a field widget that itself opens a dialog (e.g. a media field's media library). The inner dialog removes the outer.

Tracking: fedms/components/eca#7.

The current breadcrumb does not always reflect the event → session hierarchy.

Tracking: fedms/support#65.

Conditional fields are not native¶

Show-field-X-only-when-field-Y is a common request but is not supported as a first-class feature on event/session types. Workarounds involve field-group visibility rules.

Tracking: fedms/support#50.

Cosmetic but commonly raised.

Tracking: fedms/components/content#8.

Reporting¶

Some milestone views are capped at 10 rows¶

The per-milestone task list shows 10 rows with no pager option in some places.

Tracking: fedms/support#64.

Custom reporting requires PHP¶

For reports beyond what Views can express, you write a custom controller. There is no built-in report-builder.

Recipes¶

Recipe activation policy is not formalized¶

Three recipes ship today (send_email, zoom_video, attachment_recording). Whether they are applied per-tenant on provision, on-demand by the operations team, or via a future recipe-management UI is not yet decided.

Localization¶

Tenant-specific language overrides are limited¶

Customers sometimes want to rebrand the standard FedMS terminology ("Delegate" vs. "Participant", "Workshop" vs. "Module"). This is possible via the standard Drupal interface translation but not yet streamlined.

Tracking: fedms/support#9.

Modeler¶

BPMN.io modeler is being replaced¶

The current ECA modeler is being replaced. The data model stays stable; the UI changes. Don't write tooling that hard-codes BPMN.io specifics.

Tooling¶

`feature/advanced` E2E tests are not yet exhaustive¶

The advanced Playwright suite is being grown. Many user journeys are not yet covered.

Tracking: fedms/components/tests/playwright#1.

Deployment tests per-customer are not yet automated¶

Tracking: fedms/components/profile#20.

Next steps¶

Open issues — the full curated list.
Roadmap overview — the direction of travel.