Current Moment.js format for Material Datepicker as a readonly signal (e.g., "DD.MM.YYYY"). We have to use different format for datepicker because Angular DatePipe and Moment.js use different format syntax: e.g. dd.MM.yyyy in DatePipe shows as 22.01.2026, but in Moment.js it would show as Th.01.2026.

Current default shortDate format as a readonly signal (Angular DatePipe format, e.g., "dd.MM.yyyy")

Current default datetime format as a readonly signal (Angular DatePipe format, e.g., "dd.MM.yyyy HH:mm")

Display metadata per action. Orange is reserved for app chrome, so even imported uses an orange-tint background with deep-orange text — never the brand primary fill.

The list of action strings that can be used for permissions

The realm role that grants access to the administration features, as checked by the admin routes' UserRoleGuard configuration.

Section keys in DatabaseRules that carry special semantics instead of mapping a user role. The underscore prefix marks them as internal so they cannot collide with a realm role name.

A user role starting with this prefix is reserved and never resolved.

All section keys that must never be resolved as if they were user role names, even if a realm role with the same name exists.

A new key added here does not automatically stop inheriting the "_default" rules; see inheritsDefaultRules.

Add default view:note/:id NoteDetails config to avoid breaking note details with a default config from AdminModule

Add default view:note/:id NoteDetails config to avoid breaking note details with a default config from AdminModule

Special filter with pre-defined categories of Todo items.

Preload all components registered in the ComponentRegistry so their JS chunks are cached by the service worker and available offline even before the user has visited every page.

Runs once in an idle callback to avoid blocking the main thread after login.

the id through which the available attendance status types can be loaded from the ConfigService.

Null object representing an unknown attendance status.

This allows easier handling of attendance status logic because exceptional checks for undefined are not necessary.

CASL subject the audit records are keyed under (see replication-backend #4026).

A readonly array of all locales available

Explanation for the synthetic "initial snapshot" entry, shown both inline in its diff and as the badge tooltip (single source of truth).

Maps the backend audit operation to the displayed ChangeAction.

Resolves once/if it is possible to directly install the app

The deferred beforeinstallprompt event, to be triggered on user request

The registered listener, kept so resetPWAInstallListener can remove it again

Our own error classes that describe what failed precisely enough that all their occurrences belong into a single issue in remote monitoring, no matter which component, route or async call site ran into them.

For these, Sentry's default grouping by stack trace actively hurts: they are thrown from one central place, while the stack differs per caller and even per build (releases without source maps report minified frames). One problem then scatters across a dozen issues that each have to be triaged separately, and archiving one of them does not silence the others.

Only add error types whose name and message already identify the problem on their own, so that the stack adds nothing but noise. Generic errors (Error, TypeError, ...) must keep the default grouping - for those the stack trace is the only thing telling two unrelated bugs apart.

How PouchDB words a rejected write, after fingerprintKey normalization.

Placeholder type for an exception reported without one.

Sentry builds an issue title from the reported exception's type and message, and lists an issue whose exception carries no type as <unknown> - which says nothing at all in a list of issues, and hides the message that would have. The generic name is no loss: it is what an Error subclass reports anyway unless it sets name explicitly (see CAUSE_GROUPED_ERROR_TYPES).

Maximum number of times an identical event is sent to remote logging within one app session (page load). Guards against error loops (e.g. an error thrown on every change detection cycle) flooding remote monitoring with thousands of duplicate events.

How much of an error message is kept as the reported one (see reportNormalized). Generous enough for any message written to be read, and a backstop against the ones that turn out to be a serialized document or a web page.

Placeholder for a connectivity failure, which every browser words differently ("Failed to fetch" / "Load failed" / ...) while describing one problem.

Substituted wherever an error message is used as a grouping key or shown as the cause of another error, so that a mix of browsers neither splits an issue nor makes its title flip-flop between its events.

Data that varies between occurrences of the same problem and therefore has to be masked before an error message can be used as a grouping key. Order matters: the more specific patterns have to run before the plain number.

Wordings for a lazily loaded application chunk that could not be fetched.

These are requests that did not arrive, like any other connectivity failure: the device is offline, or a new deployment replaced the chunk that the still-running app asks for. Which of the two it was is not visible from the error, and neither is actionable per chunk - so they belong in the shared network issue rather than in one issue per chunk URL and browser wording.

Error names that browsers use for requests that were cut off before completing, rather than answered with an error.

Common network/connectivity error patterns shared across the application. These indicate transient failures (offline, DNS, proxy issues) rather than application-level errors.

HTTP statuses of a request that never reached the application's backend: 0 for one that got no response at all, the others reported by an infrastructure component in front of it.

Fields OpenStreetMap may use for the place a person would name as their town, ordered from the most specific to the widest area. Many places have no city at all: an address in a Dublin suburb, for example, only carries suburb.

Maps component name to the service signal property and required operation for permission checks.

Stable URL prefix used for entity routes loaded from runtime config.

sessionStorage key tracking how many times we've auto-reloaded due to a failure loading config.json, so a persistent failure (e.g. offline) doesn't reload-loop and flood error monitoring.

All temporary config migrations that fix legacy data formats. Applied by both ConfigService (Angular app) and the admin CLI. Order matters: earlier migrations may produce output consumed by later ones.

Config keys whose value is a filter object (MongoDB-style query) defined by admins, e.g. the fixed filter of a RelatedEntities view, the filter of a prebuilt filter option or the prefilter of a matching view's side.

Filter operators whose value is a list of nested filter conditions.

Entities do not provide a calculated "isActive" property anymore. Report queries selecting on it have to use the equivalent query helpers instead.

Migrate navigationMenu items that use a hardcoded entity route link to the entityType format.

Migrate ShortcutDashboard widget link values that point to entity routes to use the runtime /c/ prefix.

Extracted here (rather than kept only in ConfigService) so the CLI's latest-config-formats migration can also persist this fix to production config documents, not just apply it transiently in the running app.

Older configs contain a full copy of the prebuilt "tasks due" filter, whose options selected on calculated properties that do not exist anymore. Drop the stored options so the definition provided by the app is used.

Entities do not provide a calculated "isActive" property anymore, so a configured filter selecting on it cannot match anything.

isActive: true is simply dropped: lists exclude archived records by default now (see NOT_ARCHIVED_FILTER), which is exactly what the condition used to express.

isActive: false (i.e. archived records only) is dropped as well. It has no equivalent in a configured filter anymore, because the default not-archived condition is combined with $and and any explicit "archived" condition would make such a filter match no record at all. Users can include archived records through the list's "show inactive" toggle instead.

Use this token to provide (and thereby register) custom implementations of ConflictResolutionStrategy.

{ provide: CONFLICT_RESOLUTION_STRATEGY, useClass: MyConflictResolutionStrategy, multi: true }

see ConflictResolutionModule

highlight color for the entry that covers the current date

Container for custom Angular Validator functions.

Extend MAT_NATIVE_DATE_FORMATS to also support parsing. dateInput uses a getter so it always reflects the current global date format from date.static.

The "_default" role, whose permissions every logged-in user has in addition to the permissions of their own roles.

The "_public" role, whose permissions apply to visitors before login.

The reserved roles with their user-facing name and description, so that all places explaining them to the user (roles overview, permission matrix, permission dialogs) use the same wording.

Ordered as they should be listed to the user.

Standard default-value strategies that are used in the application. Add further providers to your modules or the AppModule to extend.

The keyword a user has to type to confirm an action that deletes data irreversibly.

Decorator to annotate a class that serves as dynamic component A dynamic component can be referenced from the config with the name defined on the decorator.

IMPORTANT: The component also needs to be added to the ...Components list of the respective module.

fresh empty matrix model; a factory (not a shared const) so callers can never alias a mutable object

see environment.ts for explanations

Central environment that allows to configure differences between a "dev" and a "prod" build. For deployments, the assets/config.json can be used to override these settings as well.

The file contents for the current environment will overwrite these during build. The build system defaults to the dev environment which uses environment.ts, but if you do ng build --env=prod then environment.prod.ts will be used instead. The list of which env maps to which file can be found in .angular-cli.json.

4XX statuses that occur during normal operation (and are handled by callers or the auth layer), so they are not reported to remote logging.

(Extended) faker module

Number of documents fetched per request when loading the complete dataset (see PaginatedDataSource.getAllData).

Country whose addresses are written as "Street 12, 12345 City", the format GeoService.reformatDisplayName produces.

Doc fields that are internal/metadata and never shown as user-facing field changes.

A map to prevent old configs from breaking.

Sample raw data that can be used in Storybook and tests.

ID of the Note category ConfigurableEnumValue in the config database.

Technical roles that serve a special function in the authentication server (e.g. granting account-management API access, or opting a user out of email 2FA). They must not be deleted from this admin UI, and their description is managed elsewhere, so it stays read-only here. They may still carry additional permission rules like any other role.

Base route of the role management admin UI, to link to a role's details from elsewhere. Mirrors the "user-roles" paths registered in admin.routing.ts.

Hard upper bound on individual Keycloak network operations (init, token refresh). Picked well above expected RTT but short enough that a hung proxy/upstream surfaces a clear failure to the user.

Backoff schedule for explicit user-initiated login retries.

Minimum remaining lifetime (in seconds) requested when refreshing the token in the background. Matches keycloak-js's updateToken(minValidity) argument.

Backoff schedule for background token refreshes (OnTokenExpired). Kept short — if the background refresh keeps failing, the next API call's 401 will trigger an explicit login, so there is no point retrying for many seconds and stalling the user's request.

localStorage key prefix under which SyncedPouchDatabase records when a database last completed a sync (one key per database).

sessionStorage key used to signal that a reset is pending. Set before a page reload; checked on the next bootstrap in runPendingReset.

The screen size where anything smaller and this size itself is considered mobile while anything strictly larger is considered desktop.

Use this instead of referencing localStorage directly.

Tests otherwise have to stub Storage.prototype, which belongs to the worker process rather than the module registry — Vitest's isolate does not undo it, so an unrestored stub leaks into every later spec file and makes unrelated tests read a fake localStorage. Injecting a fake avoids that entirely.

Use this instead of directly referencing the window object for better testability

Edit the menu as a flat, indented list (see flat-tree): every menu item can hold nested sub-items.

Transform DefaultValueConfigInherited and DefaultValueConfigUpdatedFromReferencingEntity configs to DefaultValueConfigInheritedField.

Select records that are not archived.

The inactive flag is only written when a record gets archived, so for the vast majority of records the property is missing entirely. A plain { inactive: { $ne: true } } does not reliably match those in a database query, so the missing case is spelled out as its own condition.

The prefix which is used to find the ViewConfig's in the config file

Top-level route segment under which public (anonymous) forms are served.

Kept in a module without imports of its own, because the app bootstrap needs this value (see bootstrap-environment.ts) and must not load the public form components and their dependencies while doing so.

Admin list + details views to manage ReportEntity configs, registered the same way as other "Templates and Forms" entities (e.g. EmailTemplate).

Edit the definition as a flat, indented list: only groups can hold nested items, queries are always leaves.

This allows the ReportEntity to also be used as a constructor or in the EntityMapper

Marks a class to be the target when routing. Use this by adding the annotation @RouteTarget("...") to a component. The name provided to the annotation can then be used in the configuration.

IMPORTANT: The component also needs to be added to the ...Components list of the respective module.

RoutingModule for UserModule related routes. Separating these routes from the main AppModule routing allows lazy-loading of modules.

A shown calculation older than this (seconds) is treated as stale/outdated.

Delay (ms) before a changed search text is applied, so that typing does not trigger a filter update (and, for server-side data sources, a DB request) on every single keystroke.

Thresholds for attendance percentage coloring.

Select Todo records that have been completed.

Select Todo records that have not been completed.

TodoService.uncompleteTodo resets completed to null instead of removing the property, so records without the property and records holding null both have to be matched. Each branch is an object (rather than a plain null value) so that the filter can also be used as the initial filter of a list, where FilterService inspects it to prefill new records.

Names for the response statuses that are reported to remote monitoring.

Monitoring groups a reported message by its normalized text, and that normalization masks numbers (see fingerprintKey), so a status interpolated as a number would collapse every unexpected response into one issue - the mixed bucket this exists to prevent. In AAM-DIGITAL-77H a rejected write, a malformed query and a replication checkpoint read all shared one title, and none of them could be told apart or triaged. Naming the status keeps the message text static (as the logging conventions require) while giving each root cause its own issue and a title that says what happened.

Only statuses that plausibly occur are listed, because each one here should mean a different response:

• 400 a malformed request (a bad query, or a proxy mangling the url)
• 413 a payload over the reverse proxy's limit, e.g. a large attachment
• 429 throttling Anything else shares one bucket via unexpectedResponseMessage and is still reported with its numeric status in the logged context.