From 9d6d44d8bac34afa72407a45de28989a050d4e4f Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Thu, 19 Dec 2024 16:50:40 -0500 Subject: [PATCH] feat(eventtemplates): document Preset event templates --- .../download-edit-and-upload-a-customized-event-template.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/guides/_subsections/download-edit-and-upload-a-customized-event-template.md b/guides/_subsections/download-edit-and-upload-a-customized-event-template.md index 69e1ec2..3f6085f 100644 --- a/guides/_subsections/download-edit-and-upload-a-customized-event-template.md +++ b/guides/_subsections/download-edit-and-upload-a-customized-event-template.md @@ -25,6 +25,12 @@ event types in the selected `target` application, with default values for each event option. This is not a true *Event Template* and does not have an `XML` definition to download. +Finally, **Cryostat** also includes some *Preset Event Templates*. These behave like +*Custom Event Templates* in that the event definition is stored by **Cryostat**, rather +than the `target` application, but are handled separately can cannot be deleted +like *Custom Event Templates*. *Preset Event Templates* can only be added to a **Cryostat** +instance by adding files to a specific configuration directory and restarting **Cryostat**. +
  1. {% include_relative _subsections/common/select-target-application.md