Table of Contents

Change Management Solution

Niamh Ferns Updated by Niamh Ferns

Introduction

The Change Management PowerPlay solution provides an out-of-the-box solution for managing your control within your organisation.

Below, you'll find a demonstration of the Asset Manager Solution in action:

[LOOM NEEDED]

What does it do?

When you run into issues that require your team go through standard change control, whatever the priority, your engineers can then submit a form through the DeskDirector Client Portal.

This will log a formal change control request for your CAB (Change Approval Board) to review and accept or decline.

Deployment

In this section, we'll cover how to go through the deployment process for the Problem Management Solution.

For the deployment to work, you will need to deploy the solution library, then deploy either the ALM or self-service solution.

Solution Library Deployment

  1. Open your Admin Portal and head to Integrations > Solution Library.
  2. Select the Managed Solutions tab and open the Change Management solution:
  3. Select Deploy:
    On this page, you can also see a version history as well as a list of features that will be deployed.
  4. Follow the on-screen prompts to select a Queue/Board, Status, and Priority:
  5. Confirm by selecting Deploy. (This step can take some time to complete. Please do not close out of this page.)
  6. Confirm under Advanced > Events , Client Portal > Service Types, and Client Portal > Forms to make sure your assets have deployed correctly:

Solution Marketplace Deployment

  1. Head to the PowerPlay Marketplace and select Download Solution for the Change Management solution:
  2. Select Request ALM Deployment:
  3. Navigate to your open tickets on the DD4DD Support Portal, and you should see a ticket with a name similar to PowerPlay App Deployment Request: Change Management:
  4. Open the ticket and scroll down to the automated system comment. You should see that it has started the deployment for you:
  5. Once the deployment is finished, you will see an update on the ticket reporting that the deployment was successful
  6. To confirm, open Power Apps and navigate to the Solutions tab. Under managed, you should see a successful deployment for Change Management.
In this guide, we go through the steps with the ALM version of this solution. If you want to discuss the self-service version, please reach out to the DeskDirector support team.

Post-Deployment

SharePoint Site Creation

More info on SharePoint Sites.
  1. Navigate to your Active Sites in SharePoint under your tenant
  2. Click Create and Select a Team site, then use the standard template and fill out the Site's information:
    1. Name: Change Management
    2. Group email address: ChangeManagement
    3. Group owner: Admin for your tenant
    4. Privacy settings: Private - only members can access this site
  3. Add any members that should have access, and create the site as well as your service account
  4. In your SharePoint site, under Site contents, create a new blank list
  5. Name your list Change Management Notes and Documents and click Create
  6. Rename the default title column to Change Request ID, and create a new column with the name Notes set to the Multiple lines of text type with rich text enabled.
  7. Under the column settings, ensure that the Attachments column is enabled

Connection References & Environment Variables

In the above video demonstration, we configure the default value for each variable. Changing the default means that when new solution versions are released, the default value will be overwritten, meaning you will need to re-add these values after an update.

When you set your environment variables, please instead add a custom value and do not edit the default.
  1. If you don't already have one, create a SharePoint Connection in the Connections tab for your ServOrg environment
  2. Under your ServOrg environment, navigate to the Default Solution and open the Connection references tab in the Objects panel
  3. Search for CM and then update the following connection references:
    These will all reference the connections you configured in your ServOrg post-deployment.
    1. CM - Dataverse
    2. CM - DD Custom Connector
    3. CM - DeskDirector
    4. CM - Microsoft Teams
  4. Now, under the Environment variables tab in the Objects panel, update the following variables:
    If you are unsure what these variables should be set to, please reference the video above.
    1. Change Manager - Notes and Documents
    2. Change Manager SP Site
    3. CM - Change Management Request Form ID
    4. CM - Change Request Intake Queue ID
    5. CM - DD Change Admin ID
    6. CM - DeskDirector URL
    7. CM - Implemented Change Request Event ID
    8. CM - New Status ID
    9. CM - Priorities
    10. CM - Queues and Statuses
    11. CM - Risk Assessment Scores
    12. CM - Start Review Process Form ID
    13. CM - Submit a Change Request Service Type ID

Enabling Flows

  1. Under your ServOrg environment's Managed Solutions, navigate to the Change Management solution and open the Cloud flows tab in the Objects panel
  2. Enable the CM - [DD Event] - Status Change flow
  3. Enable the CM - [DD Event] - Start Change Review flow
  4. Enable the CM - [DD Forms] - Record Change Request Details flow
  5. Enable the CM - [Powerapps] - Change Manager Updates flow
  6. Enable the CM - [Powerapps] - Get DD Agents flow
  7. Enable the CM - [Powerapps] - Schedule CAB Change Request Discussion flow
  8. Enable the CM - [Powerapps] - Update Ticket Queue and Status flow
  9. Enable the Change Management - Cancel Request (Child) and Change Management - Create Ticket Fan-out (Child) flow
  10. Enable the [Dataverse] Change Management - Create Main Tickets flow
  11. Lastly, enable the [PowerApps] Change Management - Cancel Request flow

Running Manual Flows

  1. Navigate back to your Change Management Solution under your ServOrg's Managed Solutions, and then open the Cloud flows tab under the Objects panel
  2. Perform a manual run of the following flows in order:
    1. CM [Manual] - Queues and Statuses in DD
    2. CM [Manual] - Setup Priorities and Risk Score Mappings
  3. Under the Tables tab in the Objects panel, open the ITSM Config IDs table and copy the ID for the New ↔️ priority
  4. Under the Environment variables tab in the Objects panel, update the CM - New Status ID variable to the status ID you just copied
  5. Load back into your ITSM Config IDs table and validate that your priorities show a high, low, and medium priority. You will need to map these to the desired priorities in your Tokity instance. (See the video above if you're unsure how to do this.)

Service Orchestrator App Registration

  1. Navigate back to your Managed Solutions in your ServOrg and open the Change Management Solution, then open the Apps tab in the object Panel. From here, you can share the Change Management Portal app with the users who will need access
  2. Under the Details tab, copy the app's weblink and then play the Change Management app
  3. Load in the Admin Configuration pane and confirm that your board, status, and priority configurations show as expected.
  4. Back in your ServOrg's Managed Solutions, open the Service-Orchestrator-Library and play the Service Orchestrator app
  5. Open the Configuration Details and paste your web link into the Change Management Playbook URL field

How did we do?

Asset Manager Solution

HR Joiners Solution

Contact