Variables defined by the rule engine

The following variables are defined by the rule engine:

ias_Address The address of the message. For example, myclient\myqueue.
ias_ContentSize The size of the message content. If the message is a text message, this is the number of characters. If the message is binary, this is the number of bytes.

ias_ContentType The type of message:

IAS_TEXT_CONTENT	The message content consists of unicode characters.
IAS_BINARY_CONTENT	The message content is treated as an uninterpreted sequence of bytes.

ias_CurrentDate The current date.
A string can be compared against ias_currentDate if it is supplied in one of two ways:
- as a string of format, which is interpreted unambiguously.
- as a string according to the date_format database option set for the client message store database.
  See Setting database options and date_format option [compatibility].
ias_CurrentTime The current time.
A string can be compared against ias_CurrentTime if the hours, minutes, and seconds are separated by colons in the format hh:mm:ss:sss. A 24-hour clock is assumed unless am or pm is specified. See time_format option [compatibility].
ias_CurrentTimestamp The current timestamp (current date and time). See time_format option [compatibility].
ias_Expires The date and time when the message expires if it is not delivered.
ias_Network Information about the current network in use. ias_Network is a special transmission variable. It has a number of built-in attributes that provide information regarding the current network that is being used by the device.
ias_Priority The priority of message: an integer between 0 and 9, where 0 indicates less priority and 9 indicates more priority.

ias_Status The current status of the message. The values can be:

IAS_CANCELLED_STATE	The message has been canceled.
IAS_EXPIRED_STATE	The message expired before it could be received by the intended recipient.
IAS_FINAL_STATE	The message is received or expired. Therefore, `>=IAS_FINAL_STATE` means that the message is received or expired, and `<IAS_FINAL_STATE` means that the message is neither received nor expired.
IAS_PENDING_STATE	The message has not yet been received by the intended recipient.
IAS_RECEIVED_STATE	The message was received by the intended recipient.
IAS_UNRECEIVABLE_STATE	The message has been marked as unreceivable because it is either malformed or there were too many failed attempts to deliver it.

ias_TransmissionStatus The synchronization status of the message. It can be one of:

IAS_UNTRANSMITTED	The message has not been transmitted to its intended recipient message store.
IAS_TRANSMITTED	The message has been transmitted to its intended recipient message store.
IAS_DO_NOT_TRANSMIT	The recipient and originating message stores are the same so no transmission is necessary.
IAS_TRANSMITTING	The message has been transmitted to its intended recipient, but that transmission has yet to be confirmed. There is a possibility that the message transmission was interrupted, and that QAnywhere may transmit the message again.

For an example of how to create client store properties and use them in transmission rules, see Using custom client message store property attributes.

Send feedback about this page via email or DocCommentXchange