Hi Ann,

In all those years I cannot remember we had this request. Actually in Tridion Docs 14/14.0.x we deprecated ConditionManagement web services as the last of the API 1.0 generation. As a reminder from Tridion Developer Summit sessions, we in the mean while got an API 2.0, API 2.5 (used by ISHRemote) and are now working on a REST-based API 3.0. Besides becoming obsolete, the ConditionManagement 1.0 web services is quite clumpsy to work with as well, so I would avoid going there.

If you need a way forward, then I would advise you to look at ISHCONDITIONMANAGEMENT object, typically located under Repository folder System Management >  Conditions. In the end it is an object that complies with workflow, so if you do a checkout, alter the file and do a checkin operation you are actually mimicing what that earlier mentioned ConditionManagement web services does. If you made a mistake it is as easy as restore the last-known-good file you kept aside.

Your question is on our list for the upcoming Docs 15 release to describe the alternative of then obsolete Condition Management web services. And it will look similar to the rough flow I described higher.

Just to make sure ISHCONDITIONMANAGEMENT, the xml content of this object drives what you see and manage in the Condition Manager client tool. It also drives the Condition Builder feature to generate a complex ishcondition in Authoring Bridge. Nothing more.

If you automate, then a Get-IshDocumentObjData, update the xml and matching Set cmdlet could work nicely for you.

Best wishes,
Dave

PS: this is theoretical knowledge to get you going, I didn't have time to verify this is in some quick code... If you get it working, please share

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