Message Event
The Event tab has the following fields.
Field |
Description |
Candidate Event Key |
Expression built from the data of the incoming file change event. This expression must evaluate to a string and it is compared to the "key" field of the activity’s input. If the Candidate Event Key and the activity key match, then the process accepts the incoming message. For example, you may have JMS Queue Sender activity earlier in the process diagram and you are expecting a message in response to the sent message. Place the JMSCorrelationID from the header of the incoming message into the Candidate Event Key field, then place the JMSMessageID from the header of the sent message in the "key" field on the input tab. This expression is specified in XPath, and only data from the incoming event is available for use in this XPath expression. For more information about XPath expressions, see TIBCO ActiveMatrix BusinessWorks™ Process Design. |
Event Timeout (msec) |
A message may arrive before this activity is executed. This field specifies the amount of time (in milliseconds) a message waits if it is received before this activity is executed. If the event timeout expires, an error is logged and the event is discarded. If no value is specified in this field, the message waits indefinitely. If zero is specified, the event is discarded immediately, unless this activity has already been executed. |