A user asked about a key to translate the "trigger" values for scripts returned via the edgeDX API. Another user mentioned they have the information and will share it. The answer is found through the use of Github Copilot and AI.
Read the entire ‘Translating Trigger Values in ControlUp Scripts’ thread below:
Does anyone know if there is a key to translate the “trigger” values for scripts returned via the edgeDX API to what their actual trigger is? For instance I have a few scripts set to use the trigger “Custom Action – User” which seems to translate to a “tigger” value of 9998. I’m just wondering if there is a key somewhere I can reference?
Stay tuned. I think I have those somewhere
@member
Awesome thanks Joel!
@member So I dropped that table into github copilot and asked it to build me a switch statement to populate user context and description variables respectively and I’m kind of uncomfortable with how well that worked. Apparently all hail our new AI overlords.
Continue reading and comment on the thread ‘Translating Trigger Values in ControlUp Scripts’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops, ControlUp Scripts & Triggers