...
| Warning |
|---|
The event codes used in these examples are non existing event codes. For valid event codes, please see: Event Codes - 2017.02 and before |
From this list existing mappings can be deleted. For testing purposes it is also possible to generate a log event with the event code. This should trigger the configured action event mapping.
...
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?>
<eventActionMappings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="eventactionmappings.xsd">
<eventActionMapping actionId="action_configuration_action_scheduled_repeat_interval" eventCode="ENHANCE.EVENT"></eventActionMapping>
<eventActionMapping actionId="action_configuration_action_scheduled_resume" eventCode="RESUME.EVENT"></eventActionMapping>
<eventActionMapping actionId="action_configuration_action_scheduled_suspend" eventCode="SUSPEND.EVENT"></eventActionMapping>
</eventActionMappings> |
Delete multiple event actions or event mappings (since 2021.02)
It is possible to delete multiple event actions or event mappings at a time. Using the checboxes one or more action configurations or action mappings can be selected. Using the "Delete" button all selected entries will be removed.
Advanced options
In multi-MC setups, it is possible to combine the failover mechanism with event actions. See LogEventProcessor for more details.