The ELO post-processing step allows you to store attributes and files from Forms in ELO.

Result of the ELO post-processing

MODE: Create

• A new folder in ELO is created

• the folder mask is assigned to the folder

• the mask attributes are assigned to the folder

• the map field attributes are assigned to the folder

• Attachments are uploaded as child Elements to the folder

• the file mask is assigned to each uploaded attachment

• if configured: a workflow is started

MODE: Update

• Updates an existing folder in ELO - identified by ObjectID or GUID

• If a folder mask is configured: an updated folder mask is set

• If a path is configured: moved the folder to the new location (including all subfolders/files)

• If a folder name is configured: updated the folder name

• Update the mask attributes: new values are added. If a value already exists, it will be overwritten. Old values that are not overwritten will stay

• Update the map field attributes. new values are added. If a value already exists, it will be overwritten. Old values that are not overwritten will stay

• Attachments are uploaded as child Elements to the folder

• the file mask is assigned to each uploaded attachment

• if configured: a workflow is started

MODE: Delete

• A single Sord Object in ELO is deleted - identified by ObjectID or GUID

Summary of naming conventions in ELO

Sord

A sord in ELO is any object. This can be a Folder, File, …

Folder

The Folder in ELO is a container that

• has ONE assigned Folder mask

• has N mask attributes (map-like key-value pairs) - also called objectkeys. These are directly connected to the assigned Folder mask. e.g. A Folder with the mask ‘invoice' has a mask attribute ‘invoice number’ but no attribute ‘birthday’.
  The mask attributes are String values only with a maximum length of 255 characters.

• has N map field attributes (map-like key-value pairs) - in ELO they are shown in the tab ‘Additional Infos’. They are used in various Business Solutions and Forms. Each attribute has an assigned domain (objekte, formdata, ...) and a type (string or blob). The type string is limited to a maximum length of 255 characters.

• has N child elements

  • other Folders

  • Files

File

These are actual BLOB files like JPG, PDF, …

They have:

• ONE assigned File mask

as well as

• N mask attributes

• N map field attributes

However, Portrait only allows setting the file mask. Attributes are only supported to be stored in the folder.

Detailed process description

MODE: Create

The creation process is done in the following order

• User submits Form

• Handlebars are applied, see order below

• Validations

  • Validation of Mask attributes - fieldProcessor + dialog "fields": [{...}]

  • Validation of Folder mask - mask

  • Validation of File mask - fileMask

• Folder is created or copied - according to path,folderName and sourcePath

• Folder mask is set

• Mask attributes are set

• Map fields are set

• Attachments, with the correct File mask, are uploaded

• Workflow is started

Validation of Mask attributes

Checked:

• Each mask attribute value can only contain max 255 characters.

Not Checked:

• The mask attribute is available in the folder mask. In this case, the attribute is ignored and not written to ELO.

Validation of Folder/File mask

Checked:

• If the configured mask is allowed to be set to a Sord of the type folder/file

MODE: Update

Same as in the CREATE mode. However, not all configurations are required.

• Path: if empty the folder won’t get moved and stays on the same path

• folderName: if empty the folder won’t get renamed.

MODE: Delete

• User submits Form

• A single Sord Object in ELO is deleted - identified by ObjectID or GUID

Configuration for MODE: CREATE

"¶Administration¶Business Solutions¶common¶Configuration¶Common file types¶Service Call Template"

Mask Attributes

There are two methods to configure which Mask attributes are selected to be written:

• 1:1 mapping of the dialog field names - this happens automatically

"pages": [
            {
                "label": "Person",
                "fields": [
                    {
                        "name": "damaged_person_first_name",
                        "displayText": "Vorname *",
                        "description": "First name",
                        "type": "TextBox",
                        "options": {
                            "required": true,
                            "confirmation": true
                        }
                    }
          ] 

A mask attribute with the key ‘damaged_person_first_name’ is selected.

• fieldProcessors

        fieldProcessor:
          - field: CM_WA_COMPANY
            value: "{{damaged_company_name}}"

A mask attribute with the key ‘CM_WA_COMPANY’ is selected.

The attributes are only marked to be written. At runtime, it is determined if the keys are available to be written for the configured folder mask. If some attributes are not available to be set for this mask they are simply ignored and not written.

The methods can also be combined:

"pages": [
            {
                "fields": [
                    {
                        "name": "damaged_person_first_name",
                        ...
                    },
                    {
                        "name": "damaged_person_last_name",
                        ...
                    }
          ] 

        fieldProcessor:
          - field: CM_WA_FULLNAME
            value: "{{damaged_person_first_name}} {{damaged_person_last_name}}"

Now 3 values will be marked to be written:

• damaged_person_first_name

• damaged_person_last_name

• CM_WA_FULLNAME

Map Attributes

Map attributes can be configured via the maps YML parameter

maps:
  - domain: objekte
    type: string
    fieldProcessor:
      - field: CM_WA_STATUS
        value: "aktiv"
      - ...
  - domain: objekte
    type: string
    fieldProcessor:
      - field: CM_WA_STATUS2
        value: "You can also use the same domain and type twice"
      - ...
  - domain: objekte
    type: blob
    fieldProcessor:
      - field: CM_WA_DESC
        value: "long value that is more than 255 chars ..."
      - ...
  - domain: formdata
    type: blob
    fieldProcessor:
      - field: CM_WA_HEILUNGSVERLAUF
        value: "{{accident_health_plan}}"

At runtime, the list domains and types are grouped together. For each domain and type the data is written separately.

Handlebars

The handlebars support the usage of the form parameter. In addition, we provide the following use of parameters from the user that submitted the form:

During the form submission, the handlebars are applied in this order:

1. Fieldprocessors

2. onSubmit.path, onSubmit.folderName

Therefore the result of the field processes can influence the onSubmit config.

Example ELO post-processing in Portrait

Example configuration:

 - id: createServiceCallELO
      onSubmit:
        type: ELO
        connection: sm_elo20_nav
        mask: PORTRAIT_SERVICE_PROTOCOL
        mode: CREATE
        workflow: newInsuranceClaim
        fileMask: ATTACHMENT
        path: "¶PortraitForms¶SERVICE_PROTOCOL¶{{SERVICE_PROTOCOL_PRIORITY}}"
        folderName: "{{SERVICE_PROTOCOL_MODEL}}-{{SERVICE_PROTOCOL_ISSUE}}-{{now format=\"yyyy-MM-dd HH:mm:ss\"}}"
        maps:
          - domain: objekte
            type: string
            fieldProcessor:
              - field: CM_WA_STATUS
                value: "aktiv"
          - domain: objekte
            type: blob
            fieldProcessor:
              - field: CM_WA_DESC
                value: "long text that can span more than 255 chars"
      dialog: |-
        { ...

Configuration for MODE: UPDATE

Example ELO post-processing in Portrait

Example configuration:

    - id: createExpense_elo_update
      onSubmit:
        type: ELO
        connection: sm_elo20_nav
        mask: SPESEN
        mode: UPDATE
        fileMask: Spesen_Beleg
        index: expenses
        path: "¶Alpha AG¶Spesenverwaltung¶{{BELEGDATUM_JAHR}}¶{{BELEGDATUM_MONAT}}¶{{BELEGDATUM_TAG}}"
        folderName: "{{SUBJECT}} ({{VENNAME}}) am {{BELEGDATUM_TAG}}.{{BELEGDATUM_MONAT}}.{{BELEGDATUM_JAHR}} - {{PUROWNER}}"
        fieldProcessor:
          - field: BELEGDATUM_JAHR
            value: "{{substring PURDOCDATE 0 4 }}"
          - field: BELEGDATUM_MONAT
            value: "{{substring PURDOCDATE 5 7 }}"
          - field: BELEGDATUM_TAG
            value: "{{substring PURDOCDATE 8 }}"

Config for Dialog

              "fields": [
                {
                  "name": "key",
                  "type": "Hidden"
                },

        - label: 'Bearbeiten'
          type: 'form'
          key: 'createExpense_elo_update'
          icon: 'edit'
          options:
            forwardFields:
              - key

Configuration for MODE: DELETE

Basic Example:

    - id: testEloDelete
      onSubmit:
        type: ELO
        connection: sm_elo20_nav
        mode: DELETE
      dialog: |-
        {
          "title": "ELO DELETE TEST",
          "successMessage": "Eintrag geloescht.",
          "languageCodeSuccessMessage": "ON_SUBMIT_SUCCESS_MESSAGE",
          "errorMessage": "Fehler beim Loeschen.",
          "languageCodeErrorMessage": "ON_SUBMIT_ERROR_MESSAGE",
          "submitText": "Loeschen",
          "languageCodeSubmitText": "SUBMIT_NOW",
          "description": "Delete ELO Entry",
          "pages": [
            {
              "label":"Allgemein",
              "fields": [
               {
                  "name": "key",
                  "type": "Hidden"
                }
              ]
            }
          ]
        }

Config for Dialog

              "fields": [
                {
                  "name": "key",
                  "type": "Hidden"
                },

        - label: 'Entfernen'
          type: 'form'
          key: 'createExpense_elo_delete'
          icon: 'trash-2'
          showInTableHeader: false
          showInDetailList: true
          options:
            forwardFields:
              - key

Troubleshooting

If you encounter some issues, look in the portrait backend log file. Watch out for error messages directly from ELO, which is logged during the process.
Example:

[TICKET:0ACDA9...][Die Maske Verkauf kann nicht für Ordner verwendet werden.]

The entire process is non-atomic, which means that in the case of an error, some data might have already been written to ELO. Some actions are required to classify the post-process step as a success, while others are not. Here is an overview: