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	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Service Manager9.50

Integrate > HPE Application Lifecycle Management/Quality Center (ALM/QC) > Defects and Requirements Exchange with HPE Service Manager and HPE Application Lifecycle Management Installation and Administration Guide > Synchronization Concepts

Synchronization concepts

This chapter provides a detailed introduction to the following basic synchronization concepts.

SM Change -> QC/ALM Defect

When a business owner enters a change request in SM and marks the change “Forward as defect”, a defect is created in QC/ALM. This informs the QA personnel that they should begin the QA process.

During the QA process, key information is synchronized from QC/ALM to SM. The integration administrator has the responsibility of determining the key information and specifying the information in the field mapping (using the provided integration tool) in order for the business owner to view updated (scheduled) information in SM. The information includes the status of all changes in the testing cycle.
SM Change -> QC/ALM Requirement

The requirement synchronization feature of this integration allows requirements found during the change management process to be systematically tracked by SM and QC.

When a business owner enters a change request in SM and marks it as “Forward as requirement”, a requirement is created in QC/ALM. This informs the QA personnel that they should begin the QA process.

During the QA process, key information is synchronized from QC to SM. The integration administrator has the responsibility of determining the key information and specifying the information in the field mapping (using the provided integration tool). This allows the business owner to view updated (scheduled) information in SM
SM Problem -> QC/ALM Defect

After a problem is created, if the CPE engineer determines that there is bug with the problem after analyzing it, and the bug fixing work needs to be tracked, the CPE engineer triggers/initiates the creation of the QC CR ticket. When this problem is marked as “Synchronize with QC Defect”, a defect is created in QC/ALM.
QC/ALM Defect -> SM Problem

The business process for defect management in QC/ALM supports creation of known errors in SM based on information in QC/ALM. However, in the current solution, the integration can only create a problem in SM from a defect in QC/ALM. A user must create the known error in SM manually from the problem in SM. In non-PD environment, known errors are a source of information for informal knowledge articles in the Knowledge Base. In PD environment, known error is a problem record in a special category "known error".
SM Problem <-> QC/ALM Defect

This user story is a combination of SM Problem -> QC/ALM Defect and QC/ALM Defect -> SM Problem.

Send Help Center feedback