Application Setup Help Topics For Printing
Application Setup Help Topics For Printing
Legal Notices
Warranty
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be
construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Copyright Notice
© Copyright 1994-2014 Hewlett-Packard Development Company, L.P.
Trademark Notices
Adobe® is a trademark of Adobe Systems Incorporated.
Java is a registered trademark of Oracle and/or its affiliates.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Oracle® is a registered US trademark of Oracle Corporation, Redwood City, California.
UNIX® is a registered trademark of The Open Group.
For a complete list of open source and third party acknowledgements, visit the HP Software Support Online web site and search for the product manual called HP Service
Manager Open Source and Third Party License Agreements.
Documentation Updates
The title page of this document contains the following identifying information:
l Software Version number, which indicates the software version.
l Document Release Date, which changes each time the document is updated.
l Software Release Date, which indicates the release date of this version of the software.
To check for recent updates or to verify that you are using the most recent edition of a document, go to: http://h20230.www2.hp.com/selfsolve/manuals
This site requires that you register for an HP Passport and sign in. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html
Or click the New users - please register link on the HP Passport login page.
You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.
Support
Visit the HP Software Support Online web site at: http://www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP Software offers.
HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your
business. As a valued support customer, you can benefit by using the support web site to:
l Search for knowledge documents of interest
l Submit and track support cases and enhancement requests
l Download software patches
l Manage support contracts
l Look up HP support contacts
l Review information about available services
l Enter into discussions with other software customers
l Research and register for software training
Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to:
http://h20229.www2.hp.com/passport-registration.html
Contents
Chapter 1: Application Setup 12
Create a workflow 65
Workflow phases 66
Add a phase 67
Workflow transitions 72
Create a manual workflow transition 73
Create an automatic workflow transition 74
Create a default workflow transition 74
Copy an existing workflow 75
Viewing a workflow in Workflow Viewer 76
Integrate Workflow Viewer into kmdocument form 76
Process Designer security model 78
Multiple roles 79
Add a role 79
Add security roles and settings 80
Roles in the operator record 81
Assign a role or roles to an operator 81
Add an area 81
Add a setting within an area 82
Validation script for a new setting 83
Update a setting within an area 83
Localize an additional setting 84
Modify the rights for a role within an area 85
Update rights to display allowed categories and allowed statuses 85
Modify allowed categories and allowed statuses 86
l Application profiles
l User roles
l Capability words
l Adding users
l Lockouts
l Login restrictions
l Change Management
l Configuration Management
l Incident Management
l Problem Management
l Service Desk
To view a static version of the ERDs, click the HP Service Manager Entity Relationship Diagrams link
below. The file opens in the help window.
To view an interactive version of the ERDs that enables you to view column names and data types for
each table, right-click the HP Service Manager Entity Relationship Diagrams link below, select Save
Target As (or Save Link As), and save the file to your computer. Then open the file with Adobe Reader
9 or later. Free Adobe Reader upgrades are available from the Adobe web site.
The HP Service Manager Entity Relationship Diagrams are available from the help.
The HP Service Manager Processes and Best Practices Guide provides best practices, management
overviews, process flows, and workflow diagrams for the following Service Manager modules:
l Incident Management
l Request Management
l Problem Management
l Change Management
l Configuration Management
Service Manager processes and best practices incorporate the applicable elements of ITIL V3, COBIT
4.1 and ISO 20000.
The HP Service Manager Processes and Best Practices Guide documents the practice workflows that
are standard with out-of-box Service Manager applications. It includes high-level process workflow
diagrams, and step-by-step procedural guidelines.
You can view and search this guide using Adobe® Reader, which you can download from the Adobe
Web site.
Processes
The HP Service Manager processes are based on ITIL V3 theory and are referenced in the ITIL V3
core.
The Service Manager best practices cover the following processes in the ITIL Service Transition and
Service Operation documents. For information on these processes, see the HP Service Manager
Processes and Best Practices Guide linked in the related topics.
The Service Manager Service Desk application supports the service desk function of the Information
Technology Infrastructure Library (ITIL) with its User Interaction Management processes for the IT
service and the customer base. It provides a single point of entry to the other Service Manager
applications and enables you to document and track all calls received by your service desk. It
incorporates the essential concepts of ITIL to ensure that the best practices of IT service management
in place. The Service Desk application helps you to aid end customers, ensure data integrity, and
streamline communication channels in the organization.
For complete information on the User Interaction Management (Service Desk) process overview and
workflows, see HP Service Manager Processes and Best Practices Guide in the related topics.
The Service Manager Incident Management application supports the Incident Management process. It
incorporates the essential concepts of Information Technology Infrastructure Library (ITIL) to ensure
that the best practices of IT service management in place. The Incident Management application helps
you to restore normal service operation as quickly as possible and minimize the adverse impact on
business operations.
For complete information on the Incident Management process overview and workflows, see HP
Service Manager Processes and Best Practices Guide in the related topics.
The Service Manager Problem Management application supports the entire Problem Management
process. It incorporates the essential concepts of Information Technology Infrastructure Library (ITIL)
to ensure that the best practices of IT service management in place. The Problem Management
application helps you to maximize system availability, improve service levels, reduce costs, and
improve customer convenience and satisfaction.
Note: ITIL defines a Problem as the unknown cause of one or more Incidents.
For complete information on the Problem Management process overview and workflows, see HP
Service Manager Processes and Best Practices Guide in the related topics.
infrastructure. This includes assets, such as network environments, facilities, telephony, and
resources.
The Service Manager Change Management application supports the Change Management process. It
incorporates the essential concepts of Information Technology Infrastructure Library (ITIL) to ensure
that the best practices of IT service management in place. The Change Management application help
you to ensure that changes are requested, evaluated, and implemented according to your business
processes and needs.
Note: To control changes, HP recommends that you handle all standard changes (that is, changes
of predefined types) by using the Service Catalog request fulfillment process.
For complete information on the Change Management process overview and workflows, see HP
Service Manager Processes and Best Practices Guide in the related topics.
The Service Manager Configuration Management application supports the Configuration Management
process. It incorporates the essential concepts of Information Technology Infrastructure Library (ITIL)
to ensure that the best practices of IT service management in place. The Configuration Management
application supports your business and control objectives, and helps you to track your configuration
items through their lifecycle.
For complete information on the Configuration Management process overview and workflows, see HP
Service Manager Processes and Best Practices Guide in the related topics.
n Select a user role, which includes predefined application profiles and capability words.
n Select application profiles and capability words, which lets you manually select security
settings for each application.
l Create the operator record from the operator.g form, which enables you to:
l Create the operator record from Ongoing maintenance (CAU) User Quick Add Utility, which enables
you to:
Service Manager includes several predefined operator records that you can use as templates to create
your own users. Search your operator records to see a complete list of sample operators.
Operator records
Each HP Service Manager user must have an operator record to log on and use Service Manager
applications. The operator record defines the access rights and security settings that a user has. The
following fields are required for an operator record:
l Login Name
l Resource Type
You can also define the following optional information in an operator record:
General Login Name — Use this tab to add identifying information and application profiles
Required field to an operator record. These application profiles determine which
Full Name features and views the operator can access in Service Manager
Default applications.
Company
Contact ID
Application
Profile
User role
Application
profiles
Security Password Use this tab to manage how an operator accesses Service
Information Manager. These settings determine whether an operator can log
User Session on to Service Manager.
Information
Login
Information
User Lockout
Information
LDAP
Information
Template
Information
Password
History
Startup Initial Application Use this tab to determine which forms the operator sees at
Execute startup and also to customize the capability words the operator
Capabilities has in addition to those granted by a user role.
Query Groups
Months
Notification Standard Use this tab to record contact information about the operator.
Notifications
Pager
Information
Client Printing
Security Security Groups Use this tab to add or remove security groups that determine
Groups whether the operator has access to tables protected by the
Mandanten feature.
Self Self Service Use this tab to authorize self service access to an operator. This
Service Access Only gives the user access to the self service Web client.
Self Service
Menu
Self Service
Starting Page
System Administrator
Note: To create an operator, you need to first create a contact record to match the operator record.
Note: HP recommends that you only use ASCII characters in Login Name. In Service Manager
Web Service integrations, non-ASCII operator login names are not supported.
3. Specify a Contact ID, or select the contact name that you just created.
4. Click Add.
5. On the Security tab, type the name of the Template from which you want to create the new
operator record.
The information from the template will be populated in the new operator record.
6. Add any other necessary information for this new operator record.
7. Click Save.
System Administrator
3. Click Next.
4. Type the name of a user to clone or use the Fill icon to find a user to clone.
5. Click Finish.
System Administrator
5. In the Security Groups array, type the names of the security groups for the new operator on
separate lines.
6. Click Save.
System Administrator
Information in the system default operator record becomes part of all operator records at the time you
create the operator record and whenever you query the operator table. The operator table displays the
field values in the system default record unless there is another entry that overrides it. For example, if
the system default record defines the Default Company field with the value DEFAULT, then all operator
records without a defined value for this field display the value DEFAULT.
3. Type or select the new operator information. The following fields are required for a system default
record:
4. Click Add.
System Administrator
You can create a custom startup menu for an operator by using the Forms Designer. You can designate
the custom startup menu as the initial starting application of a user’s operator record. When the
operator logs in, HP Service Manager displays your custom startup menu to the operator.
2. In the Form field, type the form name for the custom startup menu.
3. In the Language field, type or select the language used to display the form. If this field is blank,
the form uses the same language as Service Manager.
4. Click New.
7. When your new form is complete, click OK to exit the design mode.
10. In the Menu Name field, type the name of the custom startup menu in uppercase.
11. In the Format field, type the name of the startup form you created in step 2.
Menu
option Purpose
Option # The option number on the startup form must match the Button ID in the Forms
Designer.
Group Enter the security group, if any, required to access this application.
Description Type a description of the menu option. This description is only visible from this
form and is separate from the caption for the button you defined in the Forms
Designer.
System Administrator
By default, a user sees the To Do list upon logging in to HP Service Manager. You can change that to a
MySM home page by defining one in the user's operator record. You can auto-fill the MySM home page,
along with other defaults, into an operator record from the user role. You can use mass update to define
the MySM home pages of several operators at the same time. Specifying a MySM home page in a
user's operator record overrides the To Do list and menus for that operator when they log in using the
web client, even if the flag for menus has been set.
To set the MySM home page for a specific operator, follow the steps below:
3. Click Search.
6. To use the default MySM home page, along with other defaults specified for the operator's user
role, click the Fill button on the User Role field. You can then edit those defaults directly in the
operator record.
To select a MySM home page for an operator when there is no MySM home page defined for the
user role or to specify a MySM home page that is different from the default, select one from the
MySM home page drop-down list.
7. Click Save.
System Administrator
The default home page for a HP Service Manager user is the MySM home page or To Do list specified
for the operator or user role. You can define an old style startup menu or any other RAD application so
that it is the initial application that Service Manager displays when an operator logs in. You define an
initial application in the user's operator record.
Note: Specifying a MySM home page in a user's operator record overrides the To Do list and
menus for that operator when they log in using the web client, even if the flag for menus has been
set.
3. Click Search.
6. In the RAD Name field, type the name of the startup menu or initial application to run when the
operator logs on.
7. Type any parameter names and parameter values required by your startup form. For example,
specify the following values for old style menus.
8. Click Save.
System Administrator
To define the distinguished name an operator uses to log in to an LDAP directory service, follow the
steps below:
5. In the LDAP User DN field, type the distinguished name you want the operator to use to bind to
the LDAP directory service.
6. Click Save.
7. Click OK.
System Administrator
4. Click Delete.
6. When you are prompted whether to remove a certain associated record, for example, an
associated contact record, click Yes to delete the associated record or click No to keep the
record.
System Administrator
To enable an operator to see the command line, follow the steps below:
3. Click Search.
7. Click Save.
System Administrator
Database access is a feature that gives you the ability to limit or grant access to database records,
such as contacts, company, and regions. You can add or modify the existing out-of-box database
access settings per user role or operator.
c. The operator name you initially selected is in the Operator Name field. If you want to add
access to a different operator name than the one you selected, clear the field and click Fill to a
select a different operator name.
o Allow DB access: The operator specified is granted access to the table specified.
o Prohibit DB access: The operator specified is denied access to the table specified.
e. When access has been granted to a table, click Fill in the View Format field to select the
table view.
f. Click Add.
b. Double-click the Table Name of the existing database access record you want to modify.
d. Click Save.
7. Click OK.
System Administrator
To set the first day of week for an operator, follow the steps below:
3. Click Search.
6. In the First Day of Week field, select a day from the drop-down list.
7. Click Save.
If you do not configure this field, the first day of the week for the operator is as follows:
l In the date picker, the first day of the week is the day that is configured by the startDayOfWeek
parameter. For more information about the startDayOfWeek parameter, see "Web parameter:
startDayOfWeek" on page 1.
l In the calendar, the first day of the week is the day that is configured in calendar settings. For more
information about the calendar settings, see "Configure calendar settings" on page 1.
If you configure this field, the first day of the week in the date picker and the calendar for the operator
will be the day that is specified in this field.
System Administrator
To set the maximum file size of a single attachment for an operator, follow the steps below:
3. Click Search.
6. In the Max Attachment Size field, type the number of bytes for the maximum file attachment
size.
7. Click Save.
You can define a file attachment maximum size limit for a particular operator from the operator record.
The operator file attachment size limit supersedes the maximum file size set in the system wide
company record but is itself subordinate to size limits defined for an attachment container in the Form
Designer.
System Administrator
To set the total attachment size in any attachment container for an operator, follow the steps below:
3. Click Search.
6. In the Total Attachment Size field, type the number of bytes for the total file attachment size.
7. Click Save.
You can define a total attachment size limit for a particular operator from the operator record. The total
attachment size defined in the operator record supersedes the total attachment size set in the system
wide company record but is itself subordinate to size limits defined for a specific attachment container
in the Form Designer.
System Administrator
To set the time zone for an individual operator, follow the steps below:
3. Click Search.
5. In the Time Zone field, select the new time zone for the operator.
6. Click Save.
System Administrator
3. Click Search.
4. Select the operator that you want to update from the record list.
5. Type or select the new operator details. For example, change the Application Profile on the
General tab, or add new capability words to the Execute Capabilities table on the Startup tab.
6. Click Save.
7. Click OK.
System Administrator
3. Click Search.
4. Select an operator from the record list to view the operator record.
System Administrator
Note: If you exit the Mass Update template form or Complex Update form without clicking
Execute, all of your changes are cleared on the respective form.
To update several records at the same time, use one of the following methods:
3. Select the records in the record list that you want to update.
5. Type the value for the field in the text box or use the Find feature to display a list of potential values
for the field.
Note: The value(s) you enter in the form are propagated to all of the records you selected.
6. Click Next.
7. Continue updating fields and click Execute when you complete your updates.
Simple Update:
7. Click Execute.
Complex Update:
7. Click Execute.
System Administrator
In the following example you mass update all operators that have the Service Desk Agent user role.
The example assumes that the MySM home pages are already available.
Note: Specifying a MySM home page in a user's operator record overrides the To Do list and
menus for that operator when they log in using the web client, even if the flag for menus has been
set.
To mass update operators' MySM home pages, follow the steps below:
2. Search for operators with the desired user role. For example, type service desk agent in the
User Role field and click Search.
HP Service Manager displays a list of operators who are service desk agents.
8. The MySM home page field of each updated operator record's Startup tab is now populated with
the selected MySM home page.
9. To test the home pages you just set, log out and log in again as each operator.
Note: If you exit the Mass Update template form or Complex Update form without clicking
Execute, all of your changes are cleared on the respective form.
Several redundant fields in the operator table were removed in order to leverage existing fields in the
contacts table. See the Service Manager Upgrade Guide for a list of the fields removed from the
operator table.
System Administrator
To mass create contact records from operator records, follow the steps below:
3. Click Search.
System Administrator
To mass create operator records from contact records, follow the steps below:
2. Type or select optional search criteria to find the contacts for which you want to create operator
records.
3. Click Search.
System Administrator
The contact and operator records are synchronized so that if you change the HP Service Manager ID
field in the contacts record, it triggers the same change in the Contact ID field in the operator record.
The reverse is also true. In order to make the synchronization possible, every user in the system must
have both a contact record and an operator record.
To create an operator record from a contact record, follow the steps below:
2. Type or select optional search criteria to find the contact for which you want to create an operator
record.
3. Click Search.
4. If the search returned a list of records, select the contact from the list.
System Administrator
Caution: Any changes that you make to an operator template automatically propagate to operator
records based on that template. These automatic updates can consume substantial system
resources.
To create an operator record from an operator template, follow the steps below:
4. In the Template field, type the login name of the operator record to be used as an operator
template.
5. Click Add.
Note: If an operator record has group1 in its security groups array when its template is NULL and
group1 is in the security groups array of template_1 but not in that of template_2, when you assign
template_1 to the operator record, the operator record has group1 in its security groups array;
however, if you switches its template to template_2, group1 is lost in its security group array. To
work around this issue, first switch its template from template_1 to NULL, save it, and then switch
the template from NULL to template_2.
System Administrator
The contact and operator records are synchronized so that if you change the HP Service Manager ID
field in the contacts record, it triggers the same change in the Contact ID field in the operator record.
The reverse is also true. In order to make the synchronization possible, every user in the system must
have both a contact record and an operator record.
To create a contact record from an operator record, follow the steps below:
2. Enter and select the search criteria to find the operator for which you want to create a contact
record.
3. Click Search.
5. In the selected operator record, replace the Contact ID with the new contact ID.
6. Click More or the More Actions icon, and then Create Contact option.
9. Click Save.
Operator templates
System Administrators can design operator templates for creating operator records for users that share
common information and settings. For example, you can design one operator template for managers
and another template for first-level Service Desk Agents. An operator template is an operator record
containing all the common information that applies to operator records created from the template.
Typically, this includes information such as:
l Application profile
l Default Company
l Date Information
l Time Limits
l LDAP Information
l Security Groups
To distinguish the operator template from a user's operator record, select the Template Operator
option in the template. Users are not attached to templates and, therefore, cannot log in to HP Service
Manager using an operator template.
When you have created the new operator template with all the desired settings, you can then create the
operator records you need, based on that new template. When you create operator records, fill in the
Template field with the name of the template from the operator template, and then all the information in
the template will be applied to the new operator records.
Any changes you make to an operator template automatically apply to all operator records you created
from the template. If you later decide to change a setting in the template, you modify the template, and
then the setting will automatically be applied to all the operator records that use the template.
System Administrator
Caution: Any changes that you make to an operator template automatically propagate to operator
records based on that template. These automatic updates can consume substantial system
resources.
To create an operator record from an operator template, follow the steps below:
4. In the Template field, type the login name of the operator record to be used as an operator
template.
5. Click Add.
Note: If an operator record has group1 in its security groups array when its template is NULL and
group1 is in the security groups array of template_1 but not in that of template_2, when you assign
template_1 to the operator record, the operator record has group1 in its security groups array;
however, if you switches its template to template_2, group1 is lost in its security group array. To
work around this issue, first switch its template from template_1 to NULL, save it, and then switch
the template from NULL to template_2.
System Administrator
System Administrators can design operator templates for creating operator records for users that share
common information and settings. For example, you can design one operator template for managers
and another template for first-level Service Desk Agents. An operator template is an operator record
containing all the common information that applies to operator records created from the template.
Note: You can specify as many details in the new operator record template, as necessary.
2. Enter the search criteria to find the operator record for which you want to create an operator
template.
3. Fill in the necessary information, including application profiles, and proper permissions and
settings.
5. Click Add.
Note: Because operator templates are also operator records, they are valid log-in accounts for HP
Service Manager. To prevent users from using operator templates for log-in access, you can apply
a password and log-in restriction to your operator templates.
System Administrator
To define the operator template applied to LDAP users, follow the steps below:
2. In the Operator Template field, specify the operator record that you want to use as the company
default for LDAP users.
3. Click Save.
The Process Designer provides a platform to build ITIL compliant out-of-box processes. The features
include:
l Provide a platform to model complex processes that require branching and looping
l Lower Total Cost of Ownership of Service Manager by enabling an intuitive and simplified
configuration
l Workflow designer: Design and update a workflow using a graphical user interface.
l Rules editor: Create rules to enforce business logic in workflows and forms.
A workflow is a collection of phases with transitions from one phase to another. Each phase represents
the state of the workflow linked to a form for data capture. Transitions can connect phases in any
manner to create a workflow with many branches and loops back to previous phases. Transitions may
be manual, automatic, or default. A manual transition requires the workflow user to make a manual
decision to move to the next workflow phase. An automatic transition moves the workflow to another
phase based on data in the workflow record. A default transition is a special case that moves the
workflow automatically, when no other automatic transition condition applies.
The rules editor enables administrators, such as business process owners, implementers, and
developers, to add or remove the out-of-box rules and actions of a workflow to match particular
business requirements. You can group rules into Rule Sets to allow their re-use within the process. You
can configure Rule Sets to execute on events, such as saving or updating a workflow record. Rules
can also be set up to run on a workflow transition.
You can also configure rules as actions, which allows operators to run rules on demand rather than wait
for workflow processing. When an operator initiates an action, the system runs the associated Rule
Sets for that phase of the workflow.
With the Condition Editor, you can apply conditions to rules. When a rule condition is met, the rule
executes. You can also edit conditions for a rule.
The Process Designer security model provides a consistent method of assigning permissions to users
across all areas of the system. You can use security model to configure out-of-box rights for a specified
role within an area. It also provides standardized methods to manage user rights.
Process Designer features are implemented for Knowledge Management and Change Management.
You can access the Process Designer features from the system navigator as follows: Tailoring >
Process Designer
A typical Process Designer flow broadly comprises of the following major tasks:
l Create Rule Sets with Rules using out-of-the-box rule types to enforce business logic on traditional
Service Manager forms
l From workflow phases and transitions associate forms, rule sets, approvals, and alerts to
implement your business process
System Administrator
Implementer
A Rule Set contains a list of rules that you may run against a record. Rules implement business logic to
drive a workflow or a process. Rules can help perform calculations, validate fields based on data or
Rule Sets, set required fields, and more. A Rule Set uses role-based security.
You can re-use Rule Sets in many processes when you require the same rules in many places. Rule
Sets simplify the effort of implementing business logic. You can apply Rule Sets based on conditions,
or configure them to run during an action. Rule Sets are most often associated with specific phases of a
workflow.
1. Click Tailoring > Process Designer > Rule Sets > New.
Note: The name must be unique within the Rule Sets records.
3. Select Available as action if you want to offer this Rule Set as an action within a workflow
phase. For example, HP Service Manager interaction with an external system.
4. Type the display name for the Rule Set, for example, Saving a draft.
5. Select the table(s) from the Table name list that you want the rule sets to apply to, for example,
select kmdocument.
Note: If the list is blank, the Rule Set can be applied to all tables.
Note: If you want to edit an HP Proprietary Rule Set, create a copy of the HP Proprietary
Rule Set. To add Rules to a Rule Set, you must first save the Rule Set.
System Administrator
Implementer
You can create an editable copy of an existing Rule Set by using the cloning option. Cloning a read-only
Rule Set marked as HP Proprietary creates an editable copy of the Rule Set.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
2. Click Search.
4. Click More > Clone. A copy of the Rule Sets with both the ID and Name prefixed <CLONE>
displays.
5. Rename both the ID and Name prefixed <CLONE> fields by typing something unique.
6. Click Save.
Adding a rule
A rule defines a singular piece of functionality, such as making a field mandatory. A rule can perform
calculations, validate fields based on data or lists, set required fields, and more. Rules can also specify
conditions that determine when the rule should execute or who can execute.
Rules run in the order they appear in the Rule Set. The order can be changed using the Move Up and
Move Down buttons. If there is an error executing a rule, rule processing will stop. It is important to
order the rules such that validation rules come first in the list, and then any rules that will perform
actions. For example, to validate data and send an HTML email, place rules to validate data first and
then the rule to send an HTML email. If the rules were reversed, the HTML email will be sent with
invalid data or an invalid workflow state if the rules are part of a transition.
l A record is created, updated, or deleted in a certain phase of the workflow because of invoking a
workflow action.
Field Validation Against a List Validate a field against a list (global or defined).
Note:
l You cannot modify the out-of-box rules because they are labeled as HP Proprietary.
l You can edit a user-defined rule. For example, to add or remove a condition.
l Many of the rules have a default description that may contain tokens that get replaced with
values. For example, the Set Mandatory Fields rule has a default description <fields> are
Mandatory. The token <fields> will be replaced by the fields you select in the rule when you
define the rule. You can edit the default description.
l If you do not specify a condition, rule will always trigger to perform the action specified in the
rule.
System Administrator
Implementer
This rule enables you to launch a remote web address by its uniform resource locator (URL). Typically,
this rule aids in integrating with other products.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
3. Select the Rule Set to which you want to add the rule.
Note: If you do not enter an XML string, the condition is set to Always.
9. Type the URL address of the remote resource you want to launch in the URL field.
System Administrator
Implementer
This rule enables users to call a HP Service Manager process. You have to specify the process name
and the conditions that call the process.
Caution: You cannot call a Service Manager process that expects an input, because there is no
provision to pass the input through the rule. Calling a process that requires an input causes the rule
functionality to fail and may generate an unrecoverable error message.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
2. Click Search, and then select the rule set to which you want to add the rule.
System Administrator
Implementer
This rule enables you to trigger certain activities for the Case Exchange integration.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
3. Select the Rule Set to which you want to add the rule.
For more information about how to configure condition for the rule, see "Using the Condition
Editor" on page 57.
8. Select the Case Exchange integration instance that you want to apply the rule from the Instance
Name drop-down list.
System Administrator
Implementer
This rule enables you to run a HP Service Manager wizard. The form helps you to specify the wizard to
run when the rule executes.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
3. Select the Rule Set to which you want to add the rule.
System Administrator
From a rule set, you can clear the value of specified fields in a record. Optionally, the rule can also clear
the value in fields related to the specified fields.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
3. Select the Rule Set to which you want to add the rule.
8. For those fields that will be part of the Clear Fields rule, select the fields in the drop-down list.
9. If you want to clear the value of related fields of the specified fields, select Yes.
10. If you do not want to clear the value of the related fields, select No.
System Administrator
Implementer
This rule allows you to validate any JavaScript code a user enters.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
3. Select the Rule Set to which you want to add the rule.
Note:
n If you do not specify a condition, it will default to Always.
n You may reference the current record as record in the JavaScript. For example, if the field
in a form is a category, it may be referred to as follows: record.category=="xyz"
n You may reference the original copy of the record (before any changes were made by the
user) as oldRecord in the JavaScript (that is 'oldRecord.category').
n You may set the returnCode variable in the JavaScript to specify whether this rule was
successful or should be treated as a failed validation. A return code of 0 (zero) is
considered successful (it is the default), any other code is unsuccessful. The return code
must be a numeric value.
n You may set the message variable in the JavaScript to specify a message that displays to
the user if the rule is unsuccessful (returns a non-zero return code).
n You may set the cursorPosition variable in the JavaScript to specify a field on the current
form where the cursor should be placed if the rule is unsuccessful.
System Administrator
Implementer
This rule enables you to make one or more fields mandatory and to specify a default value for each
field, which will be set if the mandatory fields are empty.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
3. Select the Rule Set to which you want to add the rule.
8. Select the error message type: Pop-up or Screen to display during validation.
9. Click the Show All Error Messages Together check box if you want to display all error
messages together during validation.
11. You can choose a default value, which will be set if the mandatory fields are empty.
System Administrator
Implementer
This rule enables you to set global and thread variables as mandatory. If mandatory variables are
empty, then a default value is set if specified in the Rule.
Global or thread variables begin with the $ symbol. However, the rule does not accept local variables
beginning with $L. Global variables are set when the operator logs on and the server automatically
cleans them up when the session ends.
Thread variables do not have a consistent naming scheme. They are only valid for the current RAD
thread. If the RAD thread terminates, the server automatically cleans up all thread variables.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
3. Select the Rule Set to which you want to add the rule.
8. Select the error message type: Pop-up or Screen to display during validation.
9. Click the Show All Error Messages Together check box if you want to display all error
messages together during validation.
Note: If a mandatory variable is empty, then the rule sets it to a default value.
System Administrator
Implementer
This rule enables you to send notifications using a HP Service Manager notification record. The rule is
typically mapped to a workflow or workflow phase. For example, you can use the rule to send a
notification when a phase is entered. The rule type links to an existing notification record.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
3. Select the Rule Set to which you want to add the rule.
9. Select the existing notification record you want to send when this rule runs.
System Administrator
Implementer
This rule enables you to set a field with the value determined by a JavaScript. From a Rule Set, you can
select a common field from multiple tables and set its value based on a JavaScript expression.
Note: Make sure that the field is set to the contents of the value variable. If it is not set to the
value variable, you cannot process JavaScript.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
3. Select the Rule Set to which you want to add the rule.
9. Type the JavaScript that sets the variable value to the desired value for the field in the text box.
System Administrator
Implementer
This rule enables you to select a field to validate against a list of values. This list may be global or
manually defined.
To add a Field Validation against a List rule, follow the steps below:
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
3. Select the Rule Set to which you want to add the rule.
8. Select the error message type: Pop-up or Screen to display during validation.
10. If you select Global List, select the global list from the drop-down list.
11. If you select Manual List, type the manual list names in the Value table.
Note: If the field value does not match a value in the specified list, the system displays a message
and sets the cursor to that field when the rule is not followed.
System Administrator
Implementer
This rule enables you to validate a field against a field in another table and fill data into other fields. You
can also filter the data you are validating against, and fill data into other fields.
Note: If the field value does not match a value in the specified table, the system displays a
message and sets the cursor to that field when the rule is not followed.
To add a Field Validation against a Table rule, follow the steps below:
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
3. Select the Rule Set to which you want to add the rule.
10. Select the name of the field you want to validate against.
11. You can filter the data you are validating against using a standard RAD query.
Example:
The following field entries will validate only for cm3r with the current field name (Demo String2 in
this example) of the workflow:
12. Click Click Here to Add Fill Information to enter Fill From and Fill To fields.
Note: The Fill From field represents the fields of the validation table against which it
validates. The Fill To field represents the fields in the current table being validated.
Group rules
Applies to User Role(s):
System Administrator
Implementer
You can group multiple rules into a Rule Group with an overall condition. The system runs all the rules
in the Rule Group if the condition matches.
2. Click Rule Sets > Search to open the Rule Set form.
6. .
Note: You can add one or more rule groups within another Rule Group.
A condition is made up of one or more expressions connected by logical operators AND or OR. An
expression is a query built from the fields, operators, and values that returns a Boolean value (True or
False). An expression has a Left-Hand-Side (LHS) and Right-Hand-Side (RHS) separated by an
operator. There can be a combination of variables, types, and values on either side of the expression.
After you build a condition, HP Service Manager displays a user readable query describing the
condition.
You can also build complex conditions with the Condition Editor. A complex condition typically has
many expressions nested together with groups and sub groups. A group is a collection of multiple
expressions within braces. The following is an example of a complex expression:
Note:
l Make sure to build a proper condition. For example, a string field in a condition should have only
alphanumeric characters. Improperly built conditions will show as Never and will not evaluate
to either True or False.
l After you have built a condition, you can add more expressions by linking them with OR and
AND operators. If you change an OR to an AND operator, then the condition will group all
expressions using an OR operator to ensure the condition makes logical sense.
l Add a condition
l Add a group
Click the ! icon that appears in the group when hovering the mouse to the top left corner of a
Condition Editor. Clicking ! icon again will undo negate.
Note: The current version does not support an expression combined with negate and !=. For
example, the "Not(CurrentRecord.priority != 'high')" expression is not supported in the current
version of Service Manager. Condition Editor allows building such an expression, but it will
always evaluate to false.
l Edit a condition
l Cancel a condition
l Clear a condition
Build a condition
Applies to User Roles:
System Administrator
Implementer
Make sure that the RHS field matches with field data type in the LHS. For example, if the field data
type in LHS is a Boolean, you must select a matching Boolean field in RHS. However, if you decide to
choose a value rather than a field in RHS, the system provides you an option to type or select value
that is of same data type of the field in LHS.
3. Select an expression data type on the LHS. The following table describes the available expression
data types for the LHS.
Field Description
CurrentRec A field in the name of the current record authorization for comparison, including
ord New, Update, View, Admin, Delete/Close, and Expert.
Authorizatio
n
Note: The CurrentRecord Authorization data type is only available when you
build a condition for a workflow.
Object A field in the Object definition of the current record for comparison.
SavedReco A field in the original copy of the current record (before the user made any
rd changes) for comparison.
RAD Evaluates a RAD expression typed in the text area. For example:
Expression
evaluate(cls.control in $L.phase) and evaluate
($L.tableAccess.delete)
and open in $L.file=true and nullsub($G.ess, false)=false and
approval.status
in $L.file="approved" and (category in $L.file~="KM Document" or
category
in $L.file="KM Document"
Note:
n You cannot combine this expression with any other expression type.
Category A field in the associated category definition of the current record for comparison.
Phase A field in the associated phase definition of the current record for comparison.
Field Description
Security An operator's security rights. You can choose rights from the drop-down list of
defined values: Change, Change Management Configuration, Change
Tasks, Knowledge Management, Knowledge administration, Security, or
Tailoring.
Variable Evaluates the value of a global, local, or thread variable condition. For example:
$G.test
$L.testNumber
5. Select an expression operator for the expression type. The following table describes the
expression operator.
Field Description
= Equals
!= Not equals
< Lesser
Note: For Boolean expression conditions evaluating to !=true, you can use the following
RAD expression:
6. Select an expression value type on the RHS. The following table describes the available
expression data types for RHS:
Field Description
SavedRecord A field in the original copy of the current record (before the user made any
changes) for comparison.
Object A field in the Object definition of the current record for comparison.
Security Evaluates an operator’s security rights. You can choose rights from the drop-
down list of defined values: Change, Change Management Configuration,
Change Tasks, Knowledge Management, Knowledge Administration,
Security, or Tailoring.
For example, to trigger a rule set only if the logged in user has the Any Draft
kmprofile enabled, set the following condition:
Value Allows you to type or select values as per the data type, which is based on
selected caption on the LHS.
Phase A field in the associated phase definition of the current record for comparison.
Category A field in the associated category definition of the current record for
comparison.
7. Click Apply.
8. Click OK if you are done with the process of adding a condition. Once you add a condition, Service
Manager displays a user readable description.
9. If you want to add another condition, select Expression from the drop-down list and repeat steps 3
through 8.
Note:
l You can edit a pre-existing condition. Click the pencil icon to view and edit existing values.
l To clear a condition, click Clear. You can now build a new condition based on your
requirements.
System Administrator
Note: You can launch the Condition Editor in the web client only.
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
4. Select a Rule.
Note: If you do not specify a condition, it defaults to Always and the rule will always execute.
4. You can launch Condition Editor from either of the following tabs:
n Actions– Click Add > Action Condition to launch the Condition Editor.
n Alerts – Click Reset Condition or Recalculate Condition to launch the Condition Editor.
n Transitions– From a workflow page, click a transition > Condition in Details tab to launch
the Condition Editor.
Related concepts
System Administrator
Implementer
Condition Editor enables you to build a condition without any programming language knowledge.
Note: You can launch the Condition Editor in the web client only.
To launch Condition Editor from a rule type, follow the steps below:
1. Click Tailoring > Process Designer > Rule Sets in the System Navigator.
4. Select a rule.
System Administrator
Implementer
Condition Editor enables you to build a condition without any programming language knowledge.
Note: You can launch the Condition Editor in the web client only.
4. You can launch Condition Editor from one of the following tabs:
n Transitions: In the Details tab of a workflow page, click a transition arrow --> Condition.
System Administrator
Implementer
System Administrator
Implementer
To negate a group, click the ! icon that appears in the group when you hover the mouse at the top left
corner of a Condition Editor. Clicking this icon again will undo the negation. Negating a group refers to
negating group of expressions bound to that group.
To negate a group of expressions, click the ! icon in the Condition Builder. The icon becomes red after
the negation. Click it again to undo the negation.
HP Service Manager does not support an expression combined with negate and !=. For example, the
Not(CurrentRecord.priority != 'high') expression . The Condition Editor allows building such an
expression, but it will always evaluate it to false.
Creating a workflow
A workflow is a collection of phases with transitions from one phase to another. Each phase represents
the state of the workflow linked to a form for data capture. Transitions can connect phases in any
manner such as creating parallel branches or loop backs to previous branches.
A workflow enables an implementer to graphically layout the entire lifecycle of a process or record
without any programming knowledge. The end user of the workflow views the same graphical workflow
to see the current phase and past transitions.
Before you create a new workflow, you have to add Rule Sets, Rules to the phases and transitions of
your intended workflow.
Create a workflow
Applies to User Roles:
System Administrator
Implementer
After you have a basic workflow, you can then modify it by adding additional phases, transitions, rules,
and actions to match the business process.
You can click Zoom inor Zoom out in the toolbar either to zoom in or zoom out in the workflow page.
2. Click New.
4. Type a description for the workflow. For example, Knowledge Document Workflow.
5. Select an HP Service Manager table from the drop-down list to associate the table with the new
workflow, for example kmdocument.
Note: You can use the kmdocument table to manage the Knowledge Management document
process. You can use the WorkflowDemo table to explore Process Designer capabilities.
6. Click OK. The new workflow Knowledge appears in the Workflows list.
Note:
l For a workflow that is set as HP Proprietary, you should see a HP logo in the workflow list. For
non-HP Proprietary workflows, the logo does not appear.
l If you want to edit an HP Proprietary workflow or use it as a model, create a copy of the HP
Proprietary workflow.
After you created a basic workflow, modify the Object record of the table for the new workflow.
3. Click Enter.
4. Under File name, provide the table name of the associated workflow. For example,
KMDOCUMENT.
7. Click Save.
8. For the changes to take effect in the Object record, log off and log on to Service Manager.
Workflow phases
Workflow phases show the state of a record in the workflow and provide processing that must occur for
the record to move to the next phase. Phases use transitions to move from one phase to another
phase. Some of this processing can be manual, or it can be triggered by the rules or actions specified
for the phase the record is in within the workflow.
Within a workflow, you can specify a form to display when that phase is active. Use different forms on
different phases to allow different information to be displayed and captured at various stages of
workflow.
Rule Sets link the phase or transition to enforce business logic, such as checking if the user has filled
in the required data or has proper security to perform a transition.
Add a phase
Applies to User Roles:
System Administrator
Implementer
You can add a phase to an existing workflow. You use the graphical interface of the workflow editor to
add a phase.
Note: After you add a phase and click Save, you cannot modify its name. You can modify only its
display name.
1. Click Tailoring > Process Designer > Workflows from the System Navigator to display the
workflows list.
2. Select the applicable workflow for which you want to add a phase.
n Click a phase and hover your mouse until you see a hand symbol and then drag the mouse to
add a new transition and a phase.
n Details
Field Description
Table name The selected table name during workflow creation. You
cannot modify it.
Form Edit condition If the condition evaluates to true for a user, who will be able
to edit the form. If it does not, the form will be read-only.
Records in this phase are Select the check box if you want the records in this phase to
active be active.
Make this the first phase Click Make this the first phase if you want it to be the first
phase.
Make this the default phase Click Make this the default phase if you want it to be the
default phase.
Click Save.
n Forms
Description
Display form The display form is the primary method to capture and
display data. If you do not specify a form, the system will
look for a form that has the same name as the current table
name.
Additional Forms You can add, edit, and delete additional forms for a workflow
phase.
i. Click Add.
n Rule Sets
Description
Add To add rule sets at various stages, follow the steps below:
iii. Click the appropriate Rule Sets check box you want to
add.
Note:
o On enter – Runs when the record moves from
Description
n Actions
Description
vii. Click the Requires lock check box if you want to lock
the record before the action can be performed.
n Approvals
Description
n Alerts
Description
Note:
l To reposition the phase, select the phase and hover your move to see a crosshairs symbol and
then move it to a desired place within the workflow page.
l To delete a phase, select the phase and either click the trashcan symbol next to the phase or
Delete from the toolbar. You cannot delete either a default or a first phase.
l To move multiple phases at the same time, press Ctrl and select multiple phases, and then
move the phases or section of the workflow to new location.
l In the Rule Sets tab, select a rule set and either double-click the rule set or click the View icon
to open the Rule Set form.
l In the Approvals tab, select an approval name and either double-click the approval name or
click the View icon to open the Approval Definition form.
l In the Alerts tab, select an alert name and either double-click the alert name or click the View
icon to open the Alert Definition form.
Workflow transitions
The Process Designer workflow transitions occur when a record moves from one phase to another
phase. Transitions can happen manually, automatically, or by default. An example of an automatic
transition is when the condition set in the phase is met. An example of a manual transition is when an
operator clicks a button. A default transition is a special case that moves the workflow automatically
only when no other transition conditions are satisfied.
Note: Transitions govern the flow of the workflow but an operator with Administrator rights can use
the Change Phase menu option to bypass the workflow and jump to any phase.
After you add a transition, you can reposition it to avoid transitions overlapping with phases or other
transitions. To reposition the transition, select the transition and move the green rectangular dot to
achieve a desired layout.
You can also move a transition from one phase to another. To move the transition, select the transition,
hover your mouse near the blue rectangular dot to see a hand symbol and now move it to another
phase.
System Administrator
Implementer
In setting up a workflow, an administrator can require operator action to move a record from one phase
to another. This type of transition, in which an operator must press a button or otherwise trigger an
action, is a manual transition.
4. Hover your mouse until you see a hand symbol and then drag the mouse to add another phase.
Field Description
Transaction Evaluates to one of the transaction type: Manual, Automatic, or Default. Select
Type Manual transaction type.
Rule Sets Evaluates to the rule sets you created for the transition.
a. Click Add and then select the ID of the rule set you want to add.
b. Click OK.
6. Click Save.
Note: Click the Localize Command Label icon in the Command Name text box to open the HP
Service Manager Message form of a transition. In this page, you can add a message record for a
new transition or view the message record of an existing transition.
System Administrator
Implementer
An automatic transition moves the workflow to another phase based on data in the workflow record.
Note: You can add a condition and rule sets to the automatic transition.
4. Hover your mouse until you see a hand symbol and then drag the mouse to add another phase.
Field Description
Rule Sets Evaluates to the rule sets you created for the transition.
a. Click Add and then select the ID of the rule set you want to
add.
b. Click OK.
6. Click Save.
System Administrator
Implementer
A default transition is a special case that moves the workflow automatically only when no other
transition conditions are satisfied.
4. Hover your mouse until you see a hand symbol and then drag the mouse to add another phase.
Field Description
Rule Sets Evaluates to the rule sets you created for the transition.
a. Click Add and then select the ID of the rule set you want to
add.
b. Click OK.
6. Click Save.
System Administrator
Implementer
You can clone an existing workflow to use it in another business process or if you need to make
changes to a HP Proprietary workflow. You also have an option to copy the rule sets of the existing
workflow.
2. In the Clone a Workflow form, select the workflow you want to copy.
4. Click Copy rule sets check box if you want to copy rule sets.
6. Click Next.
Note: To view a workflow in the Workflow Viewer, you should integrate Workflow widget into any
form associated with a table that is enabled for Process Designer. This is currently available for
Knowledge Mangement (kmdocument), and WorkflowDemo.
The procedure to integrate the viewer into each module is very similar.
System Administrator
Implementer
A new icon Workflow Viewer is available in Forms Designer. The following example will help you to
integrate the Workflow Viewer widget into the kmdocument.document form. After the integration, you
can see a graphical view of the workflow in the Contribute Knowledge > External > Workflow tab.
Using similar steps, you can integrate the Workflow Viewer with other forms.
To integrate the Workflow Viewer widget into the kmdocument form, follow the steps below:
2. From System Navigator, click Tailoring > Forms Designer to open Forms Designer.
3. In the Form field, type kmdocument.external and click Search. The Contribute Knowledge
form opens with the External Document Upload tab selected.
Note: The condition hides the tab in the Windows client, but is visible in the web client.
7. In the Workflow Viewer component, set the following variables in the properties.
$L.wfgWFName
$L.wfgWFTable
$L.wfgWFRecId
$L.wfgWFPhase
10. Set the Workflow Viewer variables in the Main > Initialization tab of the kmdocFlow.open display
screen and the kmdocFlow.view display screen (see note after step 10):
$L.wfgWFName=workflowName in $L.wfPhase
$L.wfgWFTable=tableName in $L.wfPhase
$L.wfgWFPhase=phaseName in $L.wfPhase
$L.wfgWFRecId=id in $L.file
Note: To go to display screen, type ds in the HP Service Manager command prompt and
search for the kmdocument.document form.
11. Follow steps 1 through 7 to add Workflow View in the other Knowledge Management forms,
including kmdocument.probsol, kmdocument.howto, kmdocument.reference and
kmdocument.errormsg.
Process Designer security model is implemented for the Knowledge Management and Change
Management modules. For all other areas and modules, the traditional security features for Service
Manager still apply.
l Area: An area defines a specific functional area or module within Service Manager, such as
Knowledge Management or Knowledge Management administration. Each area definition includes
default rights that are copied to the role whenever a new role is created. In addition to the out-of-box
areas, system administrators are able to define additional areas.
l Rights: The system includes a set of rights such as view, new, update, and delete that control an
operator's data access. When an administrator creates a role, the default rights from each area are
used to set the rights for that role. Rights can be modified for a specific area and role by an
administrator that has update rights for the area and role. Each combination of role and area creates
a collection of rights.
l Settings: Settings are configurable security extensions such as an initial view, a format to display a
list, or an approval checkbox. Settings are added for an area. The types of settings include number,
string, boolean, date/time, global list, manual list, record, and condition.
l Roles: A role has a set of rights and settings assigned to it. Each operator is assigned a role or roles
which, along with area, determine the access rights for the operator. Whenever the roles on an
operator record are updated, the operator must log out and then log in for the changes to take effect.
Note: The out-of-box system includes a default role for the Security area that cannot be
deleted.
l Data Policy records: The data policy records include an Area field used to specify the area
associated with the table. An area needs to be associated with a Data Policy record in order to
access the information from the table.
l Allowed Statuses and Allowed Categories: These fields display the list of statuses and
categories available to the operator when accessing data. A System Administrator specifies the
allowed statuses and allowed categories for a role within an area. When the rights do not include
specific allowed statuses and allowed categories, all statuses and categories are available for the
role within the area.
Multiple roles
When an operator has multiple roles, the operator's data access rights are combined to give the
operator the greatest data access.
When the rights do not include specific allowed statuses and allowed categories, all statuses and
categories are available for the role within the area. Refer to the following examples:
l If an operator has view rights for one role in an area and update rights for another role in that area,
then the operator has view and update rights for the area.
l If an operator has allowed statuses and allowed categories specified in one role and not in another
role, then the operator is able to access all categories and statuses for the area.
l If an operator has multiple roles that include different allowed statuses and allowed categories, the
allowed statuses and allowed categories are merged so that the operator has all allowed categories
and allowed statuses. No allowed statuses and allowed categories are duplicated.
l If an operator has multiple settings because the operator has been assigned multiple roles, the
operator only has the actual settings for the first settings in the operator record .
Add a role
Applies to User Roles:
System Administrator
When you create a role, the rights from each area defined in the system are used to set the rights for
that role record.
2. Click New.
System Administrator
To create a security role and assign rights and settings, follow the steps below:
5. Click Save.
7. Under Rights, select the rights to be assigned to the security role. For example, set Expert rights
for the security role. The Expert security right enables the operator to view alert log, opened tasks,
affected services, and clocks of change request. It also enables you to set reminders, send
notifications, create hot news, and associate change request to changes, incidents, interactions,
quotes, and know errors.
The out-of-box security folders available in Service Manager are DEFAULT and advantage. You can
also create security folders to meet your business needs. By default, all security folders are assigned
to a new security role created. Once a role is created and rights are configured, you can modify the
security rights for a role within an area.
When an operator has multiple roles, the operator has the rights that provide the greatest data access.
However, if each role has additional settings, the rights from the first role listed in the Security Rights
field is used to determine an operator's access rights.
System Administrator
You assign a role or multiple roles to an operator to provide the operator access to HP Service Manager
data. You can also update the operator's role in the operator record.
2. Enter the applicable search criteria to find an operator record and then click Search.
3. In Security Roles, select the role or roles you want to assign to the operator.
4. Click Save.
Add an area
Applies to User Roles:
System Administrator
When you create an area and define the rights and settings for the area, all roles will inherit the rights
and settings for the area.
3. Click New.
System Administrator
You can add a new setting, such as record or format, in the area. A role inherits the new setting from the
area when the new setting for the area is not already defined in the role. For example, this is useful
when you want to have role within an area to have additional access to system data or another form.
When you add a new setting, it is only inherited when you add a new role.
4. Click More or the More Actions icon and then select Administration > Add New Setting.
n Type: Select the type of data used by the setting to match the type of setting you are creating.
For the type selections, the format of the field on the form depends on the type you select. For
example, if you choose boolean, then the setting displays a check box and if you select record,
the setting displays as a text field. When you select some of the types, the system prompts
you for additional information. For example:
o If you select Record, you are also prompted to specify the table and field name for the
record.
o If you select Manual List, you are prompted to provide a display type and a name - value
pair to display in the list. The Value is the field name in the table and Display Value provides
the list of items in the drop-down list for the field.
o If you select Global List, you are prompted to provide a Global List and Display Type for
the Global List.
6. Specify whether or not the setting is mandatory. When checked, a value is required for the setting
you are adding.
7. Click Next.
9. Click Finish.
When you add an additional setting you have the ability to create simple or complex validations for the
setting using JavaScript. The JavaScript automatically sets up an XML variable named result, which
has a child node named message. If the value of the result node is 0 (zero), the validation has
succeeded. Any non-zero result is interpreted as a failure. When a validation fails, the contents of the
message node display. The value of the setting being validated is set to a variable named value.
Example:
This example validates that the setting is a number between 1 and 10.
System Administrator
Once you create a setting for an area, you can update the definition of the setting or delete it. You can
also edit any labels that have been localized.
When you add a new setting to an area, it is only inherited when you add a new role.
4. Click Moreor the More Actions icon and then select Administration > Edit/Delete Setting.
n Type: Select the type of data used by the setting to match the type of setting you are creating.
For the type selections, the format of the field on the form depends on the type you select. For
example, if you choose boolean, then the setting displays a check box and if you select record,
the setting displays as a text field. When you select some of the types, the system prompts
you for additional information. For example:
o If you select Record, you are also prompted to specify the table and field name for the
record.
o If you select Manual List, you are prompted to provide a name-value pair to display in the
list. You must also enter Display Type (Radio Button or Drop Down List).
o If you select Global List, you are prompted to provide a Global List and Display Type for
the Global List.
9. For each language available, you can localize the label text. After you localize the text, click Save
and then OK to return to the wizard.
11. As an option, you can add or edit a validation script for the setting in Adding Settings Validation.
System Administrator
Once you add a new setting, such as record or format, you can localize the setting for all of the
languages that are active in the system.
4. Click More or the More Actions icon and then select Administration > Edit/Delete Setting.
5. In the Edit Setting Info wizard, click Edit localized label. A list of the messages displays for the
user's current language.
6. Click the item you want to localize and then type the applicable text to localize the label you
created for the setting.
7. Click Save.
8. Continue selecting items until you have localized all the labels for the languages active in the
system.
9. To localize the data in the settings for global lists or manual lists, use the record tag localization
utility.
System Administrator
Once a role is created and rights are configured, an administrator updates the rights for a role within an
area.
To modify the rights for a role within an area, follow the steps below:
2. Add optional search criteria and then click Search to find the role you want to modify.
3. Select the role and then select the area you want to modify.
4. Make the changes you want for default rights, folders, and settings.
6. For any other area, repeat steps 3 through 5 to update the rights for the selected role.
System Administrator
A System Administrator can add additional rights to a role within an area by adding the Allowed
Categories and Allowed Statuses fields for an area. Once these fields are available, an administrator
can then specify the particular categories and statuses for which the role has rights. If an area has
multiple tables that support category and status, the drop-down list in Allowed Categories and
Allowed Statuses will have a combination of all categories and statuses from all tables.
The example below uses the data policy record for the cm3r table for Change Management to
demonstrate how to display the Allowed Categories and Allowed Statuses fields.
Note: When you add a new setting, it is only inherited when you add a new role.
2. Use search to find the data policy record for the cm3r table.
3. Select an area from the drop-down list in the Area field. This list displays all the areas available for
the selected data policy record.
4. Click Save. The Allowed Categories and Allowed Statuses fields now appear in the Default
Rights section for the roles within the area you specified in step 3.
System Administrator
For both roles and areas, an administrator can specify in the Allowed Categories and Allowed Statuses
fields the categories and statuses for which a role has rights within an area. Before you can do this, you
must first update the applicable data policy record. These rights give a role in combination with the
other rights access to the specific categories and statuses selected. When no selections are made for
Allowed Categories or Allowed Statuses, the role has access to all categories or statuses within the
area.
You must first ensure that the data policy record for the role within an area has been updated to include
the Allowed Categories and Allowed Statuses fields.
Note: When you add a new setting, it is only inherited when you add a new role.
To modify Allowed Categories and Allowed Statuses, follow the steps below:
5. Select the allowed categories and the allowed Statuses from the drop-down lists.
6. Click Save.
n Creating formatctrl
n Creating menus
n Defining named users and restricting login to these named users only
n Enabling Secure socket layer (SSL) connections between the server and clients
In some cases, these five levels of access restrictions describe the same settings. In such cases,
Service Manager uses the following precedence to determine what access restrictions apply:
2. Tailoring settings override security settings in individual operator records and the System Wide
Company Record
3. Settings in an individual operator records and Mandanten override security settings in the System
Wide Company Record
4. Settings in the System Wide Company Record apply to all operators that have no other security
settings
HP proprietary records
Some HP proprietary records in HP Service Manager are identified by the words HP Proprietary near
the right corner of the screen and are read-only. Having these records as read-only will help future
Service Manager upgrades.
Ongoing maintenance
The Ongoing Maintenance menu enables a System Administrator to access an operator record to view
user and contact information, application profile privileges, and the Mandanten utility. If you use the
ongoing maintenance menu and have administrative rights, you can also access and control several
users or a group from a single application.
As an Application Administrator, you can add or edit users and manage user profiles from within HP
Service Manager applications. You can restrict certain user rights and control the forms that users see
when they access different parts of an application.
Environment record
Each application has an Environment record, which defines options that affect the functionality of an
application for all users. Some of the typical options stored in the Environment record include:
l Relationship model
l Access rights
l Default category
For example, if a user complains that a printer has stopped working and the Service Desk Agent
determines that an older printer is not compatible with a new laptop, the agent can open a Request
Management quote to order a new printer for the user. Once the order is placed, the Service Desk
Agent can close the interaction record and add the quote order number for the new printer to the
resolution note of the interaction. The quote order is also associated to the interaction record, so
that even though the interaction is at a closed status the agent can refer back to the closed
interaction to check the status of the related quote order.
The following can be set in the Service Desk Environment Profile record and are models for managing
Service Desk record relationships:
l Full Service Desk Model: In this model, the state of a Service Desk interaction record changes
when each related record closes. The closed state of an interaction record depends on the
notification value chosen for the "Notify By" field in the interaction record. For example, if the
notification value is "Telephone," the interaction record has a required action before it is closed. This
action describes why the customer must be contacted. It also prevents the interaction record from
closing until all required actions are complete. In this case, the interaction record goes into the
Open-Callback state before it is closed. For more information, see Full Service Desk model.
l All Records close Independently: In this model, all Service Desk interaction records close
independently. The state of related records does not affect closing an interaction record, and closing
the interaction record does not affect related records.
l Close Interactions when Related Record closes: In this model, when the last related record
closes, the Service Desk interaction record closes.
l Cannot close Related Record until Interactions are closed: In this model, records related to a
Service Desk interaction cannot close until the interaction record is closed.
l Cannot close Interactions until Related Records are closed: In this model, a Service Desk
interaction record cannot close until all related Incident Management tickets, Change Management
requests, and Request Management quotes are closed.
Option Description
Email Service Desk sends an email to the contact listed in the interaction record. The email
informs the contact that the related record is closed. Service Desk closes the
interaction record.
Page Service Desk sends a page to the contact listed in the interaction record. Service Desk
closes the interaction record.
Telephone The interaction record has a required action. This action describes why the customer
must be contacted. It also prevents the interaction record from closing until all required
actions are complete. The interaction record goes into the Open-Callback state.
Status progression
HP Service Manager applications have a logical status progression as a service desk interaction,
incident, change task, or problem task moves through its individual life cycle. The following table
describes the out-of-box status values that Service Manager assigns to these applications.
Closed
Work in progress
Pending customer
Pending vendor
Pending other
Referred
Resolved
Closed
Closed
Open - Idle
Open - Linked
Open - Callback
Closed
Application profiles
Application profiles are security settings that determine which features a user can access from a
particular HP Service Manager application. Each of the seven Service Manager applications has a set
of application profiles that determine which features a user can see. An application profile defines the
access settings that a particular business function or role has to the application. Typically, System
Administrators assign application profiles as part of user role descriptions, but the administrator can
also assign an individual application profile that overrides the default settings of a user role.
Users must have an application profile in their operator record to access any application. Each out-of-
box application has a profile record named Default to use when a profile does not exist. Each
application also has a setting to enable access to the application using only the Default profile.
For example, records in the smenv table store Service Desk rights and privileges information, such as
whether a user can close a service desk interaction record. Profiles also store information that may
affect the way an application looks and behaves, such as defining a personal search form for a user.
1. Retrieves the profile name from the operator record and accesses the profile record for the specific
application.
2. If Service Manager cannot find a user profile, it uses the Default profile.
3. If Service Manager cannot find a user profile, and the setting to use the Default profile is disabled,
the user is denied access to the application.
Service Desk
service
self servic desk
Profile DEFAUL approve helpdes initiato servic e desk manage sysadmi
name T r k tech r e agent r n
Security
Rights
Allowed
statuses
Approval
groups
Can notify FALSE FALSE FALSE FALSE FALSE FALSE FALSE TRUE
service
self servic desk
Profile DEFAUL approve helpdes initiato servic e desk manage sysadmi
name T r k tech r e agent r n
Forms
Pr
ofil
e service service sysa
na DEFAUL helpdesk self desk desk dmi
me T approver tech initiator service agent manager n
Initi Inter
al actio
vie ns I
w Regi
ster
ed
Pr
ofil
e service service sysa
na DEFAUL helpdesk self desk desk dmi
me T approver tech initiator service agent manager n
List
for
ma
t
ES ess.SD.o
S pen
initi
al
for
ma
t
ES ess.SD.u
S pdate.edit
edit
for
ma
t
Pr
ofil
e service service sysa
na DEFAUL helpdesk self desk desk dmi
me T approver tech initiator service agent manager n
ES ess.SD.s
S earch
sea
rch
for
ma
t
ES ess.SD.q
S be
list
for
ma
t
Def
ault
Te
mpl
ate
Ap
pen
d
que
ry
Pr
ofil
e service service sysa
na DEFAUL helpdesk self desk desk dmi
me T approver tech initiator service agent manager n
ch
an
ge chan
cha an ge chan pro
nge al cha coor ge cha eme ble
N KM KM SD ana yst nge dinat coor nge rgen m
a DEF coor rev agent/ lyst ta app or dinat ma cy ini ma sys
m AU dinat iew manag cha sk rov chan or na grou tiat na ad
e LT or er er nge s er ge tasks ger p or ger min
Pr a a a a (All) c t a c t a a a a a
of (All) (All) (Al (Ch (T (All) (Cha (Tas (All) (All) (Al (All) (All)
ile l) ang as nges) ks) l)
Ar es) ks)
ea
Security Rights
On this tab, in the Allowed statuses field is blank for all profiles, but can be updated by a System
Administrator.
ch
an
ge ch
an an chan
al ge ge chan cha pro
ys an cha coor ge ng eme ble
KM KM SD t aly nge dinat coor e rgen m
DE coor rev agent/ ch st ap or dinat ma cy ini ma sys
Na FA dinat iew mana an tas pro chan or na grou tia na ad
me ULT or er ger ge ks ver ge tasks ger p tor ger min
ch
an
ge ch
an an chan
al ge ge chan cha pro
ys an cha coor ge ng eme ble
KM KM SD t aly nge dinat coor e rgen m
DE coor rev agent/ ch st ap or dinat ma cy ini ma sys
Na FA dinat iew mana an tas pro chan or na grou tia na ad
me ULT or er ger ge ks ver ge tasks ger p tor ger min
Wit TRUE
hdra
w
Sec
urity
stat
use
s
ch
an
ge ch
an an chan
al ge ge chan cha pro
ys an cha coor ge ng eme ble
KM KM SD t aly nge dinat coor e rgen m
DE coor rev agent/ ch st ap or dinat ma cy ini ma sys
Na FA dinat iew mana an tas pro chan or na grou tia na ad
me ULT or er ger ge ks ver ge tasks ger p tor ger min
ch
an
ge ch
an an chan
al ge ge chan cha pro
ys an cha coor ge ng eme ble
KM KM SD t aly nge dinat coor e rgen m
DE coor rev agent/ ch st ap or dinat ma cy ini ma sys
Na FA dinat iew mana an tas pro chan or na grou tia na ad
me ULT or er ger ge ks ver ge tasks ger p tor ger min
Mod TR
ify UE
Tem
plat
e
Tem TR
plat UE
e
Mas
s
Upd
ate
Co TR
mpl UE
ex
Mas
s
Upd
ate
SC Manage
cha cha
cha cha nge nge
D SD nge nge cha coo coo eme pro
N EF KM KM age anal anal nge rdin rdin cha rge ble
a A coo revi nt/m yst yst app ator ator nge ncy m sysa
m U rdin ewe ana cha task rove cha task man gro initi man dmi
e LT ator r ger nge s r nge s ager up ator ager n
C sc. sc. sc. sc. sc. sc. sc. sc. sc. sc. sc. sc. sc.
h man man man man man man man man man man man man man
a age. age. age. age. age. age. age. age. age. age. age. age. age.
n cmr cmr cmr cmr cmr cmr cmr cmr cmr cmr cmr cmr cmr
g
e
M
a
n
a
g
e
F
o
r
m
a
t
T sc. sc. sc. sc. sc. sc. sc. sc. sc. sc. sc. sc. sc.
a man man man man man man man man man man man man man
s age. age. age. age. age. age. age. age. age. age. age. age. age.
k cmt cmt cmt cmt cmt cmt cmt cmt cmt cmt cmt cmt cmt
M
a
n
a
g
e
F
o
r
m
a
t
cha cha
cha cha nge nge
D SD nge nge cha coo coo eme pro
N EF KM KM age anal anal nge rdin rdin cha rge ble
a A coo revi nt/m yst yst app ator ator nge ncy m sysa
m U rdin ewe ana cha task rove cha task man gro initi man dmi
e LT ator r ger nge s r nge s ager up ator ager n
I All All All All All All All All All All All All All
ni open open Ope Ope Ope Ope Ope Ope Ope open open Ope Ope
ti RF RF n n n n n n n RF RF n n
al Cs Cs Cha Cha Cha Cha Cha Cha Cha Cs Cs Cha Rele
C nges nges nges nges nges nges nges nges ases
h
a
n
g
e
V
ie
w
I All All All Ope Ope Ope Ope Ope All All All All All
ni Ope Ope Ope n n n n n Ope Ope Ope Ope Ope
ti n n n Cha Cha Cha Cha Cha n n n n n
al Tas Tas Cha nge nge nge nge nge Tas Tas Tas Cha Tas
T ks ks nge Tas Tas Tas Tas Tas ks ks ks nge ks
a Tas ks ks ks ks ks Tas
s ks Assi Assi Assi Assi Assi ks
k gned gned gned gned gned
V to to to to to
ie My My My My My
w Gro Gro Gro Gro Gro
up up up up up
Approvals/Groups
pr
ch ob
K cha cha chang an em le
M nge nge cha e chang ge erg m
DE KM re SD ana ana nge coordi e ma enc ini ma sys
FA coo vie agent lyst lyst app nator coordi na y tia na ad
Na UL rdin we /man cha task rov chang nator ge gro to ge mi
me T ator r ager nge s er e tasks r up r r n
Ca TR TR TR TRUE TR TR T TR
n UE U UE UE UE R UE
ac E U
ce E
ss
ap
pro
val
s
Ca TR TR TR TR
n UE UE UE UE
ov
erri
de
ap
pro
val
s
Ca TR TRUE TR TR TR
n UE UE UE UE
ma
ss
ap
pro
ve
pr
ch ob
K cha cha chang an em le
M nge nge cha e chang ge erg m
DE KM re SD ana ana nge coordi e ma enc ini ma sys
FA coo vie agent lyst lyst app nator coordi na y tia na ad
Na UL rdin we /man cha task rov chang nator ge gro to ge mi
me T ator r ager nge s er e tasks r up r r n
Ca
n
Del
eg
ate
Ap
pro
val
s
Ma
na
ger
Gr
oup
pr
ch ob
K cha cha chang an em le
M nge nge cha e chang ge erg m
DE KM re SD ana ana nge coordi e ma enc ini ma sys
FA coo vie agent lyst lyst app nator coordi na y tia na ad
Na UL rdin we /man cha task rov chang nator ge gro to ge mi
me T ator r ager nge s er e tasks r up r r n
pr
ch ob
K cha cha chang an em le
M nge nge cha e chang ge erg m
DE KM re SD ana ana nge coordi e ma enc ini ma sys
FA coo vie agent lyst lyst app nator coordi na y tia na ad
Na UL rdin we /man cha task rov chang nator ge gro to ge mi
me T ator r ager nge s er e tasks r up r r n
Query
ch ch
an an
ge ge chan
an an ge chan cha pro
al al cha coor ge ng eme ble
KM KM SD yst yst nge dinat coor e rgen m
DEF coor rev agent/ ch ta app or dinat ma cy ini ma sys
Na AU dinat iew manag an sk rov chan or na grou tiat na ad
me LT or er er ge s er ge tasks ger p or ger min
ch ch
an an
ge ge chan
an an ge chan cha pro
al al cha coor ge ng eme ble
KM KM SD yst yst nge dinat coor e rgen m
DEF coor rev agent/ ch ta app or dinat ma cy ini ma sys
Na AU dinat iew manag an sk rov chan or na grou tiat na ad
me LT or er er ge s er ge tasks ger p or ger min
ch ch
an an
ge ge chan
an an ge chan cha pro
al al cha coor ge ng eme ble
KM KM SD yst yst nge dinat coor e rgen m
DEF coor rev agent/ ch ta app or dinat ma cy ini ma sys
Na AU dinat iew manag an sk rov chan or na grou tiat na ad
me LT or er er ge s er ge tasks ger p or ger min
App
end
Que
ry
Initi
al
For
mat
QB
E
For
mat
Category
ch ch
an an
ge ge
an an chan chan
al al ge ge cha pro
ys ys cha coor coor ng eme ble
KM KM SD t t nge dinat dinat e rgen m
DE coor revi agent/ ch ta ap or or ma cy ini ma sys
Na FA dinat ewe mana an sk pro chan task na grou tia na ad
me ULT or r ger ge s ver ge s ger p tor ger min
Def KM KM
ault Docu Doc
Cha ment ume
nge nt
Cat
egor
y
Def
ault
Tas
k
Cat
egor
y
Allo
wed
Cat
egor
ies
configurat
ion configurat
Profile DEFAU administr administr ion coordina sysad tools
name LT ator ator auditor tor min tech admin
Securit
y
Rights
Allowe
d
statuse
s
configurat
ion configurat
Profile DEFAU administr administr ion coordina sysad tools
name LT ator ator auditor tor min tech admin
Searching
configurat
ion configurat tools
Profile DEFAU administra administra ion coordina sysad admi
name LT tor tor auditor tor min tech n
Search
format
Threadi
ng
configurat
ion configurat tools
Profile DEFAU administra administra ion coordina sysad admi
name LT tor tor auditor tor min tech n
configurati
Profil on tools
e DEFAU administrat administrat configurati coordinat sysadm tec admi
name LT or or on auditor or in h n
Restri
ct to
these
types
Security
ser
vic serv
e ice ser
inci incide inci des des vic
DEF config dent nt dent ope problem k k e
Nam AUL uration anal coord man initi rato manage age man tec sysa
e T auditor yst inator ager ator r r/coord nt ager h dmin
ser
vic serv
e ice ser
inci incide inci des des vic
DEF config dent nt dent ope problem k k e
Nam AUL uration anal coord man initi rato manage age man tec sysa
e T auditor yst inator ager ator r r/coord nt ager h dmin
Upda Neve Never Wh Alway Alw Nev Wh Always Alw Alw Alw Alwa
te r en s ays er en ays ays ays ys
assi assi
gne gne
d d
Mass FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA TRU
Inacti E SE E SE SE SE LS SE LS E
vate E E
Reop FALS FALSE FAL TRUE TRU FAL FAL FALSE TR TRU TR TRU
en E SE E SE SE UE E UE E
Upda FALS FALSE FAL FALS TRU FAL FAL TRUE FA FAL FA FAL
te E SE E E SE SE LS SE LS SE
when E E
close
d
Allow
ed
statu
ses
ser
vic serv
e ice ser
inci incide inci des des vic
DEF config dent nt dent ope problem k k e
Nam AUL uration anal coord man initi rato manage age man tec sysa
e T auditor yst inator ager ator r r/coord nt ager h dmin
Skip FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA FAL
query E SE E SE SE SE LS SE LS SE
warni E E
ng
Can FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA TRU
creat E SE E SE SE SE LS SE LS E
e E E
syste
m
views
Can FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA FAL
notify E SE E SE SE SE LS SE LS SE
E E
Lock FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA FAL
on E SE E SE SE SE LS SE LS SE
displ E E
ay
Alter TRU FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA FAL
nate E SE E SE SE SE LS SE LS SE
views E E
Can FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA TRU
susp E SE E SE SE SE LS SE LS E
end E E
Can FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA TRU
unsu E SE E SE SE SE LS SE LS E
spen E E
d
ser
vic serv
e ice ser
inci incide inci des des vic
DEF config dent nt dent ope problem k k e
Nam AUL uration anal coord man initi rato manage age man tec sysa
e T auditor yst inator ager ator r r/coord nt ager h dmin
Chan FALS FALSE FAL FALS TRU TR FAL FALSE FA FAL FA TRU
ge E SE E E UE SE LS SE LS E
categ E E
ory
Note FALS FALSE FAL FALS FAL TR FAL FALSE FA FAL FA TRU
s E SE E SE UE SE LS SE LS E
E E
Overr FALS FALSE FAL FALS FAL TR FAL FALSE FA FAL FA FAL
ide E SE E SE UE SE LS SE LS SE
E E
Can FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA FAL
use E SE E SE SE SE LS SE LS SE
callb E E
ack
list
Modif FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA TRU
y E SE E SE SE SE LS SE LS E
Temp E E
late
Temp FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA TRU
late E SE E SE SE SE LS SE LS E
Mass E E
Upda
te
ser
vic serv
e ice ser
inci incide inci des des vic
DEF config dent nt dent ope problem k k e
Nam AUL uration anal coord man initi rato manage age man tec sysa
e T auditor yst inator ager ator r r/coord nt ager h dmin
Com FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA TRU
plex E SE E SE SE SE LS SE LS E
Mass E E
Upda
te
Mass FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA TRU
Close E SE E SE SE SE LS SE LS E
E E
Forms
probl
confi incid em servi
N gurat incid ent incid man servi ce
a DEF ion ent coor ent ager/ ce desk servi
m AUL audit analy dinat man initia oper coor desk man ce sysa
e T or st or ager tor ator d agent ager tech dmin
D
e
f
a
ul
t
c
a
t
e
g
o
r
y
probl
confi incid em servi
N gurat incid ent incid man servi ce
a DEF ion ent coor ent ager/ ce desk servi
m AUL audit analy dinat man initia oper coor desk man ce sysa
e T or st or ager tor ator d agent ager tech dmin
Q
B
E
f
o
r
m
a
t
S apm. apm. apm. apm. apm. apm. apm. apm. apm. apm. apm. apm.
e searc searc searc searc searc searc searc searc searc searc searc searc
a h.pro h.pro h.pro h.pro h.pro h.pro h.pro h.pro h.pro h.pro h.pro h.pro
r bsum bsum bsum bsum bsum bsum bsum bsum bsum bsum bsum bsum
c mary mary mary mary mary mary mary mary mary mary mary mary
h
f
o
r
m
a
t
M sc.m sc.m sc.m sc.m sc.m sc.m sc.m sc.m sc.m sc.m sc.m sc.m
a anag anag anag anag anag anag anag anag anag anag anag anag
n e.pro e.pro e.pro e.pro e.pro e.pro e.pro e.pro e.pro e.pro e.pro e.pro
a blem blem blem blem blem blem blem blem blem blem blem blem
g
e
f
o
r
m
a
t
probl
confi incid em servi
N gurat incid ent incid man servi ce
a DEF ion ent coor ent ager/ ce desk servi
m AUL audit analy dinat man initia oper coor desk man ce sysa
e T or st or ager tor ator d agent ager tech dmin
I Open Open Open Open Open Open Open Open Open Open Open All
ni Incid Incid Incid Incid Incid Incid Incid Incid Incid Incid Incid Open
ti ents ents ents ents ents ents ents ents ents ents ents Incid
al Assig Assig Assig Assig Assig Assig Assig Assig Assig Assig Assig ents
vi ned ned ned ned ned ned ned ned ned ned ned
e To To To To To To To To To To To
w Me Me Me Me Me Me Me Me Me Me Me
I
ni
ti
al
f
o
r
m
a
t
I FALS FALS FALS FALS FALS FALS FALS FALS FALS FALS FALS FALS
ni E E E E E E E E E E E E
ti
al
s
c
ri
p
t
R FALS FALS FALS FALS FALS FALS FALS FALS FALS FALS FALS FALS
e E E E E E E E E E E E E
s
ol
u
ti
o
n
s
c
ri
p
t
probl
confi incid em servi
N gurat incid ent incid man servi ce
a DEF ion ent coor ent ager/ ce desk servi
m AUL audit analy dinat man initia oper coor desk man ce sysa
e T or st or ager tor ator d agent ager tech dmin
A
u
t
o
-
n
o
ti
f
y
f
o
r
m
a
t
V IM.br IM.br IM.br IM.br IM.br IM.br IM.br IM.br IM.br IM.br IM.br IM.br
ie owse owse owse owse owse owse owse owse owse owse owse owse
w
f
o
r
m
a
t
probl
confi incid em servi
N gurat incid ent incid man servi ce
a DEF ion ent coor ent ager/ ce desk servi
m AUL audit analy dinat man initia oper coor desk man ce sysa
e T or st or ager tor ator d agent ager tech dmin
I
n
ci
d
e
n
t
m
a
c
r
o
m
ai
l
f
o
r
m
a
t
D FALS TRU
e E E
f
a
ul
t
t
e
m
pl
a
t
e
probl
confi incid em servi
N gurat incid ent incid man servi ce
a DEF ion ent coor ent ager/ ce desk servi
m AUL audit analy dinat man initia oper coor desk man ce sysa
e T or st or ager tor ator d agent ager tech dmin
N
e
w
t
h
r
e
a
d
:
V
ie
w
--
S
e
a
r
c
h
N
e
w
t
h
r
e
a
d
:
S
e
a
r
c
h
--
Li
s
t
probl
confi incid em servi
N gurat incid ent incid man servi ce
a DEF ion ent coor ent ager/ ce desk servi
m AUL audit analy dinat man initia oper coor desk man ce sysa
e T or st or ager tor ator d agent ager tech dmin
N
e
w
t
h
r
e
a
d
:
Li
s
t
--
E
di
t
N
e
w
t
h
r
e
a
d
:
V
ie
w
--
E
di
t
probl
confi incid em servi
N gurat incid ent incid man servi ce
a DEF ion ent coor ent ager/ ce desk servi
m AUL audit analy dinat man initia oper coor desk man ce sysa
e T or st or ager tor ator d agent ager tech dmin
A
s
si
g
n
m
e
n
t
g
r
o
u
p
s
A
u
t
h
o
ri
z
e
d
c
a
t
e
g
o
ri
e
s
ser
vic serv
inci e ice ser
den incide inci de des vic
DEF config t nt dent ope problem sk k e
AUL uration ana coord man initi rato manage ag man tec sysa
Name T auditor lyst inator ager ator r r/coord ent ager h dmin
Check FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA FAL
similar E SE E SE SE SE LS SE LS SE
incide E E
nts
Check FALS FALSE FAL FALS FAL FAL FAL FALSE FA FAL FA FAL
incide E SE E SE SE SE LS SE LS SE
nt E E
duplic
ates
on
related
config
uration
items
Max
levels
Max
hits
Problems
Security
Allowed
statuses
Assignment
Groups
Views
Initial Inbox
Initial Format
Edit Format
Search
Format
List Format
Manage
Format
Print Format
Open Script
Resolution
Script
Append
Query
Problem Tasks
Security
Allowed
statuses
Assignment
Groups
Views
Initial Inbox
Initial Format
Edit Format
Search
Format
List Format
Manage
Format
Print Format
Known Errors
Security
Allowed
statuses
Assignment
Groups
Views
Initial Inbox
Initial Format
Edit Format
Search
Format
List Format
Manage
Format
Print Format
Open Script
Resolution
Script
Security
Allowed
statuses
Assignment
Groups
Views
Initial Inbox
Initial Format
Edit Format
Search
Format
List Format
Manage
Format
Print Format
View External
View Internal
KCS I
KCS II
KCS III
Admin
Rights
Allowed statuses
Rights
Allowed statuses
Response Objectives
Rights
Allowed statuses
Availability Objectives
Rights
Allowed statuses
Reporting Tables
DE sch
FA request request request request ed
Na UL request approv coordi receive review request request ule sysad
me T admin er nator r er tech or r min
Ma PROC
nag UREM
er ENT
Gro
up
DE sch
FA request request request request ed
Na UL request approv coordi receive review request request ule sysad
me T admin er nator r er tech or r min
DE sch
FA request request request request ed
Na UL request approv coordi receive review request request ule sysad
me T admin er nator r er tech or r min
S, S, S, S, S, S, S,
VPSY VPSY VPSY VPSY VPSY VPSY VPSY
S, S, S, S, S, S, S,
WAN WAN WAN WAN WAN WAN WAN
SUPP SUPP SUPP SUPP SUPP SUPP SUPP
ORT ORT ORT ORT ORT ORT ORT
Are All All All All All All All All All All
a
DE sch
FA request request request request ed
Na UL request approv coordi receive review request request ule sysad
me T admin er nator r er tech or r min
DE sch
FA request request request request ed
Na UL request approv coordi receive review request request ule sysad
me T admin er nator r er tech or r min
S, S, S,
VPSY VPSY VPSY
S, S, S,
WAN WAN WAN
SUPP SUPP SUPPO
ORT ORT RT
Rights
Basic
Option
s
All FALSE TRU FALS TRUE FALS FALS TRU FALSE TRUE TRUE
Functio E E E E E
ns
New FALSE TRU TRUE TRUE TRU FALS TRU TRUE TRUE TRUE
E E E E
Close FALSE TRU TRUE TRUE TRU TRU TRU FALSE TRUE TRUE
E E E E
Update Never Alwa Alway Always Alwa Never Alwa Never Always Always
ys s ys ys
View TRUE TRU TRUE TRUE TRU TRU TRU TRUE TRUE TRUE
E E E E
Allowe
d
statuse
s
Audit TRUE TRU TRUE TRUE TRU TRU TRU TRUE TRUE TRUE
History E E E E
Calcula FALSE TRU TRUE TRUE TRU FALS TRU TRUE FALSE TRUE
te E E E E
Impact
Chang FALSE TRU FALS TRUE TRU FALS TRU FALSE FALSE TRUE
e E E E E E
Catego
ry
Chang FALSE TRU FALS TRUE TRU FALS TRU FALSE FALSE TRUE
e E E E E E
Phase
Conf FALSE FAL FALS FALSE FALS FALS FAL FALSE FALSE FALSE
Close SE E E E SE
Conf FALSE FAL FALS FALSE FALS FALS FAL TRUE FALSE FALSE
Copy SE E E E SE
Open
Conf FALSE FAL FALS FALSE FALS FALS FAL TRUE FALSE FALSE
End SE E E E SE
Conf FALSE FAL FALS FALSE FALS FALS FAL FALSE FALSE FALSE
Open SE E E E SE
Conf FALSE FAL FALS FALSE FALS FALS FAL FALSE FALSE FALSE
Next SE E E E SE
Phase
Conf FALSE FAL FALS FALSE FALS FALS FAL FALSE FALSE FALSE
Print SE E E E SE
Conf FALSE FAL FALS FALSE FALS FALS FAL FALSE FALSE FALSE
Reope SE E E E SE
n
Conf FALSE FAL FALS FALSE FALS FALS FAL FALSE FALSE FALSE
Update SE E E E SE
Copy FALSE TRU TRUE TRUE TRU FALS TRU TRUE FALSE TRUE
Open E E E E
Genera FALSE TRU TRUE TRUE TRU FALS TRU TRUE FALSE TRUE
te E E E E
Orders
Line FALSE TRU TRUE TRUE TRU FALS TRU TRUE FALSE TRUE
Items E E E E
List TRUE TRU TRUE TRUE TRU TRU TRU TRUE FALSE TRUE
Pages E E E E
Post FALSE TRU TRUE TRUE TRU FALS TRU TRUE TRUE TRUE
E E E E
Receiv FALSE TRU FALS TRUE TRU FALS TRU FALSE FALSE TRUE
e E E E E E
Reope FALSE TRU TRUE TRUE TRU FALS TRU TRUE FALSE TRUE
n E E E E
Update FALSE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
when E E E E
closed
Search FALSE TRU TRUE TRUE TRU TRU TRU TRUE FALSE TRUE
Duplica E E E E
tes
Select TRUE TRU TRUE TRUE TRU TRU TRU TRUE FALSE TRUE
E E E E
Show FALSE TRU TRUE TRUE TRU FALS TRU TRUE FALSE TRUE
Scripts E E E E
Split FALSE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
E E E E
Show FALSE TRU TRUE TRUE TRU FALS TRU TRUE FALSE TRUE
Subtot E E E E
als
Validity FALSE TRU TRUE TRUE TRU FALS TRU TRUE FALSE TRUE
Lookup E E E E
Views TRUE TRU TRUE TRUE TRU TRU TRU TRUE FALSE TRUE
E E E E
Alert/Approval
Alert
Optio
ns
Alert TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
Log E E E E
Appro
val
Optio
ns
Approv TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
al E E E E
Action
Approv TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
al Log E E E E
Approv TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
als E E E E
Approv TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
e E E E E
Deny TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
E E E E
Retrac TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
t E E E E
Mass TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
Approv E E E E
e
Mass TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
Deny E E E E
Overri TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
de E E E E
Reeval TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
E E E E
Reset TRUE TRU TRUE TRUE TRU FALS TRU FALSE FALSE TRUE
E E E E
Delega FALSE FAL FALS FALSE FALS FALS FAL FALSE FALSE FALSE
te SE E E E SE
Approv
als
Print/Query
Print
Opti
ons
Back TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
grou E
nd
Fore TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
grou E
nd
Print TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
E
Print TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
List E
Print TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
Rec E
s
Print syspri syspri syspri syspri syspri syspri syspri syspri syspri
er nt.mvs nt.mvs nt.mvs nt.mvs nt.mvs nt.mvs nt.mvs nt.mvs nt.win
nt
QBE print.q print.q print.q print.q print.q print.q print.q print.q print.q print.q
List belist. belist. belist. belist. belist. belist. belist. belist. belist. belist.
Rep bg bg bg bg bg bg bg bg bg bg
ort
QBE ocmr.q ocmr.q ocmr.q ocmr.q ocmr.q ocmr.q ocmr.q ocmr.q ocmr.q ocmr.q
List be be be be be be be be be be
Form
at
QBE print.re print.re print.re print.re print.re print.re print.re print.re print.re print.re
Rec cords. cords. cords. cords. cords. cords. cords. cords. cords. cords.
s bg bg bg bg bg bg bg bg bg bg
Rep
ort
QBE print.q print.q print.q print.q print.q print.q print.q print.q print.q print.q
Rec belist. belist. belist. belist. belist. belist. belist. belist. belist. belist.
s bg bg bg bg bg bg bg bg bg bg
Form
at
Quer
y
Opti
ons
Activ TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
e E
Adva TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
nced E
Sear
ch
All TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
E
Clea TRUE TRUE TRUE TRUE TRUE FALS TRUE TRUE FALS TRUE
r E E
Appe
nd
Quer
y
Time 00:00: 00:00: 00:00: 00:00: 00:00: 00:00: 00:00: 00:00: 00:00: 00:00:
Limit 10 10 10 10 10 10 10 10 00 10
Defe TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
rred E
Inact TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
ive E
Mod FALS TRUE TRUE TRUE FALS FALS FALS FALS FALS TRUE
Time E E E E E E
Limit
Parti TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
al E
Key
Rest TRUE TRUE TRUE TRUE TRUE FALS TRUE TRUE FALS TRUE
ore E E
Skip FALS TRUE TRUE TRUE FALS FALS FALS FALS FALS TRUE
War E E E E E E
ning
Stan TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
dard E
Stru TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE FALS TRUE
cture E
d
Initia
l
Form
at
QBE
Form
at
Category/Statements
Categor
y
Restricti
ons
Default
Category
Allowed
Categori
es
Stateme
nts
Queue Options
Quo All my All my All my All my All my All my All my All my All my All my
te open open open open open open open open open open
Initi request reques reques requests reques reques reques reques reques reques
al s ts ts ts ts ts ts ts ts
Vie
w
Ord All All All All open All All All All All All
er open open open orders open open open open open open
Initi orders orders orders for orders orders orders orders orders orders
al for for for Compaq for for for for for for
Vie Compa Comp Comp Comp Comp Comp Comp Comp Comp
w q aq aq aq aq aq aq aq aq
Line Deferre Deferr Deferr Deferred Deferr Deferr Deferr Deferr Deferr Deferr
Item d new ed ed new ed ed ed ed ed new ed new
Initi Emplo new new Employ new new new new Emplo Emplo
al yee Emplo Emplo ee Emplo Emplo Emplo Emplo yee yee
Vie Setups yee yee Setups yee yee yee yee Setups Setups
w Setup Setup Setup Setup Setup Setup
s s s s s s
Quo
te
Que
ue
For
mat
Ord
er
Que
ue
For
mat
Line
Item
Que
ue
For
mat
Threading
View -- Search
Search -- List
List -- Edit
View-- Edit
Contracts
Contract Templates
Software Counters
Payments
Asset Allocation
General Privileges
PAYMENT contract
Name DEFAULT SPECIALIST specialist sysadmin
Require Password
PAYMENT contract
Name DEFAULT SPECIALIST specialist sysadmin
Approval delegation
Approval delegation is an optional feature that enables users with approval rights to temporarily
delegate their approval authority to another qualified operator. Operators with the Delegate Approvals
or Can Delegate Approvals option enabled in their application profiles can delegate some or all of their
approvals by using the Approval Delegation wizard.
Using the Approval Delegation wizard, an operator can grant another qualified operator the right to
temporarily view and act on items in his or her approval queue. The wizard offers the following
delegation options:
The Approval Delegation wizard enables an operator to create any number of approval delegation
combinations, including delegating the same approvals to multiple operators at the same time.
Delegators can also update an existing approval delegation to change the delegation start and end
dates, as well as change the delegate's name.
Note: HP Service Manager tracks all changes to approval delegations using the standard field
auditing capability.
When delegates log on to Service Manager, they see both their own and any delegated approvals in
their approval list. For security reasons, delegates always retain their original application profiles and
operator records. Service Manager determines what temporary rights delegates have when they view
or act on an approval.
l Change Management
l Request Management
l Service Catalog
To enable approval delegation for one of these applications, an Administrator must edit one of the
application's profile records and select the Delegate Approvals or Can Delegate Approvals option.
Next, the Administrator must grant this application profile to the operators who will be given approval
delegation authority.
Note: If you want to support approval delegation for an application that does not support approvals
out-of-box, you must first enable and customize approvals for the application.
Approval delegation never changes a delegate's original application profile or operator record. Service
Manager only changes a delegate's approval groups in memory when the following conditions occur.
By default, Service Manager sends an email notification to the approval delegate when the following
conditions occur:
Note: Service Manager also sends an email notification to the approval owner when a new
approval arrives in the owner's queue. System Administrators can change the notification
behaviors for approval delegation directly from the notification engine.
A delegated approval always retains its original operator assignment. Service Manager records the
delegate's actions separately from the owner in the following new fields:
approved.by Operator The name of the operator who acted on the approval.
approved.for Approved For The name of operator who delegated the approval.
Note: Delegators and delegates can view these fields from the approval record and the approval
log. However, in some cases, only a delegator may have the approval group necessary to view the
records in the approval log. A delegate's temporary rights do not include viewing approvals in the
log. In order to view approvals in the approval log, a delegate's application profile must include the
required approval groups.
To delegate approval authority for this Requires enabling this application profile
application option
The Delegate Approvals or Can Delegate Approvals profile option only controls whether an operator
can view the Approval Delegation wizard. Separate application profile options control whether an
operator can view or approve objects in an application.
Refer to the following example for how to enable approval delegation for Change Management.
1. Edit the profile record which you want to grant approval delegation authority.
c. In the Name field, type the name of the security role you want to grant approvals. For
example, change approver.
g. Click Save.
Note: It is a best practice to only enable the Delegate Approvals or Can Delegate
Approvals option for operators who can also view and approve objects in the application.
2. Edit the operator record to display Delegate Approval in the System Navigator.
b. Type Change.Approver in the Login Name field, and then click Search.
d. Start with a new table row, type string1 in Parameter Names and ESSSM-Approval in
Parameter Values.
e. Click Save.
You can find Delegate Approval is displayed in the System Navigator now.
When you open the Approval Delegation wizard, the wizard generates a list of qualified operators
who are eligible for approval delegation. The wizard determines operator eligibility based on the
following criteria:
To delegate approvals for Requires these application And at least one of these
this application profile rights capability words
change request
change task
Approvals OCMAdmin
Approve OCMQ
For example, if Change.Approver wants to delegate all approvals to another operator, the potential
delegate must have the following rights and capability words:
l View and approval rights to the Change Management and Request Management applications
If, however, Change.Approver only wants to delegate Service Catalog approvals, then potential
delegates are only required to have view rights for the Service Desk application.
In some cases, you may not see any qualified operators. You may also want to delegate to an operator
who is not currently on the list of qualified operators. In either case, ask your System Administrator to
grant the desired operator the necessary rights to be an approval delegate.
Enabling approvals and approval delegation requires administrative access to the system database
dictionary, the Forms Designer utility, application profiles, and the script library. You should also know
which tables and fields the application uses.
Refer to the following checklist for how to set up an application to enable approvals and approval
delegation for Problem Management.
Note:
l To complete this checklist, follow the step-by-step procedures described in the following
examples found in the related topics.
l You must use the Windows client whenever you need to add a new field/key to a database
dictionary table.
1. Edit the object definition for the application to enable approvals by category.
2. Edit the database dictionary for Problem Management to add an approval status field.
3. Edit the database dictionary for the Problem Management categories to add an approval field.
5. Edit the database dictionary for the Problem Management profile record to add to an approval
groups field.
6. Create a new approval definition record to manage the Problem Management approvals.
7. Edit the Problem Management category definitions to add your new approval definition.
8. Edit the Problem Management profile records that you want to have access to your custom
approval group.
9. Edit the script that controls the approval inbox to add your custom approvals to the list of
approvals the system displays.
For more information, see "Example: Enabling Approval Delegation for custom Problem Management
approvals" on page 168 and "Example: Enabling custom approvals for Problem Management" below.
The following example illustrates how to enable approvals for Problem Management. At the end of this
example, you will be able to:
Note: In order to enable custom approvals for Problem Management, you must perform the entire
sequence of example tasks. You must be a System Administrator, or have equivalent system
privileges, to perform the steps in this example. Also, you must use the Windows client whenever
you need to add a new field/key to a database dictionary table.
Task 1: Edit the object definition for the application to enable approvals by category.
3. Type rootcause in the File Name field, and then click Search.
4. Click the Approvals tab, and then type the following field values.
Field Value
Field Value
Note: The fields approvals and approval.status fields do not yet exist. You will add the field
name to the Problem Management database dictionary in a later step.
5. Click Save.
Task 2: Edit the database dictionary for the application to add an approval status field.
2. Type rootcause in the File Name field, and then click Search.
3. Select the descriptor row in the Fields tab, and then click New Field/Key.
Name approval.status
Type character
Service Manager prompts you to confirm how you want to change the tables in the RDBMS.
7. If Service Manager has write permissions to the RDBMS, click SM Alters. Otherwise, click User
Alters.
Note: Check your DDL output folder for DDL text you can use to update your RDBMS
manually.
Task 3: Edit the database dictionary for the application's categories to add an approval field.
2. Type rootcausecat in the File Name field, and then click Search.
3. Select the descriptor row in the Fields tab, and then click New Field/Key.
Name approvals
Type array
5. Click Add Field. Service Manager prompts you to select the array's data type.
Service Manager prompts you to confirm how you want to change the tables in the RDBMS.
8. If Service Manager has write permissions to the RDBMS, click SM Alters. Otherwise, click User
Alters.
Note: Check your DDL output folder for DDL text you can use to update your RDBMS
manually.
Task 4: Edit the necessary forms to add the new approval fields.
3. Click Design.
4. Click Group.
Property Value
Width 152
7. Click Comfill, and then click within the Approval Requirements group.
Property Value
Input approvals
Array Length 5
For example, you may want to position the group between the Active? check box and the Phase
name table.
11. Click OK to save the form and return to the Forms Designer search screen.
14. Click Label, and then click in the open space beneath the Record Number label.
Property Value
X 2
Y 5
Width 34
16. Click Text, and then click to the right of the Approval Status: label.
Property Value
X 36
Y 5
Width 36
Input approval.status
Read-Only Selected
19. Click OK to save the form and return to the Forms Designer search screen.
Task 5: Edit the database dictionary for the application's profile record to add to an approval
groups field.
2. Type rcenv in the File Name field, and then click Search.
3. Select the descriptor row in the Fields tab, and then click New Field/Key.
Name approval.groups
Type array
5. Click Add Field. Service Manager prompts you to select the array's data type.
6. Select character.
Task 6: Create a new approval definition record to manage the application's approvals.
3. Click Design.
4. Click Label, and then click in the open space beneath the Complex Mass Update check box.
Property Value
X 2
Y 31
Width 28
6. Click Comfill, and then click to the right of the Approval Groups: label.
Property Value
X 31
Y 31
Input approval.groups
Array Length 5
9. Click OK to save the form and return to the Forms Designer search screen.
Task 7: Edit the application's category definitions to add your new approval definition.
3. Add the following link entry at the end of the list of links.
Property Value
4. Click Save.
Note: You are using a Change Management menu link because by default, Problem
Management does not have a menu item for Approvals.
Field Value
Group/Oper HELPDESK
Sequence 1
Condition true
7. Click Add.
9. In the Name field, type the name of a Problem Management category that you want to trigger your
custom approval process. For example, ITIL.
Note: You can repeat this step for each Problem Management category you want to trigger
approvals.
Task 8: Edit the application profile records that you want to have access to your custom
approval group.
2. In the Profile Name field, type the name of a profile you want to grant approvals. For example,
SYSADMIN.
3. Click Search.
4. In the Approval Groups array, type the name of the approval group you defined to manage
approvals. For example, HELPDESK.
5. Click Save.
6. Log out the current operator and log on to Service Manager with an operator account that has the
SYSADMIN Problem Management profile. For example, System.Admin.
8. Create a new problem record and note the record number. For example, PM0002.
Note: The Category field on the Problem Control form maps to the Incident Management
category, not the Problem Management category. Since there is only one approval category
for ITIL Problem Management, any problem you create will automatically be part of the ITIL
Problem Management category.
Task 9: Edit the script that controls the approval inbox to add your custom approvals to the
list of approvals the system displays.
4. In the Id field, type the record number for the problem you created. For example, PM0002.
9. Remove the comment lines /* and */ at lines 49 and 55 to enable the function.
Service Manager displays the list of pending approvals. Check the list for your custom approval.
For example, PM0002.
The following example shows how to delegate the custom Problem Management approvals you
created in a previous example. At the end of this example, you will be able to:
Note: In order to enable approval delegation for custom Problem Management approvals, you
must perform the entire sequence of example tasks. You must be a System Administrator, or have
equivalent system privileges, to perform the steps in this example. Also, you must use the
Windows client whenever you need to add a new field or key to a database dictionary table.
3. Type rcenv in the File Name field, and then click Search.
4. Select the descriptor row in the Fields tab, and then click New Field/Key.
Name can.delegate
Type logical
3. Click Design.
Property Value
Y 23
5. Select the Assignment Groups label, and change its property as follows.
Property Value
Y 21
6. Click Checkbox.
7. Click on the empty space between the Assignment Groups label and the Skip Query Warning
check box.
Property Value
X 80
Property Value
Y 19
Input can.delegate
10. Click OK to save the form and return to the Forms Designer search screen.
2. Type the name of a profile you want to grant approval delegation rights in the Profile Namefield.
For example, SYSADMIN.
3. Click Search.
5. Click Save.
3. Locate the checkProfileForModule(filename, operator) function, and then remove the /* and
*/comment lines at lines 6 and 17 to enable the function.
This function makes problem records a valid choice in the approval type list of the Approval
Delegation wizard.
b. Remove the /* and */ comment lines at lines 27 and 40 to enable the function.
This function returns all the approvals groups defined for the profile of the current application.
a. Verify that the line 100 lists profile_rootcause as the profile definition.
To use another application, type a different profile table name between the quotation marks.
6. Click Save.
7. Click Compile.
6. Type the // comment characters at the beginning of line 32 to deactivate the line.
7. Click Save.
8. Click Compile.
Task 6: Add a new approval delegation for the new Problem Management custom
approvals.
Property Value
Delegate Problem.Manager
3. Log out the current operator and log on to Service Manager as the delegate. For example,
Problem.Manager.
You should see the Problem approval you created previously. For example, PM0002.
$G.delegated.cm3r.groups Stores the approval groups that are associated with Change
Management changes that the current operator can view and act on
as an approval delegate.
$G.delegated.cm3t.groups Stores the approval groups that are associated with Change
Management tasks that the current operator can view and act on as
an approval delegate.
$G.delegated.ocmq.groups Stores the approval groups that are associated with Request
Management that the current operator can view and act on as an
approval delegate.
$G.delegated.svc.groups Stores the approval groups that are associated with Service Catalog
that the current operator can view and act on as an approval
delegate.
Viewing approvals
When you log on to Service Manager, you will see both your own and any delegated approvals in your
approval queue.
l To view approvals that another operator has delegated to you, you can use the Active approval
delegations assigned to me view.
l To view approvals delegated to you in the past, you can use the Past approval delegations
assigned to me view.
l To see which items in the approval queue are due to an active approval delegation, you can open
the Approve Requests view from the System navigator. In this view, Service Manager indicates
which approvals are in the queue due to an active delegation by displaying a value of YES in the As
Delegate? column. You can use this view to view, approve, or deny approval requests.
l Service Manager lists your name in the Operator column of the Completed Approval Actions table.
l Service Manager lists the delegator's name in the Approve For column of the Completed Approval
Actions table.
Approval delegation never changes a delegate's original application profile or operator record. HP
Service Manager only changes a delegate's approval group rights in memory when the following
conditions occur.
The manager is the delegator in this example, thereby temporarily delegating approval authority for the
following application profiles and approval groups:
FACILITIES
HELPDESK
LAN SUPPORT
M/F SUPPORT
ONLINE SUPPORT
WAN SUPPORT
TRAINING
TRAINING
TELECOMS
SUPPORT ADMIN
SYSTEMS ADMIN
SOFTWARE
SERVICE DESK
PROCUREMENT
The technician is the delegate in this example. The technician's original approval authority includes the
following application profiles and approval groups:
LAN SUPPORT
M/F SUPPORT
ONLINE SUPPORT
WAN SUPPORT
When the manager delegates approval authority to the technician, the technician temporarily becomes
a member of all of the approval groups that the manager is a member of:
FACILITIES no
LAN SUPPORT no
M/F SUPPORT no
ONLINE SUPPORT no
WAN SUPPORT no
FACILITIES Yes
HELPDESK Yes
TRAINING Yes
TRAINING Yes
TELECOMS Yes
SOFTWARE Yes
PROCUREMENT Yes
As a delegator, you always retain your normal approval authority. Both you and any delegates you
authorize have the ability to approve items while an approval delegation is active.
Viewing approvals
As a delegator, when you log on to HP Service Manager, you will see both your own and any delegated
approvals in your approval queue.
l To view your active approval delegations, you can use the Approval Delegation wizard or the My
active approval delegations view.
l To view your past delegations, you can use the Copy Approval Delegation wizard or the My past
approval delegations view.
l Service Manager lists the delegate's name in the Operator column of the Completed Approval
Actions table.
l Service Manager lists the delegator's name in the Approve For column of the Completed Approval
Actions table.
You can only delegate approvals to another operator if a System Administrator enables the Delegate
Approvals or Can Delegate Approvals option for you in your application profile.
1. Click Approval Delegation. The Approval Delegation wizard opens and displays any active
approval delegations assigned to you.
Note: HP Service Manager only displays operators who are eligible approval delegates. If you
do not see a particular operator listed as a potential delegate, it means that the operator does
not have one or more of the rights required to be eligible for approval delegation. Consult your
System Administrator if you want to assign additional rights to a particular operator.
6. Select the date range during which the approval delegation will be active.
You can change the delegate, the start date, or the end date of any currently active approval delegation
by using the Approval Delegation wizard. If you want to use a delegation as a template for a new
delegation, use the Copy Approval Delegation wizard.
1. Click Approval Delegation. The Approval Delegation wizard opens and displays any active
approval delegations assigned by you.
2. Select the approval you want to edit from the list of active delegations.
4. Select the new start and end dates for the approval delegation.
Note: Service Manager dates always default to midnight (00: 00: 00) of the selected day. If
you want to set a different start time, manually type in the new start time using the twenty-four
hour: minute: second format notation. For example 23: 59: 59 represents 11: 59 PM and
59 seconds.
You can disable any currently active approval delegation. You cannot disable an inactive past
delegation.
The Approval Delegation wizard opens and displays any active approval delegations assigned
by you.
2. Select the approval you want to disable from the list of active delegations.
Note: To view your past delegations or delegations assigned to you, use one of the default
approval delegation views.
You can use an existing approval delegation as a template to create a new approval delegation. The
wizard copies the values from the existing delegation and allows you to change the delegate and the
delegation dates. You cannot change the application module, delegated approval groups, or operator
when copying an approval delegation. If you want to change these values, you must create a new
approval delegation.
1. From the To Do view, select Approval Delegation from the Queue list. HP Service Manager
displays the Approval Delegation view.
2. From the View list, select either My active approval delegations or My past approval
delegations.
3. Select the approval you want to copy from the list of approval delegations.
4. Click Copy Approval Delegation. Service Manager displays the Copy Approval Delegation
wizard and automatically fills in the delegate name, the delegated module, approval groups, and
operator.
7. Select Enabled.
Available
View Description Actions
My active A list of the currently active approvals that you delegated to other l Start the
approval operators. This view does not display future delegations because Approval
delegations they are not currently active. Delegation
wizard
l Export
l Print
My past A list of the inactive approvals that you delegated to other operators l Start the
approval in the past. Copy
delegations Approval
Delegation
wizard
l Export
l Print
Available
View Description Actions
Active A list of the currently active approvals delegated to you. This view l Export
approvals only displays approvals where you are the active delegate. Use the
assigned to other views to display your past or pending delegations. l Print
me
Past A list of the inactive approvals that other operators have delegated to l Export
approvals you in the past.
assigned to l Print
me
Note: If you create or update an approval delegation record you may need to use the Service
Manager Refresh option in order for the views listed above to display the new delegation record.
User roles
The Service Management process can meet best practices when employees involved in the process
are assigned user roles in your IT organization. For information on the Service Management
organizational model of user roles for best practices, see HP Service Manager Processes and Best
Practices Guide in the related topics.
A user role is a template that combines a collection of application profiles, security roles, and capability
words into a single record. Service Manager provides out-of-box user role descriptions with appropriate
capability words and application profiles that define a variety of business functions or roles. By defining
and assigning user role descriptions, a System Administrator can grant an operator the capability words
and application profile required for a particular job.
Role Responsibilities
User l Report all IT-related requests to the service desk or use the self-service web
pages
l Register incidents based on user interactions and assign them to the correct
support group
l Monitor the Service Level Agreement (SLA) targets of all registered incidents
and escalate the incidents if required
expedite
change
service
desk
user.fav
orites
incident
manage
ment
ChMAd
min
OCMQ
OCML
inventor
y
manage
ment
change
request
incident
manage
ment
service
desk
EditCon
tacts
service
catalog
user.fav
orites
Role Responsibilities
Change Analyst l May be involved in the change assessment and planning phase to deliver
input to the Change Coordinator when assessing the change impact
l Verifies that tasks are correctly assigned and rejects tasks if needed
l Assign tasks to the Change Analysts and perform action based on the
outcome of the change implementation
l After implementation, evaluate the change handling and close the change
Change l Review all changes after the assessment and planning phase and address
Manager the right Change Approvers
Change l Approve or deny Change when requested. This can be either electronically
Approver by using the service management tool or by using a Change Advisory Board
(CAB) or Emergency-Change Advisory Board (E-CAB) meeting.
Release l Change Analyst who transfers the new release from development to test
Packaging environment or from test to production environment.This role cannot be
&Build Manager fulfilled by the Change Analyst who has built the new release.
Chang Reque
Configu Servi Inciden Proble e st Service Contra
ration ce t m Manag Manag Level ct
Manage Desk Manag Manag ement ement Manag Manag Capabili
User ment Profil ement ement Profile Profile ement ement ty
Role Profile e Profile Profile s s Profile Profile Words
user.fav
orites
incident
manage
ment
Chang Reque
Configu Servi Inciden Proble e st Service Contra
ration ce t m Manag Manag Level ct
Manage Desk Manag Manag ement ement Manag Manag Capabili
User ment Profil ement ement Profile Profile ement ement ty
Role Profile e Profile Profile s s Profile Profile Words
user.fav
orites
incident
manage
ment
user.fav
orites
incident
manage
ment
Chang Reque
Configu Servi Inciden Proble e st Service Contra
ration ce t m Manag Manag Level ct
Manage Desk Manag Manag ement ement Manag Manag Capabili
User ment Profil ement ement Profile Profile ement ement ty
Role Profile e Profile Profile s s Profile Profile Words
user.fav
orites
incident
manage
ment
ChMAd
min
OCMQ
OCML
Chang Reque
Configu Servi Inciden Proble e st Service Contra
ration ce t m Manag Manag Level ct
Manage Desk Manag Manag ement ement Manag Manag Capabili
User ment Profil ement ement Profile Profile ement ement ty
Role Profile e Profile Profile s s Profile Profile Words
user.fav
orites
incident
manage
ment
EditCont
acts
data
Administ
rator
public.fa
vorites
data
Administ
rator
OCMQ
OCMO
OCML
Role Responsibilities
Configuration l Review and validate CMS updates and create exception reports if needed.
Auditor
l Conduct configuration audits and perform appropriate actions if an
unregistered component is detected or if a component is missing.
CMS/Tools l Configure the data model, policies, and CI types in the service management
Administrator tool
Chang Reque
Configu Servi Incide Proble e st Service Contra
ration ce nt m Manag Manag Level ct
Manage Desk Manag Manag ement ement Manag Manag Capabil
User ment Profil ement ement Profile Profile ement ement ity
Role Profile e Profile Profile s s Profile Profile Words
user.fav
orites
incident
manage
ment
ICMAd
min
OCMQ
OCML
Chang Reque
Configu Servi Incide Proble e st Service Contra
ration ce nt m Manag Manag Level ct
Manage Desk Manag Manag ement ement Manag Manag Capabil
User ment Profil ement ement Profile Profile ement ement ity
Role Profile e Profile Profile s s Profile Profile Words
user.fav
orites
incident
manage
ment
user.fav
orites
incident
manage
ment
Chang Reque
Configu Servi Incide Proble e st Service Contra
ration ce nt m Manag Manag Level ct
Manage Desk Manag Manag ement ement Manag Manag Capabil
User ment Profil ement ement Profile Profile ement ement ity
Role Profile e Profile Profile s s Profile Profile Words
CMS DEFAU DEF DEFA DEFA DEFA DEFA DEFA DEFA partial.k
LT AULT ULT ULT ULT ULT ULT ULT ey
change
request
change
task
problem
manage
ment
expedite
change
service
desk
user.fav
orites
incident
manage
ment
EditCont
acts
data
Administ
rator
public.fa
vorites
data
Administ
rator
OCMQ
OCMO
OCML
Chang Reque
Configu Servi Incide Proble e st Service Contra
ration ce nt m Manag Manag Level ct
Manage Desk Manag Manag ement ement Manag Manag Capabil
User ment Profil ement ement Profile Profile ement ement ity
Role Profile e Profile Profile s s Profile Profile Words
user.fav
orites
incident
manage
ment
ICMAd
min
ChMAd
min
OCMQ
OCML
Role Responsibilities
Operator l Register incident based on an event and assign to the correct support group.
Role Responsibilities
Incident l Review and accept or reject incidents assigned to the support group.
Coordinator
l Handle incidents escalated by an Incident Analyst of the support group.
l Register incidents based on user interactions and assign them to the correct
support group
l Monitor the Service Level Agreement (SLA) targets of all registered incidents
and escalate the incidents if required
Role Responsibilities
Reque
Configu Servi Inciden Proble st Service Contra
ration ce t m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabil
User ment Profil ement ement ment Profile ement ement ity
Role Profile e Profile Profile Profiles s Profile Profile Words
query.st
ored
inventor
y
manage
ment
change
request
incident
manage
ment
service
desk
OCMQ
OCML
user.fav
orites
Reque
Configu Servi Inciden Proble st Service Contra
ration ce t m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabil
User ment Profil ement ement ment Profile ement ement ity
Role Profile e Profile Profile Profiles s Profile Profile Words
query.st
ored
inventor
y
manage
ment
change
request
incident
manage
ment
service
desk
OCMQ
OCML
user.fav
orites
Reque
Configu Servi Inciden Proble st Service Contra
ration ce t m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabil
User ment Profil ement ement ment Profile ement ement ity
Role Profile e Profile Profile Profiles s Profile Profile Words
query.st
ored
inventor
y
manage
ment
change
request
incident
manage
ment
service
desk
OCMQ
OCML
user.fav
orites
Reque
Configu Servi Inciden Proble st Service Contra
ration ce t m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabil
User ment Profil ement ement ment Profile ement ement ity
Role Profile e Profile Profile Profiles s Profile Profile Words
query.st
ored
inventor
y
manage
ment
change
request
incident
manage
ment
service
desk
Incident
Admin
OCMQ
OCML
user.fav
orites
Reque
Configu Servi Inciden Proble st Service Contra
ration ce t m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabil
User ment Profil ement ement ment Profile ement ement ity
Role Profile e Profile Profile Profiles s Profile Profile Words
query.st
ored
inventor
y
manage
ment
change
request
incident
manage
ment
service
desk
EditCon
tacts
SDAdmi
n
OCMQ
OCML
user.fav
orites
Role Responsibilities
Problem Manager l Prioritize and plan problems registered by the Problem Coordinators
l Monitor problem and known error resolution progress and perform required
action
Problem Analyst l Investigate and diagnose assigned problems for workarounds and/or root
causes
Chang Reque
Configu Servi Proble e st Service Contra
ration ce Incident m Manag Manag Level ct
Manage Desk Manage Manag ement ement Manag Manag Capabi
User ment Profil ment ement Profile Profile ement ement lity
Role Profile e Profile Profile s s Profile Profile Words
problem
manage
ment
expedit
e
change
service
desk
user.fav
orites
incident
manage
ment
Chang Reque
Configu Servi Proble e st Service Contra
ration ce Incident m Manag Manag Level ct
Manage Desk Manage Manag ement ement Manag Manag Capabi
User ment Profil ment ement Profile Profile ement ement lity
Role Profile e Profile Profile s s Profile Profile Words
problem
manage
ment
expedit
e
change
service
desk
user.fav
orites
incident
manage
ment
Chang Reque
Configu Servi Proble e st Service Contra
ration ce Incident m Manag Manag Level ct
Manage Desk Manage Manag ement ement Manag Manag Capabi
User ment Profil ment ement Profile Profile ement ement lity
Role Profile e Profile Profile s s Profile Profile Words
problem
manage
ment
expedit
e
change
service
desk
user.fav
orites
incident
manage
ment
OCMQ
OCML
Role Responsibilities
Role Responsibilities
Assign this level to operators who are trained on the KCS practices and have demonstrated
consistent competency.
U
se Configur Serv Proble Reques Service Contrac
r ation ice Incident m Change t Level t
R Manage Desk Manage Manage Manage Manage Manage Manage Capabil
ol ment Profi ment ment ment ment ment ment ity
e Profile le Profile Profile Profiles Profiles Profile Profile Words
expedite
change
user.fav
orites
incident
manage
ment
U
se Configur Serv Proble Reques Service Contrac
r ation ice Incident m Change t Level t
R Manage Desk Manage Manage Manage Manage Manage Manage Capabil
ol ment Profi ment ment ment ment ment ment ity
e Profile le Profile Profile Profiles Profiles Profile Profile Words
expedite
change
user.fav
orites
incident
manage
ment
expedite
change
incident
manage
ment
user.fav
orites
Role Responsibilities
l For some releases, the Release Manager identifies and describes the type of
training to be provided, when the training is to be conducted, how it is to be
administered, and the reasons for providing it.
Release l Creates and implements release plans and conducts release plan reviews
Packaging/Build when necessary
Manager
Reque
Config Servi Incide Proble st Servic Contra
uration ce nt m Change Manag e Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabi
User ment Profi ement ement ment Profile ement ement lity
Role Profile le Profile Profile Profiles s Profile Profile Words
proble
m
manag
ement
expedit
e
change
service
desk
user.fa
vorites
incident
manag
ement
ChMAd
min
OCMQ
OCML
Reque
Config Servi Incide Proble st Servic Contra
uration ce nt m Change Manag e Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabi
User ment Profi ement ement ment Profile ement ement lity
Role Profile le Profile Profile Profiles s Profile Profile Words
proble
m
manag
ement
expedit
e
change
service
desk
user.fa
vorites
incident
manag
ement
ChMAd
min
OCMQ
OCML
Role Responsibilities
Request Approver l Approve requests before they can be processed and filled.
Role Responsibilities
Request l Coordinate requests. May also be responsible for receiving things into
Coordinator inventory.
Request Helpdesk l Provide helpdesk assistance for opening new item requests.
Tech
l Process service requests.
l Oversee the request process through its cycle back to the customer.
Request Reviewer l Evaluate a Request Management quote for potential errors. A reviewer
may not necessarily have approval rights.
Requestor l Initiate a request through Request Management and search and view
request records.
Reque
Configu Servi Incide Proble st Service Contra
ration ce nt m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabi
User ment Profil ement ement ment Profile ement ement lity
Role Profile e Profile Profile Profiles s Profile Profile Words
problem
manage
ment;
expedit
e
change;
ChMAd
min;
OCMA
dmin;
OCML;
OCMO
OCMQ
incident
manage
ment
user.fa
vorites
Reque
Configu Servi Incide Proble st Service Contra
ration ce nt m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabi
User ment Profil ement ement ment Profile ement ement lity
Role Profile e Profile Profile Profiles s Profile Profile Words
request DEFAU DEF DEFA DEFA DEFAU request DEFA DEFA partial.k
approv LT AULT ULT ULT LT approv ULT ULT ey
er er
problem
manage
ment
inventor
y
manage
ment
change
request
change
task
OCMQ
OCML
query.s
tored
user.fa
vorites
incident
manage
ment
Reque
Configu Servi Incide Proble st Service Contra
ration ce nt m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabi
User ment Profil ement ement ment Profile ement ement lity
Role Profile e Profile Profile Profiles s Profile Profile Words
request DEFAU DEF DEFA DEFA DEFAU request DEFA DEFA partial.k
coordin LT AULT ULT ULT LT coordin ULT ULT ey
ator ator OCML
OCMO
OCMQ
change
request
change
task
problem
manage
ment
user.fa
vorites
incident
manage
ment
Reque
Configu Servi Incide Proble st Service Contra
ration ce nt m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabi
User ment Profil ement ement ment Profile ement ement lity
Role Profile e Profile Profile Profiles s Profile Profile Words
request DEFAU DEF DEFA DEFA DEFAU request DEFA DEFA partial.k
helpde LT AULT ULT ULT LT tech ULT ULT ey
sk tech
problem
manage
ment
inventor
y
manage
ment
change
request
change
task
OCMQ
OCML
query.s
tored
user.fa
vorites
incident
manage
ment
Reque
Configu Servi Incide Proble st Service Contra
ration ce nt m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabi
User ment Profil ement ement ment Profile ement ement lity
Role Profile e Profile Profile Profiles s Profile Profile Words
request coordina initiat initiator reviewe initiator request DEFA contrac partial.k
procure tor or r receiver ULT t ey
ment speciali
mgr. st problem
manage
ment
inventor
y
manage
ment
change
request
change
task
OCMQ
OCML
query.s
tored
incident
manage
ment
OCMO
user.fa
vorites
Reque
Configu Servi Incide Proble st Service Contra
ration ce nt m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabi
User ment Profil ement ement ment Profile ement ement lity
Role Profile e Profile Profile Profiles s Profile Profile Words
request DEFAU DEF DEFA DEFA DEFAU request DEFA DEFA partial.k
review LT AULT ULT ULT LT reviewe ULT ULT ey
er r
problem
manage
ment
inventor
y
manage
ment
change
request
change
task
OCMQ
OCML
query.s
tored
user.fa
vorites
incident
manage
ment
Reque
Configu Servi Incide Proble st Service Contra
ration ce nt m Change Manag Level ct
Manage Desk Manag Manag Manage ement Manag Manag Capabi
User ment Profil ement ement ment Profile ement ement lity
Role Profile e Profile Profile Profiles s Profile Profile Words
request DEFAU DEF DEFA DEFA DEFAU request DEFA DEFA partial.k
or LT AULT ULT ULT LT or ULT ULT ey
problem
manage
ment
inventor
y
manage
ment
change
request
change
task
OCMQ
OCML
query.s
tored
user.fa
vorites
incident
manage
ment
Role Responsibilities
Service Catalog l Manage the Catalog, including adding, updating, and deleting catalog
Manager entries.
Role Responsibilities
System Access all system capabilities and functions. This role has complete access to the
Administrator system.
Chang Reque
Configu Servi Incide Proble e st Service Contra
ration ce nt m Manag Manag Level ct
Manage Desk Manag Manag ement ement Manag Manag Capabil
User ment Profil ement ement Profile Profile ement ement ity
Role Profile e Profile Profile s s Profile Profile Words
user.fav
orites
incident
manage
ment
EditCont
acts
data
Administ
rator
public.fa
vorites
data
Administ
rator
OCMQ
OCMO
OCML
EditOper
ators
Chang Reque
Configu Servi Incide Proble e st Service Contra
ration ce nt m Manag Manag Level ct
Manage Desk Manag Manag ement ement Manag Manag Capabil
User ment Profil ement ement Profile Profile ement ement ity
Role Profile e Profile Profile s s Profile Profile Words
system sysadmi sysa sysad sysad sysad sysad sysad sysad partial.k
admini n dmin min min min min min min ey
strator
SysAdm
in
SQLAd
min
SOAP
API
user.fav
orites
System Administrator
A user role defines a set of application profiles, capability words, and query groups that you can apply
to any operator record. For example, the self-service role enables the self-service user to open, view,
update, and close service requests.
2. Enter a User Role or click Search to select a role from a record list.
3. Add optional information to the form. If necessary, press Ctrl + H to view help for each field.
4. Click Add.
System Administrator
3. Click Search.
5. Click Delete.
System Administrator
System Administrator
Database access is a feature that gives you the ability to limit or grant access to database records,
such as contacts, company, and regions. You can add or modify the existing out-of-box database
access settings per user role or operator.
To set database access for a user role, follow the steps below:
c. The user role you initially selected is in the User Role field. If you want to add access to a
different user role than the one you selected, clear the field and click Fill to select a different
user role.
o Allow DB access: The user role specified is granted access to the table specified.
o Prohibit DB access: The user role specified is denied access to the table specified.
e. When access has been granted to a table, click Fill in the View Format field to select the
table view.
f. Click Add.
b. Double-click the Table Name of the existing database access record you want to modify.
d. Click Save.
7. Click OK.
System Administrator
Setting a MySM home page for a user role enables you to auto-fill operator records with a MySM home
page, along with the other default settings for the user role. If no MySM home page is set, the user sees
a To Do list upon login.
Note: Specifying a MySM home page in a user's operator record overrides the default To Do list
and menus for that operator when they log in using the web client, even if the flag for menus has
been set.
To set a MySM home page for a user role, follow the steps below:
3. Click Search.
7. Click Save.
Service Manager stores capability words in the capability table, which you can access by opening the
capability form in Database Manager, or by clicking System Administration > Ongoing
Maintenance > Capability Words. To limit access, choose a subordinate capability word. To grant a
broad range of permissions, choose a parent capability word, such as SQLAdmin or SysAdmin. If you
create your own capability words or modify the default permissions, you can use the JavaScript
functions checkPermission() and checkExclusivePermission() available in the script library to
determine if an operator has a particular capability word. You must use these functions to enforce the
capability word model.
Capability words
HP Service Manager provides a hierarchy of out-of-box capability words.
Primary
Capability subordinate Secondary subordinate Application Description
Primary
Capability subordinate Secondary subordinate Application Description
Primary
Capability subordinate Secondary subordinate Application Description
Primary
Capability subordinate Secondary subordinate Application Description
Primary
Capability subordinate Secondary subordinate Application Description
Primary
Capability subordinate Secondary subordinate Application Description
Primary
Capability subordinate Secondary subordinate Application Description
Primary
Capability subordinate Secondary subordinate Application Description
Primary
Capability subordinate Secondary subordinate Application Description
Primary
Capability subordinate Secondary subordinate Application Description
System Administrator
3. Click Add.
System Administrator
3. Click Search.
5. Click Delete.
System Administrator
3. Click Search.
Operator passwords
Passwords play a major part in controlling system security within HP Service Manager. To protect your
system from unauthorized access, you can require passwords for every operator.
A System Administrator can change any operator password. Users can also change their own
passwords, unless the System Administrator denies operators password modification privileges.
A System Administrator can also set password format restrictions and time limits from the System
Information Record. The System Administrator can set the following password options:
l Format requirements
System Administrator
Note: A System Administrator can both change and reset a user password. Changing an operator
password permanently changes the password. Resetting an operator password temporarily
changes the password until the operator next logs in at which time HP Service Manager prompts
the operator to change the password.
3. Click Search.
7. Click Save.
System Administrator
4. Click Save.
System Administrator
4. Click Save.
System Administrator
The Reset Operators Password option provides temporary passwords. However, when you reset an
operator password, HP Service Manager does not verify that the new password conforms to any of the
password standards that you can define in the company record.
1. Click System Administration > Base System Configuration > Miscellaneous > System
Information Record.
Password
reset
option Description
Prevent Select this option to remove Reset Operators Password from the More Actions
Pwd menu. You can still manually change operator passwords from the operator record.
Resets
Reset to Select this option to reset the operator password to the log-in name whenever an
User administrator chooses Reset Operators Password from the More Actions menu.
Name
Prompt for Select this option to display a dialog box where an administrator can enter a new
Value password whenever the administrator chooses Reset Operators Password from
the More Actions menu.
Reset to Select this option to reset an operator password to the value you type in the text
Value field whenever the administrator chooses Reset Operators Password from the
More Actions menu.
4. Click Save.
System Administrator
4. Click More or the More Actions icon, and then select Reset Operators Password.
When you reset an operator password, HP Service Manager does not verify that the new password
conforms to the password standards that you defined in the company record. Therefore, use the Reset
Operators Password option to provide only temporary passwords.
System Administrator
n Min Password Length: type the minimum number of characters a password can contain.
n Max Password Length: type the maximum number of characters a password can contain.
n Allow Alpha Characters: select this option to allow users to create passwords with
alphabetical characters.
n Allow Numeric Characters: select this option to allow users to create passwords with
numeric characters.
n Allow Symbolic Characters: select this option to allow users to create passwords with
symbolic characters.
Note: HP Service Manager prevents users from creating passwords that start with the
following symbolic characters: pound (#), equal sign (=), tilde (~), greater than (>), and less
than (<).
n Always Require a Password: select this option to require all users to have a password
defined in their operator record. This option is the only way to prevent users from having blank
passwords.
Caution: Users who currently have blank passwords defined in their operator record can
still log in until they are required to change their passwords.
n Require Alpha Chars: select this option to require users to create passwords that contain at
least one alphabetical character.
o Min Required: type the minimum number of alphabetical characters a password must
contain. This value must be a positive integer if you select the Require Alpha
Chars option.
n Require Mixed Case: select this option to require users to create passwords that contain both
upper case and lower case alphabetical characters.
n Require Non-Alpha Chars: select this option to require users to create passwords that
contain at least one numerical or symbolic character.
o Min Required: type the minimum number of numerical characters a password must
contain. This value must be a positive integer if you select the Require Non-Alpha
Chars option.
n Prohibit Space Character: select this option to prohibit users from creating passwords that
contain the space character.
4. Click Save.
Caution: The only way to prevent users from defining blank passwords is to select the Always
Require a Password option.
System Administrator
n Use Time Period: select this option to have passwords expire after a set time period.
o Max Pwd Lifetime: type the number of days, hours, minutes, and seconds before user
passwords expire.
Type the time period in the following format: Dayshours: minutes: seconds. For example, 4
03: 02: 01 expires user passwords after 4 days, 3 hours, 2 minutes, and 1 second.
n Use Number of Logins: select this option to have passwords expire after a set number of
user logins.
o Max before change: type the number of logins before user passwords expire.
n Notify by Email on Password Change: select this option to notify users by email whenever
another user, such as a System Administrator, changes their password.
4. Click Save.
System Administrator
n Use Time Period: select this option to have passwords expire after a set time period.
o Min Pwd Lifetime: type the number of days, hours, minutes, and seconds before user
passwords expire.
Type the time period in the following format: Dayshours: minutes: seconds. For example, 4
03: 02: 01 expires user passwords after 4 days, 3 hours, 2 minutes, and 1 second.
n Use Number of Logins: select this option to have passwords expire after a set number of
user logins.
o Min before change: type the number of logins before user passwords expire.
n Notify by Email on Password Change: select this option to notify users by email whenever
another user, such as a System Administrator, changes their password.
4. Click Save.
License tracking
HP Service Manager tracks floating and named licenses on the application level for reporting purposes.
The logon process determines which applications are authorized for each user, allocates a floating or
named license for the duration of the session, and records usage information in the stathistory file.
When the user logs out or ends the session, Service Manager deallocates the license. Because
Service Manager tracks the highest daily license usage for each application, administrators can use
this information to determine how many licenses are being used and when peak usage times occur.
They can enable or disable user license tracking at any time.
The license tracking feature tracks the named and floating licenses on an application basis. Service
Manager refreshes the license usage information whenever the user logs out, or the session terminates
by inactivity or administrator action.
Authorized applications
The following applications monitor licenses:
l Contract Management
l Change Management
l Incident Management
l Configuration Management
l Request Management
l Problem Management
l Service Desk
l Knowledge Management
The Database Administrator can enable and disable the application license tracking feature. Service
Manager applications contain logic to ensure license usage accuracy.
License types
There are two types of license: login license (named or floating, which just controls the initial login), and
the application license for individual module access.
License type Description
l Floating: Users are not on the Named user list for the application and they have
update capabilities.
l Named: Users are on the Named user list for the application and they have
update capabilities.
Login licenses are tightly controlled so that the product will not allow you to log in if you exceed your
login licenses. Application licenses are lightly controlled, and you can exceed the licenses with only a
warning message.
If the Named Application field in the operator record is empty and the operator logging in is a Named
user, the user will consume one named login license and floating licenses for application license. If the
Named Application field in the operator record is only filled with, for example, Incident Management, the
same user will consume one named login license, one floating license for each other
application/module, and one named license for the Incident Management application/module. In other
words, by default the Application Licenses are floating licenses regardless of whether the operator is a
named or floating user.
Login licensing has been separated from Module licensing to provide more flexibility. It is possible to
change the default behavior to ensure the Named user consumes a Named license, instead of a
Floating license for the Modules. To do so, follow the steps below:
2. Click the Login Profiles tab, add the Modules required for the Named user in the Named
Applications field.
Users who have update capabilities for any of the following fields in the Service Desk security profile
(smenv) will consume a Service Desk license:
New new
Close close
Update update
Users who have update capabilities for any of the following fields in the Change Management security
profile (cm3profile table) will consume a Change Management license when they log in:
New new
Update update
Reopen reopen
Users who have update capabilities for any of the following fields in the Configuration Management
security profile (icmenv) will consume a Configuration Management license:
New new
Delete delete
Update update
Users who have update capabilities for any of the following fields in the Incident Management security
profile (pmenv) will consume an Incident Management license:
New new
Close close
Update update
Inactivate inactivate
Reopen reopen
Users who have update capabilities for any of the following fields in the Knowledge Management
security profile (kmprofile) will consume a Knowledge Management license:
KCS I
Label Field Name in kmprofile
KCS II
Label Field Name in kmprofile
KCS III
Label Field Name in kmprofile
Admin
Label Field Name in kmprofile
Admin, continued
Label Field Name in kmprofile
Users who have update capabilities for any of the following fields in the Problem Management security
profile (rcenv) will consume a Problem Management license:
New new
Close close
Update update
Reopen reopen
New pmt.new
Close pmt.close
Update pmt.update
Reopen pmt.reopen
New kne.new
Close kne.close
Update kne.update
Reopen kne.reopen
Users who have update capabilities for any of the following fields in the Request Management security
profile (ocmprofile) will consume a Request Management license:
New new
Close close
Post post
Update update
Reopen reopen
Deny apprdis
Override approve.override
Retract apprun
Reeval approve.reeval
Approvals approvals
Reset approve.reset
Approve approve
Users who have update capabilities for any of the following fields in the Contract Management security
profile (ctenv) will consume a Contract Management license.
General Privileges
Label Field Name
Contracts
Label Field Name
Payments
Label Field Name
Contract Templates
Label Field Name
Asset Allocation
Label Field Name
Software Counters
Label Field Name
Users who have update capabilities for any of the following fields in the Service Level Management
security profile (slaprofile) will consume a Service Level Management license:
New sla.new
Delete sla.delete
Update sla.update
New slocat.new
Delete slocat.delete
Update slocat.update
New slor.new
Delete slor.delete
Update slor.update
New sloa.new
Delete sloa.delete
Update sloa.update
System Administrator
You must have administrative access to the database to perform this procedure.
1. Click System Administration > Base System Configuration > Miscellaneous > System
Information Record.
4. Click Save.
Named users
HP Service Manager uses the software license agreement, which provides for two types of licensed
users: named users and floating users.
Named users are users who are always authorized to log on to the Service Manager system when
either floating user licenses or named user licenses are available. Floating users are limited to a
maximum number of concurrent logins as defined by the floating user license. The Service Manager
license key password file encodes the number of named users and floating users in the system as
separate values. You can define as many named users as you want. If the number of named users
logged on exceeds the limit of named user licenses, the surplus named users consume floating
licenses to log on to the Service Manager system. Floating users also consume floating licenses when
they log on. If all of your floating licenses have been used, Service Manager denies access to any
additional unique floating users. Unique named users will still be able to log in if Named licenses are
available. If all named licenses and floating licenses are used, no additional unique users (named or
floating) will be able to connect.
System Administrator
You must have access to the HP Service Manager server to perform this procedure.
To determine the number of named users available, follow the steps below:
sm -reportlic
4. Press Enter.
Service Manager displays a report of your licensed features and your current usage. The Named Users
field lists the number of named users that are active and inactive on your system.
System Administrator
3. Click Search.
7. Click Save.
User for the application in the operator record or in the nameduser table.
Triggers keep the operator records and named user records synchronized. When you update the
named.modules field in the operator record, Service Manager also updates the respective named user
record.If you update a named user record; Service Manager updates the corresponding operator record.
System Administrator
To define named users for applications by using the Named Applications method, follow the steps
below:
3. Click Search.
6. In the Named Applications field, type or select the application for which you want to enable
operator access.
7. Click Save.
Note: If you want to grant access and update rights for multiple named users in a specific
application, you can do this using the Named User method in Database Manager.
To define named users for applications by using the Named User method, follow the steps below:
4. Click Search.
6. In the Named users field, type or select the operators to be assigned update rights for the
specified application.
7. Click Save.
System Administrator
You must have administrative access to the database to perform this procedure.
1. Click System Administration > Base System Configuration > Miscellaneous > System
Information Record.
4. Click Save.
Permanent License.
Server Quiesced State : Allow All Logins
100)
Scheduled Maintenance(HelpDesk) 0( 100) 0(
100)
RAD Compiler 0( 0) 0(
25)
Service Catalog 0( 100) 0(
0)
Change Management 0( 100) 1(
100)
Request Management 0( 100) 1(
100)
Service Level Management 0( 100) 0(
100)
Contract Management 0( 100) 0(
100)
Asset Contracts Management 0( 100) 1(
100)
Knowledge Management 0( 100) 1(
100)
Knowledge Management ESS 0( 100) 0(
0)
System Administrator
You must have administrative access to the server operating system to perform this procedure.
1. Change directories to the RUN folder of your HP Service Manager installation. For example, run
the following command on Windows:
sm -reportlic: 1
3. Press Enter.
Stathistory table
The stathistory table updates every time a user logs on to the system. A stathistory record tracks the
named and Floating licenses on an application basis.
The application creates a new stathistory record daily. If a stathistory record already exists, the record
updates. If one does not exist, the application creates a new record. The stathistory record names are:
Application name - named
Application name - Floating
For example, to search for floating license Configuration Management records, type:
Each stathistory record updates with the number of named or Floating licenses used at that moment.
The number updates only when it is greater than the number already in the table. This enables the
administrator to keep track of the highest number of licenses used at any time.
System Administrator
3. Click Search.
Self-service licenses
The number of licenses that are active depends on the number of users logged on who can access an
application to add or update records. Self-service users who initiate service requests through an
employee self-service (ess.do) portal do not consume a named or floating license for login, but may
consume an application license. For example, if you have the ability to approve changes, whenever you
log in to the ESS client, you consume a Change Management license. It does not matter if the only
thing you do while logged in to the ESS client is submit a new interaction or check interaction status,
you will consume a full Change Management license because you have the capability to approve a
change. If you also have approval capability for Request Management, you will consume an OCM
license even when logged in to ESS. Self-service users can log on to an ess.do URL to perform certain
activities (such as, searching the knowledgebase to find an answer or logging new interactions) without
contacting the Service Desk.
Users with privileges to log on to Service Desk (or other HP Service Manager applications) are power
users. They use a Windows client or a valid (non-ESS) Web client URL (index.do) and consume a
named or floating license. They can add, update, or delete records.
You can review the sm.log file for messages that specify when a user consumes a license.
Folder entitlement
Folder entitlement isolates company information in folders, ensuring that the right users have the right
access to sensitive company data. For example, a company that manages more than one organization
could create separate security folders for each organization. Users in organization A could be granted
access to Folder A and users in organization B could be granted access to Folder B. The information in
an organization is tied to a security folder when users open records, such as incident records.
Therefore, users in organization A could not access incidents, changes, or requests made by
organization B, and vice versa. When folder entitlement is enabled, a new field appears when users
open records. This field allows users to select the security folder, allowing them to tie the information in
the record to that security folder. Users outside the organization who have not been granted permission
to access the data in the folder cannot see the record. When users outside the organization search
incidents, changes, or requests, the records are not found.
In HP Service Manager, a System Administrator enables or disables folder entitlement. For more
information on enabling and disabling folder entitlement, see the related topics.
The available out-of-box company security folders on the Folder Entitlement tab are DEFAULT and
advantage. However, the System Administrator can add folders to meet your business needs.
For each security folder added, a System Administrator must grant permissions to a specific
application security profile, thereby granting permissions to all operators associated with that profile.
Permission settings are selected for operators based on roles that reflect their responsibilities. When
defining roles, each role displays a top level view for all folders. You can then click on each folder and
set rights on individual fields for a folder, or modify workgroups. If a user does not have specific rights
defined for a folder, the default rights from the user profile are assigned.
The System Administrator can set the default folder for an individual operator. This setting allows the
records opened by the operator to be automatically associated with the default security folder selected.
System Administrator
4. Click Save.
5. Click OK.
System Administrator
4. Click Save.
5. Click OK.
Folder entitlement has been disabled. There are no longer any security folders assigned to
operators.
System Administrator
1. From the System Navigator, click System Administration > Ongoing Maintenance > Security
Folders.
2. Type the name of the new folder in the Folder Name field.
4. Click Add.
5. Click OK.
1. From the System Navigator, click System Administration > Ongoing Maintenance > Security
Folders.
3. Select a folder from the list that most closely matches the new folder you want to add.
4. Type the new name of the folder in the Folder Name field.
6. Click Add.
Caution: Make sure that you do not click Save because doing so will replace the existing
folder with the new security folder you are attempting to add.
7. Click OK.
Delete a folder
Applies to User Roles:
System Administrator
1. From the System Navigator, click System Administration > Ongoing Maintenance > Security
Folders.
2. Type the folder name, or click Search to select the folder name from a record list.
4. Click OK.
Note: You cannot delete a folder that is currently in use. An error message displays if you attempt
to delete a folder that is in use.
System Administrator
The System Administrator can set the default folder for an individual operator. This setting allows the
records opened by the operator to be automatically associated with the default folder set in the operator
record.
To specify use of the default folder from the operator record, follow the steps below:
5. In the Default Folder field, select a security folder as the default folder for this operator.
6. Click Save.
7. Click OK.
The default folder selected will automatically be used the next time the operator opens a new
record.
System Administrator
To add folder permissions to a security profile in Change Management, follow the steps below:
2. Add optional search criteria, and then click Search to select a profile from the record list.
5. In the Default Rights tab, select the applicable default rights parameters for this profile.
Note: Click Add new folder to open the Add New Folder Rights wizard. Follow the
prompts to add a new folder. When you are done, the new folder displays in your available
Security Folders list.
7. Click Save.
8. Click OK.
System Administrator
To add folder permissions to a security profile in Configuration Management, follow the steps below:
2. Add optional search criteria, and then click Search to select a profile from the record list.
5. In the Default Rights tab, select the applicable default rights parameters for this profile.
Note: Click Add new folder to open the Add New Folder Rights wizard. Follow the
prompts to add a new folder. When you are done, the new folder displays in your available
Security Folders list.
7. Click Save.
8. Click OK.
System Administrator
To add folder permissions to a security profile in Incident Management, follow the steps below:
2. Add optional search criteria, and then click Search to select a profile from the record list.
5. In the Default Rights tab, select the applicable default rights parameters for this profile.
Note: Click Add new folder to open the Add New Folder Rights wizard. Follow the
prompts to add a new folder. When you are done, the new folder displays in your available
Security Folders list.
7. Click Save.
8. Click OK.
System Administrator
Folder entitlement must be enabled in the system information record before folder permissions can be
added.
To add folder permissions to a security profile in Problem Management, follow the steps below:
2. Add optional search criteria, and then click Search to select a profile from the record list.
5. In the Default Rights tab, select the applicable default rights parameters for this profile.
Note: Click Add new folder to open the Add New Folder Rights wizard. Follow the
prompts to add a new folder. When you are done, the new folder displays in your available
Security Folders list.
7. Click Save.
8. Click OK.
System Administrator
To add folder permissions to a security profile in Request Management, follow the steps below:
2. Add optional search criteria, and then click Search to select a profile from the record list.
5. In the Default Rights tab, select the applicable default rights parameters for this profile.
Note: Click Add new folder to open the Add New Folder Rights wizard. Follow the
prompts to add a new folder. When you are done, the new folder displays in your available
Security Folders list.
7. Click Save.
8. Click OK.
System Administrator
To add folder permissions to a security profile in Service Desk, follow the steps below:
2. Add optional search criteria, and then click Search to select a profile from the record list.
5. In the Default Rights tab, select the applicable default rights parameters for this profile.
Note: Click Add new folder to open the Add New Folder Rights wizard. Follow the
prompts to add a new folder. When you are done, the new folder displays in your available
Security Folders list.
7. Click Save.
8. Click OK.
System Administrator
To add folder permissions to a security profile in Service Level Management, follow the steps below:
2. Add optional search criteria, and then click Search to select a profile from the record list.
5. In the Default Rights tab, select the applicable default rights parameters for this profile.
Note: Click Add new folder to open the Add New Folder Rights wizard. Follow the
prompts to add a new folder. When you are done, the new folder displays in your available
Security Folders list.
7. Click Save.
8. Click OK.
By default, Service Manager uses a calendar with a 24-hour work day and a 7-day work week to
determine when alerts and notifications occur. In the default 24-hour, 7-day calendar, Service Manager
sends alerts and notifications without regard to operator work shifts. For example, if an operator
schedules a notification to occur in 6 hours, then Service Manager sends the notification after 6 hours
have passed regardless of whether any operator is present to receive it. A notification scheduled at
5:00 p.m. in the default calendar arrives at 11:00 p.m. the same day.
Using a custom calendar, however, the same 6-hour delay occurs only during the defined work
schedule. For example, a System Administrator can define an 8-hour work day lasting from 8:00 a.m. to
5:00 p.m., which includes a 1-hour break from 12:00 p.m. to 1:00 p.m. If an operator then schedules a
notification to occur 6 hours after 5:00 p.m., the notification actually occurs at 3:00 p.m. the next work
day, or 6 working hours after the notification start time.
System Administrators can create custom calendar records to use throughout Service Manager. The
caldutyhours table contains custom calendar records that a System Administrator can assign to
Service Manager activities:
l Vendor schedules
Holiday records
HP Service Manager includes out-of-box records for common holidays in the United States. To add a
holiday, you must create a new holiday record in the calholidays table and associate that holiday with a
group in calholtable.
Service Manager uses calholtable to organize holidays into different groups. For example, one group of
holidays might list all holidays observed in France. This group would include worldwide holidays like
Christmas and New Year's Day and those unique to France. A second group might also list the
worldwide holidays, but add those unique to North America.
Associated tables
Service Manager uses information in these tables:
System Administrator
Note: In ITIL best practices, a Configuration Administrator manages master data. In Service Manager,
however, only a System Administrator has rights to master data, because the master data is shared by
all Service Manager applications. You may need to contact a System Administrator to implement
master data changes or to request permission to perform this function.
After you validate that the data sets for a new master data record request meet your company's
specifications, you can add the master data record to Service Manager. For example, you may need to
add a master data record for a new company location or a new vendor.
For example, if you want to add a master data record for a new company location, click
Locations.
3. Click Add.
Create a data reconciliation report summarizing the data modifications and any reconciliation errors in
accordance with your company procedures.
Part of Workflow(s):
Configuration Administrator
Note: In ITIL best practices, a Configuration Administrator manages master data. In Service Manager,
however, only a System Administrator has rights to master data, because the master data is shared by
all Service Manager applications. You may need to contact a System Administrator to implement
master data changes or to request permission to perform this function.
After you validate that the data sets for a master data record delete request meet your company's
specifications, you can delete a master data record in Service Manager. For example, you may need to
delete a location record because the site was closed.
Warning: When you delete a master data record, it is possible that some configuration item records
will still include the old master data value. Before you delete master data records, HP recommends you
conduct a mass update to replace the master data value scheduled for deletion with the new approved
value. This prevents obsolete data from remaining in Service Manager CI records.
2. Double-click the master data category for the record you want to delete.
For example, if you need to delete a master data record for a user who is no longer with the
company, click Contacts.
5. Click Delete.
Note: When you delete the contact record, the corresponding operator record will also be deleted.
Part of Workflow(s):
Configuration Administrator
Note: In ITIL best practices, a Configuration Administrator manages master data. In Service Manager,
however, only a System Administrator has rights to master data, because the master data is shared by
all Service Manager applications. You may need to contact a System Administrator to implement
master data changes or to request permission to perform this function.
After you validate that the data sets for a master data record update request meet your company's
specifications, you can update the master data record in Service Manager. For example, you may need
to change the cost center for a department or change the status of a master data record to retired or
obsolete.
3. Click Search.
Service Manager returns a list of records matching your search request.
5. Specify the new master data information. If you need to change the status of the record to indicate
that it is retired or obsolete, update the record in accordance with your company procedures. For
example, your company procedures might instruct you to add the words retired or obsolete to the
record name.
6. Click Save.
Service Manager updates the master data record.
7. Search for related active configuration items to ensure that the record updates do not conflict with
the configuration administration.
System Administrator
3. Click Search.
4. Type the name of the new holiday group in the Holiday Group Name field.
5. Click Add.
On-call schedules
On-call schedules help managers or administrators determine whether they have enough resources on
call to cover all shifts for each day. The on-call schedule specifies who is to be notified, when, and the
notification method. An administrator must complete the On Call Information form to identify individual
operator or contact assignments before HP Service Manager can create an on-call schedule record.
At midnight, the problem background processor generates the on-call schedule for the next day. The
background processor uses information in these tables to produce the on-call schedule for the next 24
hours:
l oncallsched defines on call assignments, notification methods, and time zone variations.
Time zones
The On Call Information form has a time zone field where you can note deviations from the server time
zone for any operator. For example, consider this scenario:
l A European company has headquarters in London, where the corporate server is located.
l The company record specifies that Western European Time (WET) is the default time zone.
l Her manager notes that her Local Time in the on-call schedule form is Pacific Standard Time (PST).
l When her manager sends her to Chicago for two weeks of on-site customer support, the manager
makes an entry in the Exception Time Zone field that temporarily changes her location to Central
Standard Time (CST).
l When she returns to California, the manager removes this exception entry from the on-call schedule
form before Service Manager generates the next day's record.
l A European company has headquarters in London, where the corporate server is located.
l The company record specifies that Western European Time (WET) is the default time zone.
l Her manager notes that her Local Time in the On Call Information form is Pacific Standard Time
(PST).
l When her manager sends her to Chicago for two weeks of on-site customer support, the manager
makes an entry in the Exception Time Zone field that temporarily changes her location to Central
Standard Time (CST).
l When she returns to California, the manager removes this exception entry from the on-call schedule
form before HP Service Manager generates the next day's record.
Daily Schedule
Service Manager displays daily schedule information for regular on call dates and times using a relative
date and time format that is not dependent on a specific time zone. The relative time format is
dd hh:mm:ss. For example, the Servicedesk Agent always begins work at 8:00:00 and stops work at
17:00:00.
Exceptions
Service Manager displays on call exception dates and times using an absolute date and time format.
The absolute date and time are for the time zone specified in the On Call Information form. If you omit a
time zone, the default value is the time zone in the company record. The absolute time format is
mm/dd/yyyy hh:mm:ss. For example, Teresa Thompson worked in the Central time zone only one day.
She began work on 03/14/2009 08:00:00, and stopped work on 03/14/2009 at 17:00:00.
System Administrator
Daily Schedule tab Use this tab to type the schedule for each contact in the
group.
Start Type the time that the person starts being on call. Type the
Time time in the 24-hour time format. By default, HP Service
Manager treats a blank start time as equivalent to 00:00:00
or midnight.
End Time Type the time that the person ends being on call. Type the
time in the 24-hour time format. By default, Service Manager
treats a blank end time as equivalent to 23:59:59 or one
second until midnight.
Days of Type true for any day that the person is on call, and type
the week false for days the person in not on call. By default, Service
Manager treats a blank entry as false.
Notify Specify the name of the message class used to notify this
Method person.
Local Click the drop-down list to select the local time zone where
Time the contact resides. This is optional if all contacts are in the
Zone time zone specified in the company record.
Exceptions tab Use this tab to define alternative notification methods and
conditions during exception dates such as holidays and
vacations.
Start Type the date and time on which the exception schedule
Date begins. Type the time in the 24-hour time format. By default,
Service Manager treats a blank start time as equivalent to
00:00:00 or midnight.
End Date Type the date and time on which the exception schedule
ends. Type the time in the 24-hour time format. By default,
Service Manager treats a blank end time as equivalent to
23:59:59 or one second until midnight.
3. Click Add.
Work schedules
A work schedule defines the work hours for one or more operators. HP Service Manager can generate a
complex 24x7 schedule that spans multiple time zones, includes all shift and break information,
accommodates any regional shift to Daylight Savings time, and automatically accounts for local or
national holidays. Service Manager uses the following information to create a work schedule:
Service Manager uses work schedule information in various calculations. One of the more important
calculations is when to trigger an alert that an incident should escalate to the next level.
Work schedules can apply to a group, such as an assignment group, or to an individual named in the
operator or contacts table. When you create schedule records, start and stop times must not overlap,
and breaks must occur within the defined work shift.
System Administrator
Note: In ITIL best practices, a Configuration Administrator manages master data. In Service Manager,
however, only a System Administrator has rights to master data, because the master data is shared by
all Service Manager applications. You may need to contact a System Administrator to implement
master data changes or to request permission to perform this function.
After you validate that the data sets for a new master data record request meet your company's
specifications, you can add the master data record to Service Manager. For example, you may need to
add a master data record for a new company location or a new vendor.
For example, if you want to add a master data record for a new company location, click
Locations.
3. Click Add.
Create a data reconciliation report summarizing the data modifications and any reconciliation errors in
accordance with your company procedures.
Part of Workflow(s):
Configuration Administrator
Note: In ITIL best practices, a Configuration Administrator manages master data. In Service Manager,
however, only a System Administrator has rights to master data, because the master data is shared by
all Service Manager applications. You may need to contact a System Administrator to implement
master data changes or to request permission to perform this function.
After you validate that the data sets for a master data record delete request meet your company's
specifications, you can delete a master data record in Service Manager. For example, you may need to
delete a location record because the site was closed.
Warning: When you delete a master data record, it is possible that some configuration item records
will still include the old master data value. Before you delete master data records, HP recommends you
conduct a mass update to replace the master data value scheduled for deletion with the new approved
value. This prevents obsolete data from remaining in Service Manager CI records.
2. Double-click the master data category for the record you want to delete.
For example, if you need to delete a master data record for a user who is no longer with the
company, click Contacts.
5. Click Delete.
Note: When you delete the contact record, the corresponding operator record will also be deleted.
Part of Workflow(s):
Configuration Administrator
Note: In ITIL best practices, a Configuration Administrator manages master data. In Service Manager,
however, only a System Administrator has rights to master data, because the master data is shared by
all Service Manager applications. You may need to contact a System Administrator to implement
master data changes or to request permission to perform this function.
After you validate that the data sets for a master data record update request meet your company's
specifications, you can update the master data record in Service Manager. For example, you may need
to change the cost center for a department or change the status of a master data record to retired or
obsolete.
3. Click Search.
Service Manager returns a list of records matching your search request.
5. Specify the new master data information. If you need to change the status of the record to indicate
that it is retired or obsolete, update the record in accordance with your company procedures. For
example, your company procedures might instruct you to add the words retired or obsolete to the
record name.
6. Click Save.
Service Manager updates the master data record.
7. Search for related active configuration items to ensure that the record updates do not conflict with
the configuration administration.
l When an incident ticket changes status (for example, when an incident ticket changes from Open to
Pending status, or from Open to Closed status)
l When an operator edits an incident ticket and the System Administrator has enabled the Track
Operator Times option (for example, when an operator edits an incident ticket to add details or a
solution)
To track additional Service Manager conditions, you can manually start or stop a clock using the
following tools:
l Command line
l Macro
Clock example
The following example illustrates how Service Manager uses clocks to track the duration of each phase
of an incident ticket. In this example, the clocks total.time and pending.time track the elapsed time
that an incident ticket is open and pending, respectively.
System Administrator
n Type is the RAD application that the clock tracks. You can choose from the following types:
o Problem
o Downtime
o cm3r
o SLA
o Incident
n Char Key specifies the name of the application record that starts and stops the clock.
n Char Number specifies the numeric ID of the record that starts and stops the clock.
n Total displays the total time that the clock has been running.
n Closed Total displays the total time that the clock used when it was last run.
n Schedule is the name of the work schedule for the clock to use.
n Close Date displays the date and time when the clock stopped running.
n Start array specifies the dates and times for the clock to start.
n Stop array specifies the dates and times for the clock to stop.
3. Click Add.
System Administrator
To add a clock to track incident ticket status changes, follow the steps below:
3. Click Search.
5. Click Search.
n Start These Clocks: type the names of the clocks to start when an incident enters this status.
n Stop These Clocks: type the names of the clocks to stop when an incident enters this status.
n Start These Clocks: type the names of the clocks to start when an incident exits this status.
n Stop These Clocks: type the names of the clocks to stop when an incident exits this status.
9. Click Save.
System Administrator
You can track how long each operator edits an Incident ticket by enabling a tracking option in the
Incident Management environment.
1. Click System Administration > Ongoing Maintenance > Environment Records > Incident
Management Environment.
3. Click Save.
System Administrator
2. Click Add.
Field Description
Macro Type true, or a condition statement that evaluates to true or false, to determine
Condition when to run the macro
Field Description
Name This value describes the name of the clock where HP Service Manager stores duration
of information. This name must uniquely identify the clock.
Clock
n Select Fixed Key Field to type a specific clock name.
Field Description
Type This value describes the type of clock to start. Service Manager automatically places a
of value in this parameter based on your Macro Type selection.
Clock
n Select Fixed Key Field to type a specific clock type.
n problem
n downtime
n cm3r
n SLA
n incidents
Clock This value identifies the record, event, or object to track. This value must be unique
Key throughout Service Manager. For a record, you can type number in $L.new to enter
Field the unique ID associated with the record. Service Manager automatically places a
value in this parameter based on your Macro Type selection.
6. Click Save.
7. Click OK.
System Administrator
To start or stop a clock from format control, follow the steps below:
3. Click Search.
Name Type one of This value describes the type of clock to start. For Incident
the following Management clocks, type problem or SLA.
values:
n problem
n downtim
e
n cm3r
n SLA
n inciden
t
prompt Type the This value describes the name of the clock where HP Service
name of the Manager stores duration information. This name must only be unique
clock. within the format control.
query Type the This value identifies the record, event, or object for the clock to track.
Unique key This value must be unique throughout Service Manager. For a
for the clock record, you can type the value number in $file to enter the
to use. unique ID associated with the record.
string1 Type one of This value is only required if you are calling the
the following apm.stop.clock application. The value stop stops the clock named
values: in the format control. The value strobe forces the clock to
recalculate the clock's current running time.
n stop
n strobe
time1 Type the time This value determines when the clock stops or starts. To stop the
the clock is to clock at the current date and time, type tod().
stop or start.
8. Click Save.
System Administrator
3. Click Search.
The self-service feature provides a way for administrators to grant access to infrequent users, field
personnel, or any other user outside of the IT organization without consuming a user license. These
users need no special training or software. If users can connect to the Service Manager server using a
supported browser, they can open incidents or make service requests.
l View journal entries on the Journal Updates section when the administrator enables Journal
Updates in the Environment record
When the operator makes an update to an open self-service request, Service Desk hides the update
text from the self-service user. To show the update text to the self-service user, the operator must
select the Visible to Customer check box in the Activities section of the interaction form.
l Manually create an operator and contact record for a single self-service user
HP Service Manager has an out-of-box template record to assist you with this task.
l Create multiple self-service operators from a contact record list with a single operation
System Administrator
A user role defines a set of application profiles, capability words, and query groups that you can apply
to any operator record. For example, the self-service role enables the self-service user to open, view,
update, and close service requests.
2. Enter a User Role or click Search to select a role from a record list.
3. Add optional information to the form. If necessary, press Ctrl + H to view help for each field.
4. Click Add.
The self service out-of-box user role record lists thefollowing capability words:
l service desk
l svcCatEmployeeRequester
l service catalog
l change request
If you create self-service users manually, make sure that you include the applicable settings in the out-
of-box records.
System Administrator
A new self-service user requires an operator record and a contact record. Hewlett-Packard
recommends that you also create a user role for all self-service users. Alternatively, you can use the
out-of-box self-service user role record.
2. Specify information for the new contact that you want to create. The following fields are required
for a self-service user:
n Contact Name
n Full Name
n Email
HP Service Manager uses the email address as the user's Service Manager ID when it creates
the new operator record.
4. Click Add.
5. When the new contact record is created, click More or the More Actions icon, and then click
Create Operator.
6. Select Self Service User for the operator type, and then click Next.
7. Click Save.
8. Click OK.
Note: If you create the operator record manually, you can use the out-of-box template record
(Template_SelfService) to create a self-service user. If you choose this method, you must also
create a matching contact record.
3. Select Template_SelfService.
7. Click the Login/Contact Profiles tab and choose a resource type from the Resource Type list.
8. Click the Notification tab and in the Email Addr. field, type the self-service user's email address.
n Type the name of the Self Service Menu to display when the user logs on using a self-service
URL. The out-of-box menus are ESSSM and ESSM-Approval. ESSM-Approval provides the
Approval Request link to the Approval view on the self-service starting page for those users
with approval capability.
n Click the list to choose the Self Service Starting Page to display when the user logs on using
a self-service URL. For example, choose Submit a Request.
c. Click Add.
Note:
l The Service Manager ID field in the contact record must match the operator Login Name in the
operator record.
l If you choose the User Quick Add Utility, Service Manager prompts you to create the contact
record for the user if it does not exist.
System Administrator
To create a self-service user from an existing contact, follow the steps below:
4. Click More or the More Actions icon above the form of the contact record, and then click Create
Operator.
5. Select Self Service User for the operator type, and then click Next.
6. Click Save.
7. Click OK.
System Administrator
To create multiple self-service users from a contact list, follow the steps below:
3. Select the contacts for which you want to create self-service users.
4. Click More or the More Actions icon, and then select Mass Create Operators.
5. Select Self Service User for the operator type, and then click Next.
6. Click OK.
l They have a Service Desk profile that enables them to log on to Service Desk (or other HP Service
Manager applications) using the Windows client connection dialog or any valid Web client URL to
view, add, update, or delete records. For example, the user has a Service Desk profile that enables
the user to take service requests and provide services to a user community.
l They have a self-service profile that enables them to initiate service requests through a self-service
URL. For example, a self-service user can use this feature to request services.
The following table shows how a user can access Service Manager in self-service or power user mode.
URL Description
http: //server_name: port_ The standard Web client interface for self-service users. The
number/SM/ess.do viewrecordlist parameter is disabled.
http: //server_name: port_ The standard Web client interface for power users. Self-service mode
number/SM/index.do using the parameters set in the web.xml file.
http: //server_name: port_ The accessible Web client in self-service mode. The viewrecordlist
number/SM/accessible_ parameter is disabled because it does not conform to accessibility
ess.do requirements.
System Administrator
3. Click Search.
5. On the General tab, click Fill to choose a Service Profile, or click Find to modify the existing
profile.
For example, you can add desired self-service privileges, such as Open, Update, or Close to the
existing Service Profile.
6. Click the Self Service tab. Make sure that the operator record has these settings:
n Type the name of the Self Service Menu to display when the user logs on using a self-service
URL. The out-of-box menus are ESSSM and ESSM-Approval.
ESSM-Approval provides the Approval Request link to the Approval view on the self-service
Starting page for those users with approval capability.
n Click the list to choose the Self Service Starting Page when the user logs on by using a self-
service URL.
7. Click Save.
Note: The Login Name in the operator record must match the HP Service Manager ID in the
contact record.
Form
Record Content (if applicable) Description
Form
Record Content (if applicable) Description
System Administrator
2. In the Security tab, type a descriptive name in the Profile Name field. For example, type
ServiceDeskESS.
3. Select security profile rights for Service Desk self-service users when working with user
interactions. For example:
Security
profile
right Description
Update Choose one of the following to indicate when ESS users can update interactions:
Always, When assigned, or Never
Advanced If enabled, gives ESS users access to advanced search capabilities to query for
search information.
Lock on If enabled, locks tickets when displaying them on the screen for this profile. HP
display Service Manager locks the record regardless of whether the user is making
modifications, and no other users can display or modify the record. If disabled (set
to false), Service Manager sets an exclusive lock on a record only when a user is
modifying it; other users can display or modify the record.
5. Enable inbox settings for self-service users. For example, when set to true, the New thread:
View -> Edit setting keeps the inbox open after a member of this profile runs a search from that
inbox. Service Manager displays the record in a new window.
6. Click Add.
Self-service licenses
The number of licenses that are active depends on the number of users logged on who can access an
application to add or update records. Self-service users who initiate service requests through an
employee self-service (ess.do) portal do not consume a named or floating license for login, but may
consume an application license. For example, if you have the ability to approve changes, whenever you
log in to the ESS client, you consume a Change Management license. It does not matter if the only
thing you do while logged in to the ESS client is submit a new interaction or check interaction status,
you will consume a full Change Management license because you have the capability to approve a
change. If you also have approval capability for Request Management, you will consume an OCM
license even when logged in to ESS. Self-service users can log on to an ess.do URL to perform certain
activities (such as, searching the knowledgebase to find an answer or logging new interactions) without
contacting the Service Desk.
Users with privileges to log on to Service Desk (or other HP Service Manager applications) are power
users. They use a Windows client or a valid (non-ESS) Web client URL (index.do) and consume a
named or floating license. They can add, update, or delete records.
You can review the sm.log file for messages that specify when a user consumes a license.
User name Tasks
Employee user Uses self-service to make requests for self and on behalf of other
employees and managers.
Department Uses self-service to make requests for self and direct reports.
Manager
Example: a manager requests new computer systems for each software
developer in a group.
User name Tasks
Self-service tailoring
A System Administrator can modify the look and feel of self-service forms to reflect their corporate
branding by using the Forms Designer or by modifying the display options and menu selections.
However, a self-service user is not able to customize the self-service environment.
Because self-service is part of the Web tier, you can also customize the Web tier presentation to
include font changes, logos, graphics, or navigation pane alterations. Customizations can affect the top
header, navigation pane, or main page area.
System Administrator
You can customize the self-service interface by changing the menu and forms that HP Service
Manager displays to the user.
3. Click Search.
3. Click Search.
4. Click Design.
l View definition:
l Ownership specifies who is allowed to manage the view and who is allowed to manage the content
displayed by the view.
System administrators access the Views/Favorites function from the System Administration menu:
System Administration > Base System Configuration > Miscellaneous > Views/Favorites
Create a view
Applies to User roles:
System Administrator
You can create a view for one or more users to customize the default log-on view. For example, if a
group of users regularly searches on the same query, you can provide them with a shared query view
as their default whenever they log on to HP Service Manager.
This topic assumes that you are familiar with Service Manager table and field names.
2. Click New.
3. Select the Area to create the view in and then click Next.
4. Specify the name and type for the view you wish to create, and whether it is a system view or
personal view.
5. Select who the view will be available to, and then click Next:
n Everyone
n Selected Groups
n Selected Roles
a. Click Fields.
b. To add fields, select items from the table menu and click Add to List.
Note: If you select a field that has a link to another table, select from the secondary menu
to add fields you want in the view.
7. Select view properties for Group By, Sort By, Filter, and Autoformat as desired.
8. Click Finish.
After the system adds the view, you can provide additional information for the view definition
9. In the Audience tab, select an audience for the view and then click Save.
10. You can also update or add additional properties for the view with the View definitions, Query
definitions, and Ownership tabs.
System Administrator
When you want to expand the list of views in a queue, you can use the New View wizard. However, if
the table does not yet exist, you need to first configure the table as an object record. You can then add
the view to the table.
Note: These procedures use the kmdocument table as an example for configuring and adding a
Knowledge Documents view to a table.
To configure an object record for a new table, follow the steps below:
2. Type the file name (table name) in the File name field. For this example, type kmdocument.
3. In the Manage Queues tab, type an expression in the Manage condition field that evaluates to
true. For example, type lioption("Knowledge Management").
4. Create a form to be used to display the view. Type your entry in the Manage default view field.
For example, type Knowledge Documents.
5. Click Fill in the Manage display format field and choose inbox.view.
6. Click Add.
7. Log out of HP Service Manager, and then log back in. This enables the new object kmdocument
table that you configured to be added to the view list. You can now add the new view to the table.
3. Select an entry for Area (Knowledge Documents) and then click Next.
4. Type the name of the view in the Name field and then click Next.
5. Click Fields.
6. Select Title in the Knowledge Documents list entries and then click Add to List. The Title entry
appears in the Destination Fields box.
7. Click Finish. You receive a message that states the view record was added. You also see the
View Definition form to add additional properties to the view you created.
The view appears under Favorites and Dashboards in the navigation pane.
Delete a view
Applies to User roles:
System Administrator
System Administrator
You can add, delete, or change the order of fields in a system view. This topic assumes that you are
familiar with HP Service Manager table and field names.
Note: You can only change fields for views with a Table view type.
5. To add fields, select items from the table menu and click Add to List.
Note: If you select a field that has a link to another table, select from the secondary menu to
add fields you want in the view.
6. To delete fields, highlight the field you want to delete in the Destination Fields window and click
Remove Field.
7. To move a field location up, highlight the field you want to move in the Destination Fields window
and click Move Field Up.
8. To move a field location down, highlight the field you wan tot move in the Destination Fields
window and click Move Field Down.
9. Click Next.
System Administrator
5. Click Save.
6. Click OK.
Autoformatting
Autoformatting is part of a view in that it is a view that has been customized by a set of rules that
specify certain display conditions for records that satisfy the conditions. For example, you can create a
view that displays all incident records older than one week and then in that view create an
autoformatting rules that displays records as red if their urgency is critical.
System administrators access autoformatting by selecting Customize Current View from the More
Actions menu for a view or queue.
System Administrator
2. From the Queue menu, select Approval to open the Approval Queue.
3. Click More or the More Actions icon, and then Customize Current View.
e. In the next field, select a comparison value, such as a to establish the rule starts with the
letter a.
6. Click Next to view a list of current rule definitions. The Configure Autoformat Rules form opens.
n Move the order of rules up or down; the first in the order overrides the others
The records that match your rule criteria now display in the color selected for this rule.
System Administrator
2. From the Queue menu, select Approval to display the Approval Queue.
3. From the next Queue menu, select Incident to view the Incident queue.
4. From the View menu, select a view, such as Autoformat date view.
5. Click More or the More Actions icon, then Customize Current View.
6. Click Autoformat.
7. Select a rule to adjust the order of and click the Move Up or Move Down button to adjust the
order of the rule.
Note that the first rule in the order overrides all others in the record list.
System Administrator
2. From the Queue list, click Approval to open the Approval Queue.
3. From the next Queue menu, click Incident to view the Incident queue.
4. From the next View menu, select a view, such as Autoformat date view.
5. Click More or the More Actions icon, then Customize Current View.
8. In the name field, you can optionally change the name of the rule.
9. For the rule to be active, select the Is Active check box. For the rule to be inactive, clear the Is
Active check box.
10. In the Color field, you can optionally modify the color in which the rule appears in the queue by
using the color selections.
11. Optionally modify the field name by using the field selections.
12. In the Operator field, you can optionally modify the operator to use for this rule.
n On
n On or After
n On or Before
n Is Between
13. You can optionally modify the date in the date field by selecting a date using the calendar widget or
by manually typing in a new date.
16. From Specify View Type, select Save as a system view or Save as a personal view.
17. Click Finish to return to the Incident queue and view your changes.
System Administrator
1. From the System Navigator, click Service Desk > Interaction Queue.
2. From the Queue menu, select Approval to open the Approval Queue.
3. Click More or the More Actions icon, then Customize Current View.
System administrators can access Customize Current View from the More Actions menu on any of
the display views, queues, or record lists for any of the applications. The system provides a wizard to
configure the view properties.
l Detailed descriptions of the focus of each ITIL process and supporting module in Service Manager.
This includes the scope of the function or process, the goals, the roles and thus profiles typically
required to deliver the function and their responsibilities. This information is included in the help
server.
l Process diagrams that define the out-of-box process flows to deliver the function are included in the
help server.
l The screens, work flows, profiles and system logic is pre-defined in the Service Manager system to
deliver the functions as described in the help server.
Access Control
Authorized users can create, modify, and close tickets through the different HP Service Manager
modules. Access to functionality within each module is governed by Service Manager security utilities,
which define access based on role; for example, one user may be able to create and modify, but not
close, tickets.
Service Manager security utilities govern access to modules, functionality within modules, and
underlying data.
Mandatory Fields
HP Service Manager provides two basic methods for setting field-level controls including making a field
mandatory. The system provides two methods to indicate that a field is mandatory in the user interface.
If the field is only required to be mandatory on a screen-by-screen basis, the field can be set as
mandatory using the format control validations. This control can be visually indicated by a property in
Forms Designer.
If the field needs to be set as mandatory for all access points throughout the system, a data policy for
the field can be set using the supplied configuration tools. In this case the visual indication is
automatic.
On screen, Service Manager identifies mandatory fields with a red asterisk indicator.
Reporting
HP Service Manager includes two options for generating management reports using key performance
indicators: Service Manager Dashboard queries and charts, and Service Manager Crystal Reports.
These tools allow you to generate predefined and ad hoc reports to display any information. The
following describes these tools.
Service Manager has the ability to search almost any set of records to produce a list and then display
the results in either a bar or pie chart.
To create a chart, first create a query to display desired information; you can then convert query data
into a chart (bar and pie charts are supported) with one simple mouse click. You can save charts as
single objects, or in Dashboards; Dashboards are folders in which you can store multiple charts.
Dashboards show relationships among categories of data. For example, one chart might show the
number of Incidents by customer; another chart might show the number of Incidents by priority.
Viewing charts together as a Dashboard enables you to make better business decisions, such as
assigning resources to close Incidents.
Chart preferences enable you to customize your chart settings. Service Manager client controls the
chart refresh rate, and the server communicates the latest data to the client as needed. If no changes
occur, the latest data comes from the cache if caching is enabled. Charts do not rerun the query when
they check the server for updated information.
You can export chart data to Microsoft Excel or to an ASCII delimited file for use in any statistical
reporting package. In addition, you can cut and paste chart images into other documents.
For operational reporting or regularly scheduled reporting requirements, HP provides an OEM version of
Crystal Reports with Service Manager. HP also delivers over 40 predefined reports. You can run
reports on an ad hoc basis and system administrators can define an automatic report-generation
schedule using the Service Manager Report Scheduler tool. Crystal Reports 2008 is required to view,
generate, or modify these reports and is included with Service Manager.
n Escalated Interactions
n CI Relationships
n CI Summary
n Backlog of Incidents
n Reopened Incidents
In addition, you can perform a search within each module using different combinations of conditions,
and the search results can be presented in list or chart.
You can also create your own management reports using Crystal Report and build your reports on any
field in the database.
Management Reporting
HP IT Executive Scorecard
The HP IT Executive Scorecard is a key element in the HP IT Performance Suite and is a systematic
approach to digitizing the sensing, measuring, and instrumentation of the entire IT-controlled landscape
into single consolidated views for IT leaders and practitioners. The HP IT Performance Suite includes
comprehensive families of proven software for strategy, planning, and governance, application lifecycle
management, IT operations, information management, security intelligence, and risk management.
These solutions are unified by one of the most complete IT data models for collecting and relating data
feeds from individual products.
What makes the HP IT Performance Suite much more than just a collection of management software is
the HP IT Executive Scorecard—a single pane of glass that pulls all the information and analysis
together. In short, HP IT Executive Scorecard can help track performance and communicate in
business terms.
l Use a single pane of glass to view IT business services, programs, and financial status
l Show historical data to highlight improvements and identify negative trends early
l Automate and decrease effort required for the data-gathering process to enable real-time reporting
With its balanced scorecard, best-practice dashboards, and over 135 key performance indicators
already defined, the HP IT Executive Scorecard is a unique differentiator. The HP IT Executive
Scorecard is an analytical product that renders performance from a broad range of data sources,
including (but not limited to) HP Business Service Management, HP Service Manager, HP Asset
Manager, and HP Project and Portfolio Management.
From a business point of view, the need to control information technology (IT) is driving a new level of
maturity in performance management. Many organizations turn to executive scorecards to help drive
performance and more are now pouring this approach into the context of IT. The out-of-box Scorecards
in the HP IT Executive Scorecard are based around up to four high-level perspectives. These equate to
high-level goals of IT or the business. The four used in HP IT Executive Scorecard are: IT Value,
Customer, Operational Excellence, and Future Orientation.
The scoring of those objectives is based on one or more KPIs. In this way, the persona can gain a quick
view of overall performance in an area of interest and drill down further if required into the KPI or KPIs
that are responsible for the performance score.
KPIs reflect how well the organization is doing in areas that most impact financial measures valued by
shareholders, such as profitability and revenues.
A KPI evaluates the performance according to expectations. The context is provided using:
l Targets, which records the predefined gains, such as 10 percent new customers per quarter
l Benchmarks, which is based on industry wide measures or various methodologies, such as Six
Sigma
l Trend, which is the direction of the performance of the KPI, either Up, Down, or Static
A KPI is a Metric, but a Metric is not always a KPI. The key difference is that KPIs always reflect
strategic value drivers whereas Metrics represent the measurement of any business activity. Metrics
always show a number that reflects performance. KPIs put that performance in context. Metrics are not
matched against a threshold. An example of a metric could be an MTTR (mean time to recover) which
measures the average time between the occurrence of a set of incidents and their resolution. An
example of a KPI could be an MTTR, which measures the average time between the occurrence of a
set of incidents and their resolution, compared to a defined threshold. For example, MTTR less than
one hour.
The out-of-box KPIs can be altered to suit different personas or augmented by new KPIs created within
HP IT Executive Scorecard.
Audit Trail
For all records in HP Service Manager, a date time stamp and a user stamp are updated in the record
when it is created or saved.
Service Manager provides an audit trail capability that identifies each step taken in the resolution of a
ticket. Each time the ticket is updated (whether manually or automatically), a separate historical
activity is created for the ticket. An authorized user may review each historical activity to develop a
comprehensive understanding of the history of the record and its resolution, including which operators
took what actions at what times. These updates are displayed into an aggregated journal of all updates.
Service Manager also provides an auditing feature that records modifications to fields within the
Service Manager database. Field modifications are detected by comparing the fields in the original
version of a record to the updated version. When modifications are detected, an Audit Log entry is
recorded for each changed field showing the name of the modified field, the old and new version of the
data, the current date/time, and the current operator’s user ID.
Archiving
Closure of processed problems, incidents, changes, interactions, and other records is a standard part
of the workflow for each module. Typically, the closure action not only supports saving the record but
separate validations, rules, and possibly even separate forms to help ensure business success.
The most typical approach for archiving records is to leverage the chosen RDMS tools from Oracle, MS
SQL or DB2 to perform database administration for purging and archiving.
HP Service Manager provides an archive and purge tool that can be configured by table and criteria for
archiving. This is a facility only the administrator would use. This capability allows the ability to archive
either manually or on a scheduled basis.
One new capability in this area is the ability to take advantage of the HP archive tool suite. These tools
allow data to be archived out of Service Manager into a system-accessible file system. The production
or alternative instance of Service Manager can then be used to access these data records. See the link
below for additional details.
l Notifications
Service Manager provides a broad and deep solution to deliver notifications to stakeholders
whenever a record is opened, updated or closed. The notification engine allows administrators
complete control over the following:
l Alerts
Modules include the ability to set criteria for the generation of alerts. For example, the administrator
can set rules for three stages of alert and a deadline condition. When these targets are met,
specified users receive alerts and notifications through the Service Manager tool, email or via pager,
fax etc.
l Escalations
Business rules can be used to trigger automated escalations of tickets under various conditions.
Examples include: should the status remain unchanged for too long; the ticket reassigned too often
between assignment groups; or for other rules as defined. In addition, to document the violation of
these rules the administrator can configure Service Manager to act in certain ways should these
rules be breached. For example, if a ticket remains in open state for too long, reassign it to the
assigned user’s manager.
Alerts and escalations can be triggered through evaluation of Service levels as defined in the
Service Level Management module. This approach is used to set Service Level Objectives and
Service Level Agreements with associated actions should service levels approach breach
conditions. In this way, escalation is accomplished proactively to avoid breach rather than react to
breach.
Feedback on Application Setup help topics for printing (Service Manager 9.34)
If no email client is available, copy the information above to a new message in a web mail client, and
send your feedback to [email protected].