Archive for the ‘PowerShell’ Category

#SCSM: Set Service Request Title from Related Request Offering

One of request that I got through my SCSM project is to create custom workflow to Set Service Request Title from Related Request Offering

The script use SMLets commands that you can download from

You can configure workflow using that script to trigger on new Service Request creation to copy title from related Request Offering

Import-Module SMLets  
$ServiceRequest = Get-SCSMObject -Class (Get-SCSMClass -Name System.WorkItem.ServiceRequest$) -Filter "ID -eq $ServiceRequestID"  
$GetRelatedRequestOffering = (Get-SCSMRelationshipObject -BySource $ServiceRequest | ?{$_.RelationshipID -eq "2730587f-3d88-a4e4-42d8-08cf94535a6e"}).TargetObject.DisplayName  
$GetServiceRequestTitle = $ServiceRequest.Title  $ServiceRequest | Set-SCSMObject -Property Title -Value "$GetRelatedRequestOffering"
Categories: PowerShell, SCSM Tags:

SCSM: Workflow to Assign Change Request Creator to Completed Needed Documentation

May 15, 2013 2 comments

All changes should be tracked in a change management system. The change is documented in the change tracking system when the change initiator has completed the required level of technical verification and completes a change request. The following status codes can be used to reflect the status of a change request:

  • Open: The change has been received and accepted but has not been assigned.
  • In-Progress: The change has been received, acknowledged, and assigned. Work is in progress to fulfill the change request.
  • Approved: The business and technical assessments have been completed and the change has been approved and committed to the change scheduler.
  • Rejected: The change has been rejected and will be routed back to the requester with an explanation and a recommended course of action.
  • Closed: The change request has been closed.
  • Canceled: The change request has been canceled.

The change initiator is the person who initially perceives the need for the change and develops, plans, and executes the steps necessary to meet the initial requirements for a Request for Change (RFC). A common task is when change request created by someone to assign first activity to him “Documentation” to be completed before proceeding with the change.

You can create different change request templates with different activities and identify “Documentation” as first manual activity task to be completed by change creator.

This Workflow will trigger on new Change Request creation and check  within the Change Request activities “Pre-defined template” for Manual activity with Name “Documentation”  and assign the Person who create the change to this manual activity to make sure that change initiator complete needed documentation before proceeding with the change request approvals

You can open the Workflow using Authoring tool and Change Manual Activity name  to fit with your organization requirements

You can download the workflow from there




%d bloggers like this: