beautypg.com

2 variables for alert message – Kofax Communication Server 9.2.0 User Manual

Page 44

background image

Client Applications

Administrator‘s Manual Version 9.02.00

©Kofax, Inc.

44/203

Examples:

Warning: trigger threshold = 1000, re-activation threshold = 500: The warning message will be
posted if the queue length rises above 1000. If the queue length oscillates between 1100 and
900 no further warning will be given. Only after the queue length falls below 500, a second
warning will be posted if it then rises to 1001.

Warning retraction: trigger threshold = 500, re-activation threshold = 1000: If the system starts
with an almost empty queue, the check will be suspended. Only after the queue length has
risen above 1000 the check will be activated and the warning retraction message will be
posted if the queue length subsequently falls below 500.

4.9.3.1.3.3.6

Folder and File name

Enter the folder and file name of the warning message created in step 2. This message will be
posted if the warning or warning retraction is triggered.

4.9.3.1.3.3.7

Template Text Variable

This is a variable text that is saved in the alert definition. The text is limited to 80 characters
.For more information, see 4.9.3.2 Variables for Alert Message.

4.9.3.2

Variables for Alert Message

A message template defined for an alert may contain alert variables in the following recipient
fields: Department, Full name, Free text and in the KCS User ID within a TOPCALL address.

These alert variables may be used here:

Variable in Recipient

Replaced by this field from alert definition

(SET_ACTION)

{QueueRecipient}

TS_RECIPIENT / TS_RECIPIENT_GROUP

{QueueOriginator}

TS_ORIGINATOR / TS_ORIGINATOR_GROUP

{AlertFreetext}

TS_FREETEXT

The alert variables are resolved, i.e. replaced by the appropriate string field, when the alert
message is posted. An exact match is required for variables to be detected and resolved, the
variable name has to be put into the template exactly as defined, without prefix or postfix.

Alert message variables are used for two purposes:

a) in th

e ―User ID‖ address field: to send the alert message to that user

b) in all other fields: to get the field value into the message using cover variables. This is a
two-hop process. The alert variable gets the value into the message header, so that it is
stored with the message. Later, when the alert is viewed with a cover sheet, an appropriate
cover variable can pull the value into the message text.