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.

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.

Hi John,

You made me think about it from an ISHRemote angle... the building block cmdlets are there, and if I would wrap them up it would be a Find-IShConditionValue cmdlet

1. Use Get-IShDocumentObjData as described above
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
4. Result is a ConditionValue object that actual returns the matched ConditionName and ConditionValue
   1. So a result could be a table looking like
   2. COOLING | AIR
   3. COOLING | WATER
   4. COOLING | FREON
   5. ENGINE | DIESEL
   6. ...
5. From there you can do what you want?

Best wishes,
Dave

PS: https://github.com/RWS/ISHRemote/issues/176 for crosslinking the idea