Add cmdlet Find-IshConditionValue returning denormalized Condition Name/Value combinations

[ddemeyer]

Quick drop from my personal notes to share an idea on community.rws.com... inspired by https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/45257/can-condition-manager-data-be-manipulated-via-ishremote/160303?focus=true

We would actually have a use case for ISHRemote and condition management, too. We use a lot of conditions, and the lack of a search function in Condition Manager/Condition Builder makes it very difficult to find existing conditions. The ability to pull and search the master list via ISHRemote would at least fill the gap until RWS adds search to Condition Manager.

The building block cmdlets are there, and if I would wrap them up it would be a Find-IShConditionValue cmdlet

1. Use Get-IShDocumentObjData to retrieve the xml of the latest ISHCONDITIONMANAGEMENT object under System area
2. Load the resulting Condition Management xml (it holds all the data you see in Condition Manager)
3. Find-IShConditionValue -Filter ThisCouldBeAnyConditionNameOrConditionValue or perhaps two filters. These are in the end XPath select expressions on the Xml, you would to find matching xml nodes to convert to some IShConditionValue object (becomes a table row)
4. Result is a ConditionValue object that actual returns the matched ConditionName and ConditionValue and perhaps some other meaningful data?

So a result could be a table rendering denormalized Condition Name/Value combinations looking like

ConditionName	ConditionValue	Anything else?
COOLING	AIR	?
COOLING	WATER	?
COOLING	FREON	?
ENGINE	DIESEL	?

From there you can do what you want? Push them in a UI, or have them in an Excel file? Or...

Note

• There is no intention for an Add- or Set- or Remove cmdlet. Only a read-only operation.