As you start to build your service catalogue in SCSM, and the number of Request Offerings grow and grow, the need for additional properties to store data also grows.

For example, if you take my Create Announcement request offering (RO) example, there are six questions asked in order for the workflow to create the announcement.  All the answers to these questions will need to be mapped to properties in the RO, and by default there are a very limited of fields to which you can map data to.

As there aren’t the properties available to map the RO data to, the SR class needs to be extended to provide the required properties.  What usually happens at this point, in my experience, is that the class extensions are created and named specifically for the purpose of the RO.  If a question was being asked, such as “What’s the Title of the Announcement?” then a extended property will be created for “AnnouncementTitle”.

While this approach works, there is a problem with it.  The problem is that as the number of RO’s grows, so does the number of extended properties until you are suddenly dealing with hundreds of extensions.

To be more efficient, what I recommend is creating a set of generic class extensions that can be used by any of the request offerings.  As I recommend it, I created an MP that contains the following generic extensions:

  • 10 String properties
  • 5 Boolean properties
  • 3 Date properties
  • 3 Integer properties
  • 1 Decimal property
  • 5 Long String properties



These extensions should cover most of your request offering needs 🙂

The management pack (both sealed and unsealed versions) can be downloaded from the TechNet Gallery at