{# "Read from Checkmk" for the Notification Method field. Checkmk's REST API has no endpoint listing the notification scripts installed in a site, so the view's `_notification_plugins` endpoint reports the plug-in names the rules already on that site use — which is where a third-party script shows up — merged with the plug-ins Checkmk ships with. The result refills the of every Notification Method field on this form; typing a name by hand stays possible. The second button writes the parameters of a plug-in into an empty Custom Plug-in Parameters field: those of a notification configuration that already exists on that site, or the empty skeleton the plug-in declares when there is none. A rule cannot name a configuration — the API has no field for its id — it binds to the one whose parameters it repeats, which is why starting from those matters. Checkmk also rejects a missing parameter with "A required (sub-)field is missing." without ever naming it. #}