Definition of an additional generic import action, e.g. linking imported records to an existing group entity.

Type for the definition of a single column in the EntitySubrecord

A ConfigMigration is checked during a full JSON.parse using a reviver function. If the migration does not apply to the given configPart, make sure to return it unchanged. Multiple migrations are chained and can transform the same config part one after the other.

Interface specifying overall object representing an enum with all its options as stored in the config database

The format that the JSON defined rules need to have. In the JSON object the Entities can be specified by using their ENTITY_TYPE string representation.

The type which defines which actions can be used for permissions. The type allows all strings defined in the actions array. E.g. "read" or "manage"

The type which defines which subjects can be used for permissions. This matches any entity classes, entity objects and the wildcard string "all" E.g. Child, new Note() or all

This filter can be used to filter an array of entities. It has to follow the MongoDB Query Syntax ://www.mongodb.com/docs/manual/reference/operator/query/{@link https}.

The filter is parsed using ucast ://github.com/stalniy/ucast/tree/master/packages/mongo2jshttps

Available validators that can be used to display errors to the user when a form is invalid

the validators config. This is an object where the key must be one of the DynamicValidators. The value to that key is specific to that validator. For example, the max validator requires a number while the pattern validator requires a string or regex. Compliant examples:

{
  min: 5,
  pattern: "[a-z]*",
}

Non-compliant examples:

{
  min: "abc",
  rabbit: true
}

This represents a static class of type . It can be used for passing a class from which new objects should be created. It can also be used to check the ENTITY_TYPE of a class For example usage check the EntityMapperService.

These are utility types that allow to define the type of FormGroup the way it is returned by EntityFormService.create

Specifies the role of an entity reference where "aggregate" = "has a" relationship where both entities have meaning independent of each other; "composite" = "part of" relationship where the referenced entity should not exist without the referenced entity.

Default is treated as "aggregate".

(role names following the UML association types)

Complete schema of an Entity containing multiple EntitySchemaFields.

This is generated from all @DatabaseField() of a class and then defines the transformation for that whole entity type.

Basic database read options supported by Database.

also see https://pouchdb.com/api.html#fetch_document

Basic database read options supported by Database.

also see https://pouchdb.com/api.html#fetch_document

Basic query options supported by Database.

also see https://pouchdb.com/guides/queries.html

A type that is used to document the return type of the platform observable. A variable that has this type shall only have two values that are encoded in a boolean way:

• true: the variable represents that the width of something is considered 'desktop width'
• false: the variable represents that the width of something is considered 'mobile width'

A map of entity types and the (selected) location properties of this type

Defines allowed notification channels.

Note: "push" is handled via individual device registrations and not part of this config currently.

Base type of notification rule.

These position states are used internally as animation states for the tab body. Setting the position state to left, right, or center will transition the tab body from its current position to its respective state. If there is no current position (void, in the case of a new tab body), then there will be no transition animation to its state.

In the case of a new tab body that should immediately be centered with an animating transition, then left-origin-center or right-origin-center can be used, which will use left or right as its pseudo-prior state.

Union type to enable type safety for report configs. Use this instead of the {@class ReportConfig}