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 |
|
Release and Deployment Management process overview
The Release and Deployment Management process includes activities necessary to control releases to service assets and configuration items across the entire service lifecycle. It provides standard methods and procedures to use when implementing all releases.
The purpose of Release and Deployment Management is to ensure that:
- Releases follow a set process
- Appropriate users are notified at key points in the process
- Progress of a release is monitored and notification are issued if deadlines are missed
- Releases are supported throughout a simple or complex lifecycle
Release types
Release and Deployment Management includes three release types: Emergency, Major, and Minor. All three release types utilize the Release Management category and workflow in the Change Management module. Additional categories and workflows can be created if required. The steps of the workflow are represented by the phases and tasks within the phase. Service Manager requires that every release has a category and phase, but tasks are optional.
Release phases and transitions
Service Manager uses phases to describe the steps necessary to complete a release. The phase also determine the release screens users see, the approvals required to advance to the next phase, and the conditions that cause the system to issue notification and alerts. Each phase has workflow transitions that control how the release record will move through the workflow. When the work for a given phase has been completed the user will advance it to the next phase. If the release has encountered a failure condition then the release may be move back to an earlier phase for rework or abandoned.
Release tasks
Release Management utilizes tasks to capture work that is necessary for the overall release. This is work in addition to the Change specific tasks that are required to complete the changes that are associated to the release. Examples of required release activities are: determining if funding is available to support the release, arranging for required contracts and licenses, building and delivering training, evaluating the financial impact of the planned release, and performing knowledge transfer after the release has been deployed. Release Models can be used to pre-define task plans for Releases.
Integration with Change Management
In Service Manager the Release record and workflow control the overall process of the release, including approvals for the release and the release specific activities (tasks) that need to be complete. The release is related to multiple change requests (RFCs) that have their own workflow, approvals, and tasks. The planning, assessment, build, and deployment of each change is tracked and worked in the Change Management module. The Release provides the higher level oversight and provides visibility into the Change Management process through the Related Records section in the release record.
Release roles
The following table describes the responsibilities of the Release and Deployment Management user roles.