Umm.
Delivered with Maerklins usual lack of professionalism I see. Specifically version control (the date of the document footer does not count)

Re: https://www.maerklin.de/...ads/Ereignisse_Modus.pdf
This sounds like the functionality described as "Alpha" in the 1.3.0 ChangeLog of over a year ago , and to the best of my knowledge is not actually available.
Does anyone know differently?

=== 1.3.0 Change Log : 21 April 2017 ===============================
Alphatest phase
Extensions Events
In the test are extensions to events. These are preliminary and will not be included in the release.

This includes:
Setting the status of S88 contacts.
Accessories and locomotive control as conditions for waiting or canceling.
=======================================================

=== Google Translate of help file ==================================
Extended functionality of the events

Basic operation events
Notes on the normal operation of the events
- triggering events
Events are basically only triggered by contacts. In the settings of the event, it can be determined whether documents or vacancies trigger the event. The control of the process is realized by control contacts. These allow or prevent the start of events.
- actions in the event
The actions in events are limited to triggering actions only. This means switching accessories, controlling locomotives, and calling other events. Specifically, no contact can be changed.
- Conditions in events
Contacts can influence the course of an event in events. A running event can be paused or canceled {The current options are actually "Delay" and "continue}

Advanced operation events
The essential extension is a generalization. Each action of the CS3 can trigger an event. In an event, each element can also be changed or used as a condition. This basically simple generalization of systematics realizes a very far-reaching extension of the capabilities of events.
- triggering events
When triggering events, all elements are conceivable - except for control contacts. These are a special form of contacts and are reserved for special applications.
- actions in the event
An action in the event can now be the editing of contacts. Thus, a contact can now become a flag and contain an intermediate result. The evaluation of these flags in further events then influences the course of the realized control.
- Conditions in events
Each element in the course of an event can be used as a condition. Events can be influenced depending on a turnout, a locomotive speed or the status of a contact.
- New elements
Additional elements are available for handling special conditions to control the events:
For emergency treatment, 2 additional actions have been introduced:
CS3 stop events stop. These can be used when the implemented controller detects a fault condition. To control the events
additional triggers were realized:
System Startup
CS3 Go
Events-Go These triggers can be used to bring the controller into a desired start state.

Some use cases
Below are some use cases of how the extended events can be used.
- Conditional switching of points

The process implements conditional switching of points. The first step realizes the query of the current position of the switch. This can be recognized by the question mark at the upper left end of the symbol. The setting condition will continue if the switch position is straight ahead. If the turnout is such, the 2nd command is executed and the turnout is switched.
Important note: When creating an event, you can not insert the same elements directly after each other.
Either an intermediate element is inserted and then deleted again, or you select another article and then select the correct article in the properties. Since it generally makes no sense to control the same article in quick succession, this restriction has been retained.
- Check conditions

The ability to edit contacts and subsequently evaluate the result creates the possibility to shift shared conditions into events. An event checks conditions and sets a flag if successful.
This flag is evaluated in the higher-level event and the further action is carried out in dependence. In this way, it is also possible to carry out multiple nested checks and, for example, Determine and adjust alternative routes.
=======================================================