Script Statement: Extends the notificationAn Automation Engine object type used to send messages to users and user groups. [Formerly called "CallOperator."]'s message text at runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start)..
:PUT_ATT_APPEND CALL_TEXT = Text
Syntax |
Description/Format |
---|---|
CALL_TEXT |
The name of the attribute whose value should be appended. |
Text |
The text that should be attached to the existing message text. |
This scriptA particular Automation Engine object type. statement can only be used in the Process tab of a Notification objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task. It appends the specified text to the end of the message text.
The existing message text remains the same because this script statement does not change the Notification object. The extended message text is only valid for the notification's particular execution.
The following peculiarities apply if you use blanks (see also: examples):
Note that the length of the text that you pass on must not exceed 8,000 characters for technical reasons concerning the databaseA database is an organized collection of data including relevant data structures..
The following example stores the current time in the script variable and put it to the READ buffer. Subsequently, a notification is activated.
:SET &TIME# = SYS_TIME("HH:MM")
:PUT_READ_BUFFER
TIME# = "&TIME#"
:SET &CALL# = ACTIVATE_UC_OBJECT(CALL,
BACKUP.END)
The notification reads the script variable's value from the READ buffer. The current time is appended to the notification's message text.
:READ &TIME#,,
:PUT_ATT_APPEND
CALL_TEXT = " &TIME#."
The following examples serve to explain the use of blanks. The notification's message text is "Start checking the".
1) The text is correctly printed because a leading blank is inserted. Note that blanks are not automatically inserted.
:PUT_ATT_APPEND CALL_TEXT = " Server processes"
Output:
Start checking the Server processes
2) Blanks that are used at the end of texts are truncated as the following example shows:
:PUT_ATT_APPEND CALL_TEXT = " Server
"
:PUT_ATT_APPEND
CALL_TEXT = "processes"
Output:
Start checking the Serverprocesses
3) If a text only consists of blanks, these blanks are also ignored.
:PUT_ATT_APPEND CALL_TEXT = " Server"
:PUT_ATT_APPEND
CALL_TEXT = " "
:PUT_ATT_APPEND
CALL_TEXT = "processes"
Output:
Start checking the Serverprocesses
See also:
Script element | Description |
---|---|
Adds recipients to a notification at runtime. | |
:REMOVE_ATT | Removes notification recipients at runtime. |
:PUT_ATT | This is used to change the value of an attribute during generation. |
GET_ATT | This functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… returns the values of a taskAn executable object that is running. Tasks are also referred to as activities.'s attributes during generation. |
GET_ATT_SUBSTR | Supplies part of a notification's message text. |
Script Elements - Read or Modify Objects
About Scripts
Script Elements - Alphabetical Listing
Script Elements - Ordered by Function
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |