Using an asynchronous event handler: trigger follow-up events

Use an asynchronous event handler to communicate with TeamForge, external systems, processes or system resources.

Important: To avoid accidentally locking the main TeamForge event queue down (and essentially rendering the system unusable), use only asynchronous event handlers (not synchronous event handlers) to trigger events.
Interacting with TeamForge is done as you would do it if you had to write a Java program to interact with TeamForge using its web services API. The only difference is that you will connect to localhost (since your handler is running locally) and that you already have a valid session ID.