Constants

Constants are used to store information that can be used during the processing of a script task. They are grouped into the following sections:

Constant Description
A String entry field
A value entry field. The engine will try and determine its type based on where it is used.
A numeric entry field
A date picker field
A date and time picker field
A True/False Boolean picker field
A colour picker control
Returns an empty string
Returns a Boolean to indicate whether or not all required fields have been set
Constant Description
The agent's access level
The client's name
The agent's CTI extension number
The agent's first name
The agent's full name
The agent's login code
The agent's name
The project name
The project ID
The project group name
The name of the reporting team the agent is assigned to
The ID of the reporting team the agent is assigned to
The agent user ID
The current skill name
The current skill ID
The agent's surname
The agent's team name
[AGENTTENANT] The current client's name
Constant Description
The current date and time
The current day number
The current part of the day, morning, afternoon or evening
The date in format “dd MMMM yyyy”
The time in format “HH mm ss”
The current month number
The current date and time in format "dd-MM-yyyy HH:mm:ss" unless overwritten by the [SCRIPTDATEFORMAT] variable
The current date in format dd/MM/yyyy
The current time in format HH:mm
The current day name
The current month name
The current date in format "dd-MM-yyyy" unless overwritten by the [SCRIPTDATEFORMAT] variable
The current year
Constant Description
The CLI data as passed down from the CTI Toolbar
The DDI data as passed down from the CTI Toolbar
The name of the screen currently shown in the main script flow – allowing it to be accessed for pop-ups
The name of the current screen
The mode of the script: BUILD, TEST or LIVE
The name of the script
Defines the date format string used by the system
Defines the “now” format string used by the system
Defines the keys to be handled by the GLOBAL_ONKEYPRESS global function as a comma separated list of keys
The result of external DLL function calls
Sets the return value for the dictionary commands if it is not able to locate a key. The default value is **NO KEYS**

Information on the “wrapper” that the engine is running in:

  • CMGR for contact manager or
  • SCRIPTRUNNER if running as a back office script
If set it only allows one function to be run in the engine/parser at a time
Used to delay the processing of any XXX_ONKEYPRESS functions by x milliseconds
The code page ID for the current script
The selected call outcome. It will only be set after you have selected a call outcome.
The selected call outcome sub code. It will only be set after you have selected a call outcome
The ID of the history record being only available in script end
If this variable is set to TRUE then each parser/engine will no longer raise warning about unknown variables
The id of the calls list used by the current record
Holds any call notes that you want to save to the history record when the call is coded
Saves a "sales" value with the call history record (to aid reporting)
The ID of the related record, i.e. pEmail
The priority of the current task
The ID of the task
The ID of the task type for the task
If this variable is set to TRUE then each function called will be added to the script flow information XML data
The time zone offset between client and infinity webserver
Returns the time the script has been open
Constant Description
Matches to the AllowInUseReCheck Project Setting so it can be changed in the script
Matches to the AllowInUseContinue Project Setting so it can be changed in the script
Matches to the AutoCheckInterval Project Setting so it can be changed in the script
Constant Description
The current DB Connection string
The format that dates need to be converted to when issuing insert/update statements to non MSSQL databases. For MySQL this would need to be set to "yyyy-MM-dd HH:mm:ss".
It is used to insert a record where the new ID/key has to be obtained before the insert command is run. For instance in MySQL where IDs are UUIDs these can be obtained by running:

The ID field is then set to this value and the [DBKEYININSERT] variable is set to TRUE.
The query to retrieve the ID of the last record inserted. For MySQL this would be ; SELECT LAST_INSERT_ID() Assuming the ID isn’t a UUID and needs to be generated before the insert (save command)

The query that can be used to obtain information about a table. This way the Script Engine is able to determine the primary key of the table and the fields and their types when using non MSSQL databases. For MySQL this would need to be set to:

SELECT COLUMN_NAME AS FIELDNAME, 'PRIMARYKEY' AS FIELDTYPE

FROM information_schema.`COLUMNS` C

WHERE table_name = '[TABLE]: '

AND COLUMN_KEY = 'PRI'

UNION

SELECT CONCAT(TABLE_NAME, '.', COLUMN_NAME) AS FIELDNAME, DATA_TYPE AS FIELDTYPE

FROM information_schema.`COLUMNS` C

WHERE table_name = '[TABLE]: '
Constant Description
When the system creates a new email this SysID will be used rather than the one from current record
When the system creates a new email this SubSysID will be used rather than the one from the current record
When the system creates a new letter this SysID will be used rather than the one from current record
When the system creates a new letter this SubSysID will be used rather than the one from current record