In several occasions I have found myself needing to use a value from an LLD macro in a trigger prototype. Something like

{#LLDMACRO}.iregexp("^Something$",) = 0

Use cases I have come across:

• I have a LLD rule to discover tasks from a certain task scheduling software on windows. The discovery rule returns a few macros such as {#TASK.ID} and {#TASK.DESC}. I then have several item prototypes to discover the status of the task (active/inactive) and the last run status (ok/nok). I want to trigger but only if the task description contains the word "URGENT" using iregexp.
• I want to create a trigger of type HIGH for certain high priority windows services (specified by a global or host macro), and of type AVERAGE for all other windows services.

At the moment I have to artificially create an item prototype that echoes back the {#TASK.DESC} macro by doing one of these two things:

• a zabbix agent item prototype asking the agent to run something on the PC to echo back some information that I already have or
• an external check with key echo{#TASK.DESC} (thus occupying the external check agent for a trivial "echo back" type task)

There doesn't seem to be a good way to just use that value that I have already discovered in a sensible manner as part of a trigger prototype.