The main queue to which all trigger events are passed and which should trigger workflow instances initially or by correlation id

Queue ID	Format	Active MQ Name
bpm	XML	P360_BPM

Trigger Message Header

Please note that the General Headers from the Message Queue API page do not apply for the trigger message as this is not a request or a response!

Header name	Stored in	Values	Purpose
`JMSCorrelationID`	JMS Message header	<String>	Identifies the communication series that the message belongs to. (Not available in trigger events, only in responses where a correlation id was given in the request)
`MessageFormat`	JMS Property	XML/JSON	Similar to HTTP Content-type header. Can either be XML or JSON. Note ActiveVOS can only consume XML.
`P360TargetService`	JMS Property	<String>	The target consumer service within the target workflow.
`Origin`	JMS Property	<String>	Identifies the P360 server environment (DEV/QA/PROD) the message was sent by. Per default this is the value of system.name in the server.properties

Message Body

The message body consists of the corresponding payload of the trigger which has fired. Details on the payload and how the triggers can be configured can be found in the Trigger Configuration page within the Knowledge Base.