Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Optional manual migration tasks
- Configure the Change Management module to use the new Task Planner
- Upgrade to the Process Designer related record subform
- Use the Process Designer workflow viewer in your forms
- Configure the Search form
- Migrate the solution matching configuration from security profiles to security settings
- Update reports to use Process Designer-based category tables
- Make the Category field in the Interaction form read-only
- Revert to using the "escalate to Change" wizard
- Remove the button in the Incident form that cancels the Interaction escalation process
- Migrate any customization of the knownerror table
- Remove the legacy Request Management dashboard and report definitions
- Enable legacy Request Management and Process Designer-based Request Fulfillment to run in parallel
Configure the Change Management module to use the new Task Planner
Note The following step applies only to customers who upgrade to Service Manager Hybrid from a 9.3x system that has PDCP3 or PDCP4 installed.
If you are upgrading to Service Manager 9.50 Hybrid from a Classic version of Service Manager, you must add the Task Planner form to your Change format, and then run the "Legacy change/task data to new taskplanner" data migration script, if you want to use the new Task Planner.
An improved version of the Task Planner was introduced in Service Manager 9.40. To use it, make sure that the following code elements are successfully implemented (this disables the previous version of the Task Planner). To do this, you can use conflict resolution or manually change the code elements according to following table.
Record type |
Record name |
Modifications |
Comments |
---|---|---|---|
Object |
changeModel |
Uses the "Change Model" workflow, the workflow location is "In Object," and the file-level rule sets are configured to use the new Task Planner. |
|
cm3t |
The following object-level rule sets are configured to use the new Task Planner:
|
|
|
Process |
changeModel.buildtable |
The following initial JavaScript is commented: |
This record was used by optionid 441 to save taskxml files to the changeModel table for the Classic Task Editor. |
Process |
changeModel.init |
The following initial JavaScript is commented: |
This record was used to initialize a taskxml file to be displayed by the Classic Task Editor. |
Process |
changeModel.save |
The following initial JavaScript is commented: |
This record was used to save taskxml files to the changeModel table. |
Process |
change.open.save |
|
|
Process |
change.update.save |
|
|
Process |
changePlan.buildtable |
|
This record is used by optionid 441 to save taskxml files into the changeModel table for the legacy Task Editor. |
ScriptLibrary |
ApplyChangeModel |
The following script is commented:
|
Additionally, you must check that the following code elements are correctly implemented before you use the new Task Planner. To do this, you can use conflict resolution or manually change the code elements according to following table.
Record type | Record name | Modifications | Comments |
---|---|---|---|
format | chm.cm3r.tasks.horz | The old Task Editor widget is replaced with the new Task Planner widget. | These are the out of box formats. Please customize your own formats accordingly if you are not using out of box formats. |
chm.task chm.standard.registration chm.standard.pln.sch chm.standard.execution chm.standard.pir chm.standard.backout chm.normal.registration chm.normal.rsk.imp chm.normal.tcab.approval chm.normal.build.test chm.normal.dcab.approval chm.normal.deployment chm.normal.backout chm.normal.pir chm.emergency.registration chm.emergency.rsk.imp chm.emergency.approval chm.emergency.build.test chm.emergency.implmt chm.emergency.backout chm.emergency.pir |
A new Task Context tab is added to dynamically display context-related record information that is planned during the task plan. | ||
Triggers |
trigger.name="trigger.changeModel.remove.taskplan" and table.name="changeModel" |
A new trigger is added to remove task plan-related information once a changeModel record is deleted. |
Update your customized formats
If you do not plan to use the out-of-box ChangeModel or Task formats, you must configure the Task Planner widget in your tailored ChangeModel and Task formats as described in the following table.
Task Planner property | Value in ChangeModel format | Value in Task format |
---|---|---|
Editor type | Model | Ticket |
Category | Category | Header/category |
ID | id | Header/number |
Editable | Yes | Yes |
Parent file | cm3r | cm3r |
Additionally, you must manually add the "Additional Properties" tab to the Change and Task details forms, in order to display the Additional Properties information for Changes and Tasks. To do this, manually add references to the following subformats in the relevant formats:
-
Change format
common.taskplan.parent.InputOutput.subform
-
Task format
common.taskplan.task.InputOutput.subform
Data migration
For more information about how to migrate your data, refer to Appendix B: Data migration.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-ITSM@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: