ANDP brings together two products with their own vocabularies. The back office speaks Acta Nova (records management, in German), the front office speaks Gentics CMP (content and portals, in English). This page defines the terms as they are used in this documentation, maps them to the Acta Nova terms, and explains where each concept lives.
|
Tip
|
The Acta Nova user manual (RUBICON) contains a complete glossary of the records-management terms (Akt, Eingang, Erledigung, Ausfertigung, Geschäftsfall, Sachgebiet, …). This page only covers what matters for the dialog between front office and back office. |
Services and forms
- Service
-
What a front-office user sees in the service catalog: an administrative or business service that can be started online – "apply for a parking permit", "register a company", "change my address". Technically a service is a CMS page (or folder of pages) with a service description, links, downloads and one or more forms. The portal module reads the service tree from Mesh (
dialogportal_folder/dialogportal_contentschemas) and renders the catalog, favourites and – with the service catalog feature – the detail pages. Acta Nova’s manuals use "Service" for the same thing, seen from the back office: a set of forms, templates and workflow definitions that implement the service.
- Form (Frontoffice-Formular)
-
A form is defined in Acta Nova by the back-office administrator: it has an object type, references a subject area (Sachgebiet) and a catalog entry (for example a record type), and the Fachdaten properties assigned to that catalog entry become the form fields. Acta Nova’s tabs become the form pages. Publishing the form sends its schema to the front office, where it is stored in Mesh and created as an external form of type
andpin Gentics CMS, so that editors can place it on a page. The form is identified by its form key (also called form ID), which encodes the Acta Nova form and tenant.
- Form object types
-
Acta Nova supports five object types for front-office forms; they determine what happens on submit:
-
Record (Akt) – the main case: submitting creates a new record with an incoming document and can start a workflow. These forms can also be reused in dispatches to let the user edit the record’s data.
-
Incoming (Eingang) – answers a query about an existing record: submitting adds a new incoming to that record. Used as the communication form referenced by a message.
-
Expert search (Expertensuche) – a search form: the user enters parameters, the back office runs a predefined query and returns a result list (JSON, or Excel through the report mechanism). Results can link to other forms, pre-filled with data from the result row.
-
Subject-specific data object (Fachdatenobjekt) – creates a stand-alone data object (for example a "park" with all its properties) that other forms can reference.
-
External link (Externer Link) – redirects to an external URL, optionally with form data in the URL (for example to pre-fill an AFS form).
-
- Initial form and communication form
-
The front office distinguishes an initial form (opened without a business object; typically creates a record) from a communication form (opened for an existing business object – a record or incoming – from a message or task). The plugin and portal APIs mirror this:
/form/:key/…​versus/form/:key/businessObject/:boId/…​.
- Form flow, pages, summary
-
A form is filled in page by page. Data is sent to the back office on page change (and, if configured per field, immediately on input) for validation, visibility rules and computed properties. The form flow (sequence of steps, with or without summary page, with or without payment) is configured in the CMS form configuration (
forms.yml). Drafts are saved in Mesh so the user can continue later.
- Preconditions
-
Each form can have preconditions that are checked in the back office when the form is opened – for example "onboarding not yet done" or "only one application per year". If a precondition fails, the user sees an explanation and optionally a link to the form that fixes it.
- Business partner services (Geschäftspartnerservices)
-
Standard services shipped with the Dialog Portal plug-in: onboarding, change personal data, create organisation, change organisation, my permissions, manage organisation permissions. They are imported into Acta Nova as transport files and dynamic modules and then maintained like any other service. See Business partner services.
Communication from the back office
- Message (Nachricht, Ausfertigung)
-
A message is sent from the back office to one or more front-office users. In Acta Nova it is created as a dispatch (Erledigung) from a template and sent with the Dialog Portal dispatch activity; the dispatched copy (Ausfertigung) is what arrives in the front office. A message usually carries a document (the final document, Reinschrift) and can reference a communication form that the user must fill in to answer. Messages are stored in the front office (Mesh schema
acta_nova_notification), can be marked as read, moved and deleted by the user, and trigger an e-mail and – in the app – a push notification. See Messages.
- Task (Aufgabe)
-
A task is something the back office is waiting for from the user: answer a query by submitting the referenced form, or open a delivered document. Tasks are not stored in the front office; the Tasks MicroApp queries them live from Acta Nova (pending activities), so they reflect the current workflow state and disappear as soon as one of the addressed users has completed them.
- Business case (Geschäftsfall)
-
In the front office, the business case list shows all records (Akten) that are assigned to the user, with their documents and messages. that Acta Nova itself also has objects called Geschäftsfall and Geschäftsvorfall, which are something else; the front-office business case is a record.
- Report
-
The result of an expert search when it is requested as a file (Excel). The plugin asks Acta Nova to run the query, Acta Nova publishes the result back asynchronously, and the user downloads it from the portal. The Mesh schema
acta_nova_reporttracks the state.
- Published content
-
Documents and other binaries that Acta Nova pushes into the front office (for example to be linked from a message or a page), stored in the Mesh schema
acta_nova_published_content.
Users, organisations and roles
- Front-office user
-
A citizen, customer or business partner. Authenticated by Keycloak; in Acta Nova not a user but a person (Person) with the business partner flag. A Keycloak account exists before the person: the person is created when the user completes onboarding. The front office checks on login whether the business partner exists (
getBusinessPartnerPersonExistence) and redirects to the onboarding form if not. Anonymous access to selected services is possible, without a business partner.
- Back-office user
-
A regular Acta Nova user (case worker, administrator) with Acta Nova’s own permission system (groups, roles, positions, ACLs). Never logs in to the front office.
- Organisation
-
A business partner that is not a natural person. Front-office users can be linked to organisations and then act for them (see business cases, permissions). Managed through the business partner services.
- Roles
-
Three layers control what a front-office user may see and do:
-
Keycloak roles – assigned in Keycloak (or by an external identity provider), mapped to Mesh roles by the Keycloak plugin. The standard ANDP roles are
anonymous,guest,weak,strongandnormal, where weak/strong typically express the level of identity verification (for example a plain account versus an ID Austria login). -
Dynamic roles – application-specific roles loaded from Acta Nova on login (feature
feature_load_user_roles_from_acta_nova), for example "verified", "employee of department X" or "administrator of organisation Y". CMS pages and services can be restricted to such roles. See Dynamic roles. -
Acta Nova permissions – inside the back office, independent of the front office.
-
- User context
-
The information the front office sends to the back office about who is acting: the user ID and selected claims from the Keycloak token (configurable whitelist), the culture (language), the form key and – for communication forms – the business object. Transported in the
X-User-Contextheader from the portal to the plugin and from the plugin to Acta Nova.
Tenants and projects
- Tenant (Mandant)
-
An organisational partition of Acta Nova. All back-office objects – including forms – belong to a tenant. ANDP supports one front office in front of several tenants (a master data tenant for business partners and business partner services plus one or more business tenants); see Architecture.
- ANDP Mesh project
-
The Mesh project (default name
eGov) in which the Acta Nova Mesh plugin stores its data, separate from the content project that holds the CMS pages. Configured on both the plugin (meshProject) and the portal (ANDP_MESH_PROJECT).
- ANDP project (customer project)
-
A concrete installation for one organisation, derived from the ANDP reference project repository: Docker / Kubernetes setup, portal templates, CMS packages, FormGen customisations, Keycloak realm, configuration. Projects are updated to new ANDP versions following the reference project’s update guide.
Features
Many behaviours of ANDP are features that are switched on or off per project in the plugin’s
features.yml (or via environment variables) and partly mirrored in the portal: languages, onboarding,
terms of use, wizard, service catalog, prefill, compression, upload constraints, dynamic roles, FormGrid,
form flow, push notifications, debug. The
feature descriptions in the
Infoportal explain each one; the generated tables in
Mesh plugin configuration list the options.
German ↔ English term map
| Acta Nova (German) | This documentation | Notes |
|---|---|---|
Frontoffice / Backoffice |
front office / back office |
|
Frontoffice-Benutzer, Geschäftspartner |
front-office user, business partner |
a person in Acta Nova |
Frontoffice-Formular |
form |
published as external form of type |
Akt |
record |
created by an initial form of object type "Akt" |
Eingang |
incoming |
created on submit; also the object type of communication forms |
Erledigung |
dispatch |
created by the case worker, e.g. from a template; sent via the Dialog Portal dispatch activity |
Ausfertigung / Nachricht |
message |
what the user sees in the Messages MicroApp |
Reinschrift |
final document |
the document attached to a message |
Aufgabe |
task |
pending activity, queried live |
Geschäftsfall (Dialog Portal) |
business case |
a record assigned to the user; not Acta Nova’s own Geschäftsfall |
Fachdaten, Fachdaten-Eigenschaft |
subject-specific data, property |
the form fields |
Fachdaten-Aggregat |
aggregate |
a group of properties; multi-valued aggregates become lists / sub-forms |
Sachgebiet |
subject area |
determines where a record is filed and which process starts |
Aktentyp / Eingangstyp |
record type / incoming type |
catalog entries that define the form fields |
Expertensuche |
expert search |
search form / report |
Mandant |
tenant |
|
Stammdatenmandant |
master data tenant |
|
Vorlage (Erledigungsvorlage, Aktenvorlage) |
template |
initialisation scripts, referenced forms, processes |
Prozess / Workflow |
workflow |
|
Dialog Portal-Versand-Aktivität |
Dialog Portal dispatch activity |
workflow activity that sends a message |
Dialog Portal-Warteaktivität |
Dialog Portal wait activity |
waits for the user’s answer or document access |
Dynamische Rollen |
dynamic roles |
|
Onboarding |
onboarding |
