You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Use Get-IShDocumentObjData to retrieve the xml of the latest ISHCONDITIONMANAGEMENT object under System area
Load the resulting Condition Management xml (it holds all the data you see in Condition Manager)
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)
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.
The text was updated successfully, but these errors were encountered:
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
The building block cmdlets are there, and if I would wrap them up it would be a
Find-IShConditionValue
cmdletISHCONDITIONMANAGEMENT
object under System areaIShConditionValue
object (becomes a table row)So a result could be a table rendering denormalized Condition Name/Value combinations looking like
From there you can do what you want? Push them in a UI, or have them in an Excel file? Or...
Note
The text was updated successfully, but these errors were encountered: