Home > PowerShell, SCSM > SCSM: Workflow to Assign Change Request Creator to Completed Needed Documentation

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

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

 

 

 

Advertisements
  1. July 11, 2013 at 2:17 am

    I just tried this with SP1 and the latest SMLets. It does not work. I was able to use your script within the workflow and create a task to do this, but for automation there may need to be some adjustments.

    The Get-SCSMObject is returning null because it isn’t attaching to the classes properly.

    Try using the ManagedTypeID (GUID) and instead when referencing the class since these are constants. Here is the Query for SQL to get them… Run it against the ServiceManager DB.

    For WorkItem Class:
    Select TypeName, ManagedTypeId from ManagedType where TypeName like ‘System.WorkItem%’ order by TypeName

    For RelationshipTypeClass:
    Select RelationshipTypeName,RelationshipTypeId FROM RelationshipType Where RelationshipTypeName like ‘System.WorkItem%’ order by RelationshipTypeName

    Let me know if you would like for me to share the script and instructions for creating the task within the console.

    • Mohamed Fawzi
      July 11, 2013 at 10:19 am

      Sure, I tested that one for SCSM 2012 with SP1, Would be great if you can share your solution

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: