Common action event

In the 'Common' category, events can be selected that are defined uniformly for all objects in Lobster Data Platform / Orchestration:


In the 'Common' category, events can be selected that are defined uniformly for all objects in Lobster Data Platform / Orchestration:


Event

Short description

New

This event is triggered in the user interface when a data object is created via 'New'. The new object can be read and edited, for example, with event actions, but is not yet saved in the database.

Create

This event is triggered when a data object is saved for the first time, i.e. created in the database.

Update

This event is triggered when a data object in the database is updated.

Copy

This event is triggered when any object with copy is created in the user interface. The copy can be read and edited e.g. via event actions, but is not yet saved in the database.

Delete

This event is triggered when a data object is deleted from the database.

Prepare Print

This event is triggered before a data object is printed. If multiple entities are selected for printing, the event is executed for each entity. However, all variables will be retained for all entities.

The following variables are available:

Name

Type

Description

fileName

String

The file name of the print result (without a file extension).
This variable can be manipulated to create an alternative file name.

printDocument

core:PrintDocument

The document to print.

printType

core:PrintType

The selected print type (e.g. PDF).

entity

Entity

The entity to print.

entities

List of entities

All entities to print.

pagination

core:Pagination

(Optional) The selected page layout.

►IMPORTANT◄ Since the events in the 'Common' category can match all objects in Lobster Data Platform / Orchestration, the event handling filter rule for these events should start with a Typprüfung that is as specific as possible.

If an error or cancellation occurs in the event processing that was triggered, then the entire action becomes ineffective. A Abort can be used to precisely define under which conditions a certain common action is effectively executed or notUsing rules or case distinctions in event handling. Example: A business object should not be deleted if the last change was less than 90 days ago.

System queries can appear before or after event processing:

  • With an interactive 'Delete', the system prompts for confirmation before the 'Delete' event is triggered. If 'No' is selected, the event is not triggered.

  • Events are processed immediately with 'New' or 'Copy'. If there are unsaved changes when clicking on 'New' or 'Copy', the query for 'Discard changes' will only appear afterwards and no new object will appear if 'No' is selected. However, a rollback is not triggered. Data adjustments in the course of event handling that do not affect the new or copied data record are therefore retained – unlike in the case of an error or cancellation in event handling – even if the changes are not rejected.

'Common events' in the data object's life cycle

The following diagram shows the role of events in the common life cycle of data objects:

images/download/attachments/62862887/image2018-8-9_12_9_48-version-1-modificationdate-1609768370214-api-v2.png

  • The 'New' and 'Copy' events can only be triggered interactively using the corresponding menu functions.

  • The 'creation' of an object in the database only occurs in an interactive process when the object is saved for the first time.

  • The 'Save' function can be repeatedly activated after data changes. In each case, this triggers the 'Update' event for the object.

  • The 'Delete' event marks the end of the object's life cycle.