So I was trying to create a VCO policy in 5.1 and basically uses an AMQP subscription and a trigger of onMessage to call a workflow.
I did this way back in Orchestrator. This post ( http://www.vcoteam.info/learn-vco/configure-the-amqp-plug-in.html ) walks you through how to do this....
In 5.1 when you click on the onMessage trigger object there is no bottom half of the screen where it shows what script or workflow to run.
The bottom panel says in grey letters... User Mode, Inspector Disabled.
This seems like a bug.
I can have a workflow that just loops waiting on events in the queue, but that makes life difficult in a world where we are trying to automate now we have to log in manually and make sure this workflow is running or things break....
Also if we run the listening workflow manually and have it loop, it spawns an async workflow and then gos back to listening.
Sometimes the async workflows show up as running in orchestrator and sometimes not.
If we put 1 message on the AMQP it executes but does not show up in orchestrator.
If we put 3 messages on AMQP all 3 execute and only 1 shows up in orchestrator.
If we put 5 messages, all 5 execute but only 1 shows up in orchestrator.
We are basically using an AMQP message to kick off provisioning workflow and that workflow publishes out an amqp message when it is complete.