system center service manager – extending work items … · service manger – xapity reference...

System Center Service Manager – Extending Work Items to Add

Custom Properties

www.xapity.com

Document Version 1.0

May 2016

http://www.xapity.com/

SERVICE MANGER – XAPITY REFERENCE GUIDE - EXTEND SCSM WORK ITEMS

Innovative Tools For Service Manager 2

This document contains information that may change without notice. It is provided to be

used as a guide only. While every effort has been made to ensure that the information

contained in this document is correct and up-to-date, Xapity accepts no responsibility or

liability to any party for any loss, damage, or disruption caused by errors, omissions,

completeness or suitability of the information.

This document can be used for internal and reference purposes. You cannot republish or

commercially exploit the document. Nor can you store it on any other website or other form

of electronic retrieval system without the written approval of Xapity.

©2016 XAPTY PTY LTD. All Rights Reserved.



System Center Service Manager –

Extending Work Items

Contents 1 Overview ............................................................................................................................. 5

1.1 Support Groups ........................................................................................................... 5

1.2 Service Manager Defaults ........................................................................................... 5

1.3 Names of Custom Support Group Lists ....................................................................... 5

2 Prerequisites for Service Manger Authoring Tool .............................................................. 6

2.1 Download the Authoring Tool ..................................................................................... 6

2.2 Authoring Tool documentation ................................................................................... 6

2.3 Signing Key to Seal Management Packs ...................................................................... 6

2.4 Planning ....................................................................................................................... 7

2.5 Support Group List Management................................................................................ 7

2.6 Windows Operating System Authoring Issues ............................................................ 8

2.7 Forms are not supported for customizations ............................................................. 9

3 Creating New Management Packs ................................................................................... 10

3.1 Create blank Management Packs .............................................................................. 10

4 Classes – Extend vs Inherit................................................................................................ 11

4.1 Classes ....................................................................................................................... 11

4.2 Extend vs Inherit ........................................................................................................ 11

5 Extend the Work Item Class ............................................................................................. 12

5.1 Extend the Work Item Class ...................................................................................... 12

5.2 Create the Property ................................................................................................... 13

5.3 Create Other Property Types .................................................................................... 16

5.4 Create a Relationship Property ................................................................................. 17

5.5 Mandatory Properties ............................................................................................... 18

5.6 Seal the Management Pack ....................................................................................... 19

6 Extend the Work Item Form ............................................................................................. 20

6.1 Copy Sealed Class Extension Management Pack to Authoring Tool ......................... 20

6.2 Extend the Work Item Form ...................................................................................... 20

6.3 Add the List Picker to the Form ................................................................................. 21



6.4 Relationship Controls on the Form ........................................................................... 23

6.5 Remove the Extensions Tab ...................................................................................... 23

6.6 Seal the Management Pack ....................................................................................... 25

7 Import the Management Packs ........................................................................................ 26

7.1 Import the Management Pack .................................................................................. 26

7.2 Create List Values ...................................................................................................... 27

8 Extending Other Work Items ............................................................................................ 28

9 Useful Links ....................................................................................................................... 31

10 Videos ............................................................................................................................... 32

11 About Xapity ..................................................................................................................... 33



1 Overview

This guide outlines how to extend System Center Service Manager Work Item Classes to add

custom properties and to extend a Work Item Form to display that property.

A practical example of adding a custom Support Group list to the Change Request Work

Item will be used to illustrate the steps involved. The steps will apply to any type of custom

property (string, Boolean, list, relationship, etc) that you may want to create for any Service

Manger Work Item.

This guide will give basic steps for form layout, but should be used in conjunction with the

“XRG - SCSM Authoring Tool - Form Layout Guide” to provide more detailed information and

tips on Form Layout.

1.1 Support Groups

Support Groups are a way of assigning Work Items to a team. By default, Microsoft has

configured Support Groups on Incident and Service Requests. The other Work Item types do

not have Support Groups and require extending the Class and Form to add them.

This guide will go through the process of adding a custom Support Group list to the Change

Request Work Item. The steps can be also applied to Problem, Release Record and Manual

Activity to allow Support Groups to be used with these Work Items.

Support Groups on the other Activity types – Review, Dependent, Sequential and Parallel

are of limited value in most situations. However, if your business requirements or processes

need Support Groups on these activities, you can apply the steps in this guide to extend

them.

1.2 Service Manager Defaults

Incident and Service Requests have built-in support for Support Groups. They use the

following built-in lists:

Incident: Incident Tier Queue list

Service Requests: Service Request Support Group

1.3 Names of Custom Support Group Lists

You can use any name for your Support Group lists. This guide will go through the steps to

create the following custom Support Group:

Change Request: Change Support Group list



2 Prerequisites for Service Manger Authoring Tool

2.1 Download the Authoring Tool

Download from: http://www.microsoft.com/en-au/download/details.aspx?id=40896

2.2 Authoring Tool documentation

How to install the Authoring Tool: https://technet.microsoft.com/en-

us/library/hh524302.aspx

Authoring for System Center 2012 - Service Manager

https://technet.microsoft.com/en-us/library/hh542404(v=sc.12).aspx

2.3 Signing Key to Seal Management Packs The extensions to the Work Item Class and Form will require a key to seal the Management

Pack. There are different ways of getting this key. As an example, the steps to use Visual

Studio to create a signing key are:

1. Open a Visual Studio Developer Command Prompt window (under Start -> All

Programs -> Visual Studio)

2. Create the key:

sn -k -keyname.snk

3. It is a good idea to create the public key in text format:

sn -p keyname.snk keynamePublic.snk

sn -tp keynamePublic.snk > keynamePublic.txt

See https://msdn.microsoft.com/en-us/library/aa560264.aspx for reference.

Tip: Read the XRG - SCSM Authoring Tool – Form Layout Guide. There are some quirks

and bugs, especially when designing the layout of forms.

http://www.microsoft.com/en-au/download/details.aspx?id=40896

https://technet.microsoft.com/en-us/library/hh524302.aspx



https://msdn.microsoft.com/en-us/library/aa560264.aspx



2.4 Planning

Having a clear plan of what each Management Pack will hold and a clear naming convention

for Management Packs will make transferring Management Packs between environments

easier and make backup and restore of Management Packs simpler. Plan out what you want

to accomplish and what Management Packs you will need.

This guide will create two Management Packs to hold the changes to the Work Item Class

and to the Work Item Form. This is recommended by Microsoft, but is not required. You can

store both changes in one Management Pack.

The advantage of having two Management Packs is that Form changes (usually more

frequent) can be made without changing the last modified date of every item associated

with the Management Pack. Changes to the Class Management Pack (i.e. adding properties)

will require an update to every item and thus the last modified date will change on every

item.

This guide will use the following Management Packs (the names are just examples and

should be changed to fit your requirements).

ChangeLists – to hold any values for lists associated with change items. For example, the

values that are placed in the Change Support Group list. Unsealed.

ChangeFormClassExtension – will hold the extension to the Change Request class. In this

guide, the new Support Group property custom list. Sealed.

ChangeFormFormExtension – will hold the extension to the Change Request base form. This

holds the changes to the original form to display the list box for the Support Group property

created in the class extension Management Pack. Sealed.

2.5 Support Group List Management

Support Group management can be difficult and there are two base approaches:

A list per Work Item: allows for flexibility where different Work Items use different lists. But

this will require more administrative overhead to manage multiple lists. A new Support

Group may need to be added to six different lists.

One master list (e.g. Incident Tier Queue or a custom list) for all Work Items. Not as flexible,

but it is easier to manage. A new Support Group only needs to be added to one list and it is

available for all Work Items.

The decision on which approach to take will depend on your business requirements

Tip: Microsoft recommend in the Authoring Guide documentation to split the Class

extensions and Form Layouts into two separate Management Pack.



2.6 Windows Operating System Authoring Issues

There are also errors on Windows 2012 relating to AeroLite. These can be ignored and they

do not affect the created or edited Management Packs, except for Problem.

The Service Manager Authoring Tool, at the time of writing, cannot extend the Problem

record on Windows 2012 R2 server. It is possible to do this on Windows 7, Windows 8.1 and

on Windows 2008 R2.

Example Scenario: The Change and Release areas have the same teams, so the

Support Groups will be exactly the same. One list can be bound to two different list

properties – one in the Change Request class and one in the Release Record class.

Updates to the list will be reflected in both forms.

But Problem management is only used by a subset of the Change\Release teams and

an additional number of teams. In this case a separate list for the Problem support

groups would be appropriate.

Tip: Combine some Work Items that share the same teams to use one list, like Change

and Release, and keep the other Work Items different, like Service Requests where

only a subset of teams process requests. There is no right or wrong way to configure

the lists, as it will depend on your business requirements and processes.

Figure 1: Error Extending Problem on Windows 2012



The use of different operating systems can also introduce problems with language locales.

Even with English, editing Management Packs on different OS’s can lead to some changes

being made under English US and other made under another English variant like UK or AU.

Editing of Management Packs should be done on a consistent Windows OS and with a

consistent language.

2.7 Forms are not supported for customizations

The following default forms are not officially supported for customizations: The problem form The user form The service map form The knowledge form

It is possible to extend them, but support from Microsoft may be limited.

Important Note: The official position from Microsoft is that modifying the Problem

Record class and User form are not supported. See the Authoring Guide release notes

https://technet.microsoft.com/en-us/library/hh524227(v=sc.12).aspx.



3 Creating New Management Packs

3.1 Create blank Management Packs

Depending on the planning decisions above you will need to create a number of

Management Packs. It is generally easier to create blank Management Packs in the

authoring tool to allow more control of the Management Pack name.

In this guide we will use a separate Support Group list for each Work Item and will create

two Management Packs to split the class and form extensions. Using Change as an example,

the following Management Packs will be created:

ChangeLists

ChangeFormFormExtension

ChangeFormClassExtension

Creating a new Management Pack in the Authoring Tool produces a shell and that will

contain no data. Creating them first in the Service Manager Authoring Tool allows you to

give a friendly name to each Management Pack.

Steps to create new Management Pack:

1. Open Service Manager

Authoring Tool

2. Click the new button or File

new

3. Change the name and save

Management Pack

4. Repeat these steps for each

of the Management Packs

listed above.

Tip: The Authoring Tool will probably crash intermittently after creating and saving

Management Packs. Save frequently and restart the Authoring Tool if you are starting

an important piece of work.

Figure 2: Create Management Pack



4 Classes – Extend vs Inherit

4.1 Classes A class is a set of objects that share characteristics, usually attributes and relationships. For

example, the Incident class has the properties and relationships related to incidents.

When customising Service Manager you can choose to extend or inherit from an existing

class or even create a new class.

4.2 Extend vs Inherit There is no right or wrong answer as it will always depend on your business requirements.

But think about it and do some research on what would be appropriate for your situation.

Extending a class – will add properties or relationships to an existing class. The practical

result is that all Work Items in that class have the properties regardless of whether they

need them or not.

This has positives, easier to create forms and reports. Also there are already lots of fields

that are not used in a class, a few more will not make a big difference. But it is messier and

potentially confusing to have fields that only relate to a subset of the entire class.

Inherit from class – creates a class that inherits all the properties of the parent and allows

you to add more. This is cleaner and allows you to have a custom form for the inherited

class, but is more complex to manage and may not be supported by third party extensions.

An example situation might involve a business area that must have a certain set of fields for

their business practices. You now have two options:

Extend – the fields are visible on the form for all business areas. Analysts use the

existing Work Item form and reporting is fairly straight forward.

Inherit – a new custom form is created that is only available to the business area. It

takes more effort to launch the form, reporting and the data warehouse need to be

updated. But it gives a custom result to the business area.



5 Extend the Work Item Class

Extending the class involves opening the appropriate blank Management Pack in the

Authoring Tool and then adding the Work Item class you wish to extend to it. This will create

a copy of the original class that was in a sealed Management Pack and by saving it to the

new blank unsealed Management Pack, as many properties (or fields) can be added as

needed.

Steps to extend the Change class

5.1 Extend the Work Item Class 1. Use the Authoring Tool to open the ChangeFormClassExtension Management Pack

2. In the Class Browser window (usually in lower right corner)

Change to All Management Packs

Search for “change”

Right Click on “Change Request “ and

select View

Figure 3: Change Request in Class Browser



3. This will open a read only copy of the change request

Expand Change Request

Right click -> choose Extend Class

Save the target Management Pack in ChangeClassExtension.

4. Save the Management Pack, just in case it decides to crash.

5.2 Create the Property

The Change Request class has been added to our ChangeClassExtension Management Pack

and now Properties (or fields) can be added to the change class.

Important Note: Do not create string values over 4000 chars or Rich Text data types

if you want the content to transfer into the Service Manager Data Warehouse.

Values or content of the new property will not flow to the Service Manager Data

Warehouse if the data type is Rich Text or a string value over 4,000 characters in

length.

This is a design decision of the product team and is not well documented. There is

no supported way around this. The only option is export data, recreate the fields

and import the data back in. The potential for data loss is high.

https://blogs.technet.microsoft.com/servicemanager/2010/12/01/class-property-

data-types-explained-in-detail/

Figure 4: Extend the Change Class



Create the Support Group list property

1. On the Extension of Change Request tab

2. Click Create Property

3. Type in a name for the property - ChangeSupportGroup (no spaces allowed)

Once created it is possible to give it a friendly display name with spaces

4. Click Create

Change the Display Name of the Property

To change the display name to a more readable

name (i.e. with spaces):

1. In the Details browser

2. Select the Name field

3. Type or edit the existing name

Tip: A property is initially created as a string value and then is converted into the data

type required.

Figure 5: Create new Property

Figure 6: Change the Display Name



Change the Property Data Type and Create a List

By default, the property was created as a string value and can now be changed to a list data

type.

1. Click on the property – it will probably be at the bottom of the list in the Extension

of Change Request tab.

2. Click on the Details pane and scroll up to the Data Type

Select List form the drop down box and hit enter (Select a List dialogue will then appear on

screen)

The Select a List dialogue box will pop up. It is possible to link the new custom property to

an existing list, such as Incident Tier Queue or to create a new list. By using an existing list, it

is possible for two custom lists on different Work Items to share the same values. See the

previous Section 2.4 Support Group List Management for more details.

Creating a new Change Support Group list will allow different lists between Work Items,

giving more flexibility between the different Work Items. But it will mean more

management overhead to manage two lists.

Create a New List

1. Click Create List

2. The Internal Name cannot have blanks: ChangeSupportGroup

3. The Display name can have blanks: Change Support Group

4. Add an optional description

5. Click Create

Figure 7: Change Data Type to List



5.3 Create Other Property Types

The following property types can be created:

Integer

Decimal

Double

String

Date Time

GUID

Bool

List

Rich Text

Binary

Only the list property has the extra steps described above, the others only require changing

the data type.

Tip: Only create a new list to keep each Work Item Support Group list independent of

each other. If combining Work Items to use the same Support Group list, select an

existing list from the available lists on the left.

Figure 8: Create New List



5.4 Create a Relationship Property

Creating a relationship property can be useful for some business processes. Using the

Change Support Group example, adding a Business Service relationship may be useful.

1. On the Extension of Change Request tab

2. Click Create Relationship

3. Type in a name for the relationship – BusinesService (no spaces allowed)

Once created it is possible to give it a friendly display name with spaces

4. Click Create

Change the Relationship Type

1. In the Details pane

2. Click Target Class

3. Select the object type, in this case Business Service

4. You can also set the friendly name (not shown in screen shot below)

Figure 9: Create Relationship Property



5.5 Mandatory Properties

To set a field to mandatory, go into the details pane on

the class extension and set the Required value to True.

Making the value mandatory by changing this value,

will not automatically display this property as mandatory

when used on a form which will be frustrating to

analysts – that is it does not have the red dot next to the

property.

Figure 10: Set Relationship to Business Service

Figure 11: Set as mandatory



5.6 Seal the Management Pack

To use this Management Pack in a production environment it should be sealed. Sealing a

Management Pack implements versioning and locks it from changes. Use the signing key

that was created in Visual Studio in the prerequisites section.

Seal the Management Pack using the signing key created in the prerequisites.

Figure 12: Seal the Management Pack



6 Extend the Work Item Form

Extending the Work Item form to add the new Support Group list, allows analysts to see and

edit the values added to the class.

This involves opening the appropriate blank Management Pack in the Authoring Tool and

then adding the Work Item form to it or adding the Work Item form to the existing

Management Pack used to extend the class.

Adding the Work Item form will create a copy of the original form that was in a sealed

Management Pack. By saving it in our new blank unsealed Management Pack items can be

added or removed from the form.

6.1 Copy Sealed Class Extension Management Pack to Authoring Tool

If you decided to split Management Packs for the class extension and the form, there is an

extra step required.

You need to copy the sealed class extension Management Pack (from the steps above) into

the Library folder of the Authoring Tool install directory. This allows the Authoring Tool to

read the information about the class extension and allows you to bind it to the list box

placed on the form.

6.2 Extend the Work Item Form

1. Use the Authoring Tool to open the ChangeFormExtension Management Pack

2. In the Form Browser window (usually in lower right corner)

Change to All Management Packs

Search for “Change”

Right Click on

Microsoft.EnterpriseManagement.ServiceManager.ChangeManagement.Forms

.ChangeRequestForm and select View

Figure 13: Choose the Change Form



3. This will open a read only copy of the Change Request

Expand Service Manger Change Management

Right click -> choose Customize or click Customize button.

Save the target Management Pack in ChangeClassExtension.

4. Optional: You may want to close the read only System Work Item Change Request

Library Management Pack.

6.3 Add the List Picker to the Form

Add elements to the form that has been copied into the unsealed Management Pack.

From the Form Customisation Toolbox you can

choose the controls to add.

For Support Groups add a List Picker.

It should be easy to drag the list picker on the form

and everything would be great. But the Authoring

Tool is not that simple.

Please refer to the XRG – SCSM Authoring Tool -

Form Layout Guide for more detailed information

on how to do this. This guide will give basic

instructions.

Figure 14: Customize the Form

Figure 15: Add List Picker to the Form



The basic steps are (using the Priority Stack Panel):

1. Drag a Label as the first item on to the

form and position it where you want it to

go.

2. Drag a List Picker item on to the form

3. Change the position and size of the items.

Label Settings List Picker Settings

Figure 16: Label and List Picker on Form

Figure 17: Label Settings Figure 18: List Picker Settings



This produces the result:

6.4 Relationship Controls on the Form

When adding a relationship to the form use the following controls:

User Picker – for any user based relationships

Single Instance Picker – for any other relationship

6.5 Remove the Extensions Tab

Extending the class creates a new tab on the form, the Extensions tab. This tab contains the

properties added to the class, but does not show relationships. And if you have added the

properties to the main form is not required. It can confuse analysts or just expose properties

that you did not want analysts to see or change.

Figure 17: Form updated with Support Group List

Figure 18: Extension Tab on Form



Removing the Extensions tab should be the last step before moving the form into

production. Preform all testing and validation of fields first.

The steps to remove the Extension tab from any Work Item are (using Incident as an

example):

1. Before sealing the Management Pack, open the XML file in an editor

2. Add the entire Admin Reference to the XML

References XML: <Reference Alias="Admin"> <ID>Microsoft.EnterpriseManagement.ServiceManager.UI.Administration</ID> <Version>7.5.3079.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference>

3. Add the example “HideFormExtensionTab” (your choice on name) Category line to

the XML

Categories XML: <Category ID="HideFormExtensionTab" Target="CustomForm_63369de5_0dbf_44ac_9996_b9cc9f529b8d" Value="Admin!Microsoft.EnterpriseManagement.ServiceManager.UI.Administration.Enumeration.HideExtensionTab" />

Note: The Form ID needs to be copied from the existing XML file (green highlight in

Form XML). You will find it in the Form section located just under the Categories

Section.

Forms XML: <Form ID="CustomForm_63369de5_0dbf_44ac_9996_b9cc9f529b8d" Accessibility="Public" Target="CustomForm_63369de5_0dbf_44ac_9996_b9cc9f529b8d_TypeProjection" BaseForm="Alias_8fcff993_a009_4752_a7ac_0678c17dd429!System.WorkItem.Incident.ConsoleForm" TypeName="Microsoft.EnterpriseManagement.ServiceManager.Incident.Forms.IncidentFormControl">

4. Save the XML

5. Open the Management Pack XML file in the Authoring Tool then seal it like normal

6. Import and confirm Extension tab is hidden



6.6 Seal the Management Pack

To use this Management Pack in a production environment it should be sealed. Sealing a

Management Pack implements versioning and locks it from changes.

Use the signing key that was created in Visual Studio in the prerequisites section.

Figure 19: Seal the Management Pack



7 Import the Management Packs

There are now two Management Packs (or one if you did not split them) that can be

imported into Service Manager. It is then possible to add values to the custom list for the

Support Group.

You should also import the unsealed Management Pack that will hold the values for the

custom list.

7.1 Import the Management Pack

Open Service Manager and navigate to Administration -> Management Packs.

1. Import the

ChangeFormFormExtension and

ChangeFormClassExtension sealed

Management Packs – extension *.mp.

Do not import the unsealed Management Pack – extension

*.xml.

2. Import the unsealed, MP files (*.xml), ChangeLists Management Pack created in

Section 3.1 Blank Management Packs.

This will be used to hold the values entered into the list.

Tip: Close the Service Manager console and open it again to reload the new

Management Packs

Figure 20: Import Management Pack

Figure 21: Choose .mp



7.2 Create List Values

Configure the newly created Change

Support Group list. Navigate to Library ->

Lists and search or scroll to find the new list

Change Support Groups.

The first time you edit the list you will be

asked for an unsealed Management Pack to

store the values in. Choose ChangeLists

from the drop down list.

Then Add Items to enter the change Support Group names.

Tip: The display order of Management Packs is by last modified date and is not

alphabetical. It can be hard to find the Management Pack at time, especially with a

long list

Tip: The list items do not display in alphabetical order - reorder then manually. It is also

not possible to move items between levels.

Figure 22: Choose Management Pack for List Values

Figure 23: Add list values



8 Extending Other Work Items

To add Support Groups to the other Work Items, you need to repeat this process for every

Work Item type. The screen shots below show the main Work Items and which Class or

Form is used for the extension.

Incident Work Item

Class: Incident

Form: System.WorkItem.Incident.ConsoleForm

Change Request Work Item

Class: Change Request

Form: Microsoft.EnterpriseManagement.ServiceManager.ChangeManagement.Forms.

ChangeRequestForm

Figure 24: Incident Class and Form

Figure 25: Change Class and Form



Release Record Work Item

Class: Release Record

Form:

Microsoft.EnterpriseManagement.ServiceManager.ReleaseManagement.Forms.ReleaseRec

ordForm

Service Request Work Item

Class: Service Request

Form:

Microsoft.EnterpriseManagement.ServiceManager.Applications.Forms.ServiceRequestForm

Figure 26: Release Record Class and Form

Figure 27: Service Request Class and Form



Problem Work Item

Class: Problem

Form: ServiceManager.ProblemManagementLibrary.Form.Problem

Manual Activity Class

Class: Manual Activity

Form:

Microsoft.EnterpriseManagement.ServiceManager.ActivityManager.Forms.ManualActivityF

orm

Figure 28: Problem Class and Form

Figure 29: Manual Activity Class and Form



9 Useful Links

Download Authoring Tool


How to install the Authoring Tool


Authoring for System Center 2012 - Service Manager


Classes: Customizing and Authoring


Extending the Service Request Form and Exposing the Request Offering Field in System

Center 2012: Service Manager

https://blogs.technet.microsoft.com/wincat/2013/03/11/extending-the-service-request-

form-and-exposing-the-request-offering-field-in-system-center-2012-service-manager/

In Defense of Class Extension vs. Inheritance

http://scsmmercenary.blogspot.com.au/2016/02/in-defense-of-class-extension-vs.html

XRG - SCSM Authoring Tool – Form Layout Guide

http://www.xapity.com/#!support/dc8c8

Xapity Blogs

http://www.xapity.com/#!blog/c146e

Tip: Read the reference “XRG –SCSM Authoring Tool – Form Layout Guide” to provide

more detailed information and tips on Form Layout.





https://blogs.technet.microsoft.com/wincat/2013/03/11/extending-the-service-request-form-and-exposing-the-request-offering-field-in-system-center-2012-service-manager/

https://blogs.technet.microsoft.com/wincat/2013/03/11/extending-the-service-request-form-and-exposing-the-request-offering-field-in-system-center-2012-service-manager/

http://scsmmercenary.blogspot.com.au/2016/02/in-defense-of-class-extension-vs.html

http://www.xapity.com/#!support/dc8c8

http://www.xapity.com/#!blog/c146e



10 Videos

We have created a companion set of videos that show the techniques outlined in this guide.

These can be viewed on the Xapity web site.

Videos Available:

Admin Series - Extending Work Items - Part 1 - Extend the Class

Admin Series - Extending Work Items - Part 2 - Form Layout

Admin Series - Extending Work Items - Part 3 - Hide Extension Tab

Admin Series - Extending Work Items - Part 4 - Grid Panels

Admin Series - Extending Work Items - Part 5 – Tabs and VIP



11 About Xapity

We are a small software development company based in Australia. We have been working

with Service Manager since 2012 and have come across gaps in the functionality that

customers needed for their business practices. The products we have launched fill existing

gaps and we are working on more to be released in the coming months.

The products are available for a download on a trial basis (fully functional for 30 days).

Download them and then let us know what you think. Our goal is to make tools that are

useful and practical.

www.xapity.com

http://www.xapity.com/

system center service manager – extending work items … · service manger – xapity reference...

Documents