There are two data types

List: Default variables

It is likely that the list of default variables varies from release to release. The out-ofbox system includes the following global and local variables.

Variable

Definition

$G.profiles

List of personal profiles

$G.pm.global.envir
onment

Incident Managements global environment record

$G.category

List of category forms (category file)

$G.assignment

List of Incident Management assignment groups

$G.categories

List of categories

$G.problem.inbox

List of Incident Management views

$G.open.lists

List of all global lists built at login

$G.icm.status

List of Configuration Management statuses

$G.assignment.gro
ups

List of Incident Management assignment groups

$G.prompt.for.save

Global flag (Boolean) that determines whether or not to

prompt you to save when you press OK or Cancel after
you update a record.

Variable

Definition

$G.operators

List of Service Manager operators

$G.availability.map
s

List of availability maps

$G.pm.environmen
t

The current users Incident Management personal profile

record

$G.pm.status

List of Incident Management statuses

$G.groups

List of all PM profile groups in the system

$G.technicians

List of technicians (operator file)

$G.inbox.types

List of view types (Incident, Service Desk interaction)

$G.incident.inboxe
s

List of Service Desk views

$L.filed

This is the current file opened by the display application

$L.new

The current file being updated when evaluating macro

conditions

Variable

Definition

$L.old

The pre-updated state of a file undergoing an update

while evaluating macro conditions

$lo.appl.name

Application name passed to menu.manager

$lo.appl.names

Application parameter names passed

$lo.appl.values

Application parameter values passed

$lo.cm.limit

Partial-key time threshold for Change Management

$lo.company.name

Company name as defined in the Client record (company

file)

$lo.copyright

HP copyright (copyright())

$lo.date.order

Number representing date order (mdy, dmy, ymd)

$lo.db.limit

Partial-key time threshold for Database Manager

$lo.device

Device ID (current.device())

Variable

Definition

$lo.es

Vars not used

$lo.groups

List of query group names in operator record

$lo.home

Name of Home menu for GUI

$lo.i

Temporary variable that functions as a loop counter

(variable is cleaned up in the login application)

$lo.main

Name of main menu for text

$lo.month.abv

List of abbreviated months (Jan, Feb, Mar)

$lo.month.ext

List of months (January, February, March)

$lo.msglog.lvl

Level of messages to be logged

$lo.pm.limit

Partial-key time threshold for Incident Management

$lo.printer

Default printer name

Variable

Definition

$lo.system.startup

Set at login to value of the field called

system.startup.time in Company Information record.

$lo.time.zone

Users time zone

$lo.uallow.syslog

Determines whether syslog table is updated when

processes start and end in the system.

$lo.uallow.timezon
e

Allows user to modify time zone based on capability

$lo.uapprovals

List of change approval groups

$lo.ucal

not used

$lo.ucalz

not used

$lo.ucapex

List of users capability words

$lo.uchgmgr
$lo.uchgrps

List of change groups

$lo.ucm.print

Flag to indicate Change Management print default

$lo.ufname

Users full name

$lo.ulogin.time

User login time stamp

$lo.ulogoff.parm

Obsolete

$lo.upm.print

Flag to indicate Incident Management print default

$lo.user.name

operator()

Device is the name of the table for configuration items.

popup.contact.info is used for hover.

sysmodtime is a system defined field that always holds the value of the last
time a record was modified.
The tod() function always holds the value of the current date and time.
The date time statement '7 00:00:00' represents 7 days, zero hours, zero
minutes and zero seconds.

Knowledge documents
In the Knowledge Management (KM) system, a knowledge document typically consists of
information about a particular topic. The amount of detail and length depends on the complexity
of the topic and the audience for the document. Knowledge documents can include attachments
that can be images, text files, PDF files, or Word files for example. In the out-of-box system, the
types of knowledge documents are error messages, external documents, question/answer
documents, problem/solution documents, and reference documents. All knowledge documents
are assigned to at least one document category and may be placed in multiple categories. A
typical document category might be technical documents or HR procedures.
1. Draft documents - These are documents that are being created, but have not yet been
submitted for approval or approved.
2. Approved documents - These are documents that are available for searching and
viewing. Some documents may only be viewed by an internal users, while others can be
viewed by internal and external users. Approved documents can be edited by users with
the edit in place option selected for their KM security profile. Users can add feedback to
approved documents. Users with appropriate privileges can create a working copy of the
document and then make revisions.
3. Working copy - A document becomes a working copy when an approved document
goes into the workflow to be updated. When the working copy of the document is
approved it replaces the original document. A working copy of an approved document
has an "R" appended to the document ID. A new document submitted for approval is
also considered a working copy while it is in workflow waiting to be approved, but there
is no "R" appended to the document ID.
4. Retired documents - These are documents that become out of date and have been
archived for some reason. Retired documents are not searched when users perform a
knowledgebase search. KM ADMIN users can delete retired documents.
Knowledge documents typically have a life cycle that includes draft, working copy awaiting
approval, approved, and retired.

Request management compromised of model table, vendor table and modelvendor table.

A catalog --a list of parts and services --is a table that contains all the items
available for request by users.
A catalog, a list of parts and services, is a file that contains all of the items
that a requester might want to order.

This includes request

categories,
master categories,
and line items such as a new phone,
move/add/change of a PC,
and a new logon ID.
The Catalog contains all the items that users can request, including request
category packages, such as Employee Office Move or whether they directly
request to add something to their order at a later time.
Catalog line items require detailed definitions, such as specific model
numbers, prices, and delivery lead times.
Other items that can be tracked include descriptions, vendors, and approval
requirements.
Phantom line items
Phantoms are place holders, or pseudo parts, used to organize a collection of
multiple items. They are used to provide flexibility in defining component
relationships within the catalog, and are usually not physical items. A
phantom can be considered an umbrella type of level for several parts
selections of the same type. For example, beneath the New Employee Setup
master category the New Accounts & Access line item provides a selectable
option. This item itself does not display on the quote or order when it is
selected; the catalog displays each of the associated parts as individual line
items, such as internet access, email account, and network ID.
A phantom part is a parent of the specific items within it, and you can select
specific items (or parts) through the phantom part.
Phantoms are assigned part numbers, but they themselves usually are not
ordered or placed on a quote.

SCEMAIL requires MAPI profile to login to email server

SCSMTP executable can download from supportable website. Easiest way to setup.
Dont need MAPI profile.
SCAutomate requires license, support bi-directional email.
Connect-IT prepares scenario.

SCSMTP way must be SMTP Compliant

1. Requires mail client
2. Mail server