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 |
|
Review and Close Change (process ST 2.5)
After a change is completed, the results must be reported for evaluation to those responsible for managing changes, and then presented for stakeholder agreement. This process includes the closing of related user interactions, incidents, and known errors. The Change Owner and Change Manager review the change implementation and close it if successful.
Post-implementation review of the change (or PIR) is performed to confirm the following:
- The change meets its objectives
- The change Requester and stakeholders are satisfied with the results
- Unanticipated effects have been avoided.
- Lessons learned are incorporated in future changes.
By default, an Emergency Change or a Normal Change requires PIR, while a Standard Change does not.
Details for this process can be seen in the following figure and table.
Process ID |
Procedure or Decision |
Description |
Role |
---|---|---|---|
ST 2.5.1 |
Review RFC for Success |
The Change Owner checks whether the RFC deployed by Release and Deployment Management process is successful. |
Change Owner |
ST 2.5.2 |
RFC Successful? |
If the release is successful, it is handed over to the support staff. If the release is unsuccessful, it is subject to a Post-Implementation Review (PIR). |
Change Owner |
ST 2.5.3 |
Conduct Formal Turnover to Support |
The Change Owner ensures that all the functionality changes are documented and performs the tasks required to hand over the change to the support staff. |
Change Owner |
ST 2.5.4 |
Perform PIR |
The Change Owner and Change Manager perform a Post-Implementation Review (PIR) to ensure that the change is reviewed and lessons learned from the change are implemented. |
Change Owner |
ST 2.5.5 |
Notify Requestor of Change Results |
The Change Requestor is notified of the success or failure of the change. |
Change Owner |
ST 2.5.6 |
Reject RFC |
The Change Coordinator rejects the RFC. |
Change Coordinator |
ST 2.5.7 |
Close RFC |
The Change Requestor is notified of the success or failure of the change. |
Change Owner |