Input Management can export documents to Documents on-premise (a.k.a.
LEXolution.DMS) classified using Document Classes. The
Administration
section provides two options for creating
and configuring document classes:
-
Neue Dokumentenklasse
- A button that allows the creation of a completely new class. -
Klasse importieren
- A button that enables the import of an already configured class (does not includeZUORDNUNG
since it depends on the external system and may differ).
GENERAL
-
Anzeigename
- A mandatory field, required for identifying the document class. -
Beschreibung
- A mandatory field, required for identifying the document class. -
Schema für Dokumenttitel
- Defines a custom title for the document after import, if needed. A set of placeholders can be utilized, as described in a tooltip.
Document data
In the document data section, different types of fields can be added, organized by category. The default values are not mandatory, except those described explicitly. Each field can have an English translation. All the fields have the following settings available to configure:
-
Wird in der Benutzeroberfläche für Clickworker angezeigt
- Determines whether the field is visible in the user interface when manually editing the document. -
Muss von einem Benutzer bestätigt werden
- Specifies if manual approval is required for recognized values based on recognition rules. -
Muss ausgefüllt sein
- Indicates whether the field must be filled in before exporting the document, or if it can remain empty. -
Wert kann nicht geändert werden
- Specifies if the field is read-only. -
Feldwert an Kinder vererben
- Controls whether the field value should be propagated to fields in the attachments (e.g., emails, beamsg files, or documents with attachments). The value is only propagated from the top-level document to all of its children.
FIELD TYPES
-
VERFAHREN, AKTE, FALL
- A field that is required if the document is to be exported to a matter or proceeding. -
BETEILIGTER (WINSOLVENZ.P4)
- A field that is required if the document is to be exported to participants in a proceeding. -
KOLLEKTOR
- A field used when the document will be exported via DMS KOLLEKTOR. If present, it is mandatory to set a default value (preliminary configured on-premise). Default values are available only when an external system (e.g. LEXolution.DMS) is configured (see sectionZUORDNUNG
). -
LEXOLUTION.DMS AKTENREGISTER
- A field used for exporting the document to a specific file register (Registerstruktur). The register value can be provided either as a default value or manually when selecting a proceeding. -
LOOKUP LIST
– A field that uses predefined lookup lists (Customization service). Adding a lookup list is mandatory when this field is set, but default value is not required. -
ABHÄNGIGE LISTE
- A field dependent on a LOOKUP LIST field. It is mandatory to configure this dependency and assign at least one option. For each dependency option, a dedicated lookup list with a default value can be set. -
DATUM
- A date field that can have the current date as its default value using the placeholder %DATE%. -
BETRAG
- A decimal field with two decimal places, primarily used for monetary values. -
DEZIMAL
- A decimal field that can have one or two decimal places. -
ZAHL
- An integer field primarily used for numbers. -
TEXT
- A text field that can have the lane name as a default value, where the document was imported, using the placeholder %LANE%. ATEXT
field can be also used to trigger an automation processor. In such cases, theName
of the field must have a specific value (see sectionAUTOMATISIERUNG
).
RECOGNITION
Each field can be associated with a Recognition rule (Regel hinzufügen) that uses either text or barcode matching. These rules rely on Regular Expressions to identify text within a document. Each recognition rule consists of several configurable settings:
-
Suchfenster verwenden (Rechteck)
– Limits the rule to be applied only within the specified part of the page. -
Seitenzahlen eingrenzen
- Limits the rule to be applied only to the specified pages. -
Rückwärtssuche von der letzten Seite
– Applies the rule to the specified number of pages counted from the end of the document. -
Suche nur auf der ersten und letzten Seit
- Limits the rule to only first and last page. -
Regulärer Ausdruck für einen Treffer
- Regular Expression to identify text within a document. -
Groß-/Kleinschreibung beachten
- Specifies whether the rule should be case-sensitive. -
Leerzeichen aus dem Wert entfernen
- Trims whitespace from the matched value, primarely used with IBANs. -
Doppelte Werte entfernen
- Removes duplicate matches from the results.
RULE TYPES
Barcode Match
Barcode match supports recognition of following barcode types:
Code 39
QR code
Textual Match
The Textual Match can recognize both an attractor and a value (e.g. in the text: “IBAN: DE25315613394292472443”, “IBAN” is the attractor and “DE25315613394292472443” is the value). The following settings apply specifically to the attractor:
-
Regulärer Ausdruck für den Attraktor
- Regular Expression to identify text within a document. -
Suchrichtung für Treffer
- When an attractor is configured, the corresponding value can be found either to the right of or below the attractor, based on the specified matching direction. -
Groß-/Kleinschreibung beachten
- Specifies whether the rule should be case-sensitive. -
Fallbacksuche nutzen
- If no attractor is found, this option allows the system to search for the value based on the rule without the attractor.
All recognition rules can be tested using a previously uploaded
document in the system by pressing the
ERKENNUNGSREGELN TESTEN
button.
AUTOMATION
Input Management allows automatic document processing, reducing the need for manual intervention. This is achieved through automation processors that use keywords to search for a specific dossier or proceeding.
-
Inso Default Processor
- Exports documents to an existing Winsolvenz proceeding. -
Bea Default Processor
- Exports beamsg files to an existing Winsolvenz proceeding. -
Dms Default Processor
- Exports documents to an existing DMS dossier or folder. -
Null Processor
- The default processor that does nothing.
Inso Default Processor KEYWORDS
Keywords for Proceedings (Verfahren)
Name | Description |
---|---|
ProceedingName | The description (Bezeichnung) of a proceeding |
ReferenceNumberExternal | The external Reference Number (AZ Gericht) of a proceeding |
ReferenceNumberInternal | The internal Reference Number (AZ Intern) of a proceeding |
TaxNumber | The taxNumber (Steuer-IdNr., Steuernummer) of a proceeding |
IBAN | The IBAN of a proceeding |
AccountNumber | The account number (Kto.-Nr.) of a proceeding |
To trigger automated processing, a TEXT field must have the
appropriate keyword set as Name of the field (e.g.: if the
documents will be processed using internal reference numbers, the field
shoould be set: Name - ReferenceNumberInternal, and the display
name set as desired, e.g. Anzeigename des Feldes - Az
Intern).
If any of these fields contain a value, the document will be exported to
the corresponding proceeding based on the provided information.
Keywords for Interested parties (Beteiligten)
Name | Description |
---|---|
IBANInterestedParty | The IBAN of an interested party |
InterestedPartyIBAN | The IBAN of an interested party |
ReferenceNumberInterestedParty | The reference number of an interested party |
BarcodeIdInterestedParty | The barcode of an interested party |
InterestedPartyName | The barcode of an interested party |
To trigger automated processing, a TEXT field must have the
appropriate keyword set as Name of the field (e.g.: if the
documents will be processed using internal reference numbers, the field
shoould be set: Name - ReferenceNumberInterestedParty, and the
display name set as desired, e.g. Anzeigename des Feldes - AZ
Beteiligte).
If any of these fields contain a value, the document will be exported to
the corresponding interested party based on the provided
information.
Additional parameters for Interested parties (Beteiligten)
Parameters | Values | Description |
---|---|---|
InterestedPartyIBANDetection | 0,1; true,false; yes,no; enabled,disabled | Determines if the system will detect an interested party by IBAN |
InterestedPartyReferenceNumberDetection | 0,1; true,false; yes,no; enabled,disabled | Determines if the system will detect an interested party by reference number |
InterestedPartyBarcodeIdDetection | 0,1; true,false; yes,no; enabled,disabled | Determines if the system will detect an interested party by barcodeId |
InterestedPartyFunctionType | Vertreterart | The function type of the interested party |
InterestedPartyType | BeteiligtenArt | The type of the interested party |
InterestedPartyNameSuffix | Zusatz | An appendix to the interested party |
Automated processing can be triggered using additional parameters by
pressing the ADD PARAMETER
button. Each parameter must have
the appropriate keyword set, and the values should be based on the
acceptable options listed.
If any of these fields match a value, the document will be exported to
the corresponding interested party based on the provided
information.
Bea Default Processor KEYWORDS
This processor checks the xjustiz_nachricht.xml of the beamsg file and searches for values within the following nodes:
aktenzeichen.absender
aktenzeichen.empfaenger
aktenzeichen.freitext
kurzrubrum
gegenstand
If any of these nodes contain information related to the AZ Intern or Case Number (internal or external reference number), the document will be exported accordingly.
Dms Default Processor KEYWORDS
Name | Description |
---|---|
ReferenceNumberInternal | Internal Reference Number (AZ Intern) of the dossier |
DmsContainerDescription | Description (Bezeichnung) of the dossier |
If any of these fields contain a value, the document will be exported to the corresponding DMS dossier or folder based on the provided information.
MAPPING
Each field, once configured, can be mapped to the LEXolution.DMS document data. In this section, values that are configured, recognized, and set by Input Management can be mapped to corresponding LEXolution.DMS fields. For this mapping to occur, an external system must be added:
-
Externes System
- Refers to the LEXolution.DMS instance (preliminary configured on-premise).
Document title
-
Schema für Dokumenttitel
- This field is used if the document requires a custom title after export. A set of placeholders can be utilized, as described in a tooltip. - The document title can be overridden based on rules. Multiple rules, utilizing regular expressions, can be configured. If a match is found, the document will be exported according to the value specified in the rule.
- Rules can also be configured in combinations; the rule will apply only if all configured fields match the required values.
Aktenregister
-
Aktenregister
- This field allows for configuring a default value for the File Register. This setting has priority; regardless of whether a dedicated AKTENREGISTER field is specified, the document will be exported to the register assigned in this section. - The file register can be overridden based on rules. Multiple rules, utilizing regular expressions, can be configured. If a match is found, the document will be exported according to the value specified in the rule.
- Rules can also be configured in combinations; the rule will apply only if all configured fields match the required values.
Collector
-
Kollektor Konfiguration nach Import
- This field allows for configuring a default value for the DMS Collector. This setting has priority; regardless of whether a dedicated KOLLEKTOR field is present, the document will be exported via the collector assigned in this section. - DMS Collector can be overriden based on rules. Multiple rules, using Regular expressions, can be configured. If there is a match, the document will be exported according to the value set in the rule.
- Rules can also be configured in combinations; the rule will apply only if all configured fields match the required values.
Mapping of the document data
In addition to the fields for the document title, file register, and collector, each field from the Document Class can be mapped to a corresponding DMS field based on the DMS-Thema (preliminary configured on-premise). Each DMS-Thema may have different target fields, but the most common mappings are as follows:
Document class Field Types | DMS-Thema Target Fields |
---|---|
DATUM | DatumEinAus |
DATUM | SchreibenVom |
LOOKUP LIST or Text | Dokumentquelle |
LOOKUP LIST or Text | DokumentKategorie |
LOOKUP LIST or Text | Kategorie |
LOOKUP LIST or Text | DokumentArt |
LOOKUP LIST or Text | Postweg |
Text | Kommentar |
Classname after import
If configured, the class name will be mapped to the Standard Document Class with the specified value. For further information, see ai-smart-claims.md.