When the DQMH Framework creates a new DQMH Event, it automatically opens the Module's API Tester Block Diagram. The diagram displays instructions for placing the Event Trigger Button (if the Developer checked the place button to API Tester in the Create Event UI)

I’ve noticed that I always create controls and indicators for firing the events since the API Tester’s purpose is to exercise all public events. To improve this process, I developed a plugin that automatically creates controls and indicators for every public request.

This plugin reutilizes source code for one of the Quick Drop plugins (already installed in LabVIEW) to create controls and indicators for any node.