Using extended properties to search for workitems

Fredrik_Borchsenius

I have extended the ServiceRequest class with a few Booleans. Is there any way I can use those properties to search/filter workitems from the search window?

Conner_Wood

The general rule is to create a sealed MP of your class extension.  Then in another MP you reference the sealed MP and define a TypeProjection (in SCSM Console it's known as Combination Class) which will allow also having relationships to pull info from.

However if you just want a plain class, that is doable, you could create a new view in SCSM Console and Publish to Cireson Web Portal assuming that's what you want to use it for.  All the classes and properties in the Portal Search are hardcoded as far as I can tell, so you cannot use custom classes/properties when building criteria in the Portal.

Tom_Hendricks

Conner_Wood said:

... All the classes and properties in the Portal Search are hardcoded as far as I can tell, so you cannot use custom classes/properties when building criteria in the Portal.

That's the answer.  @Conner_Wood did a great job of explaining class extensions and type projections, but following that model will not (as he also says) make these properties available for searching.  This was also covered in another thread (https://community.cireson.com/discussion/comment/5327#Comment_5327) and I believe has been mentioned other times as well.

More importantly, perhaps, there is a feature request for this, which is getting a stunningly low number of votes, given how useful this would be:  https://community.cireson.com/discussion/182/search-on-extended-fields-in-service-request

Conner_Wood

The general rule is to create a sealed MP of your class extension.  Then in another MP you reference the sealed MP and define a TypeProjection (in SCSM Console it's known as Combination Class) which will allow also having relationships to pull info from.

However if you just want a plain class, that is doable, you could create a new view in SCSM Console and Publish to Cireson Web Portal assuming that's what you want to use it for.  All the classes and properties in the Portal Search are hardcoded as far as I can tell, so you cannot use custom classes/properties when building criteria in the Portal.

Tom_Hendricks

Conner_Wood said:

... All the classes and properties in the Portal Search are hardcoded as far as I can tell, so you cannot use custom classes/properties when building criteria in the Portal.

That's the answer.  @Conner_Wood did a great job of explaining class extensions and type projections, but following that model will not (as he also says) make these properties available for searching.  This was also covered in another thread (https://community.cireson.com/discussion/comment/5327#Comment_5327) and I believe has been mentioned other times as well.

More importantly, perhaps, there is a feature request for this, which is getting a stunningly low number of votes, given how useful this would be:  https://community.cireson.com/discussion/182/search-on-extended-fields-in-service-request