Hi Ann,

Our equivalent is the Publication Context (ishconditions). Within SDL Tridion Docs the publication context is stored on a version of the publication and used by any publication output which gets created from that version.

Populating/providing the publication context is done through the Conditions tabpage in the Publication Manager application while the publication version is loaded..

One difference between the ditaval and the publication context is that ditaval allows you to flag information which is not supported by publication context (ishconditions). The publication context will allow you to include/exclude information.

Kind Regards,

Raf

Hi Ann,

Our equivalent is the Publication Context (ishconditions). Within SDL Tridion Docs the publication context is stored on a version of the publication and used by any publication output which gets created from that version.

Populating/providing the publication context is done through the Conditions tabpage in the Publication Manager application while the publication version is loaded..

One difference between the ditaval and the publication context is that ditaval allows you to flag information which is not supported by publication context (ishconditions). The publication context will allow you to include/exclude information.

Kind Regards,

Raf

Hi Raf,

Thanks for your answer. I am conscious that the publication context is tied to a publication version. Is there any way of duplicating or reusing the condition config from a publication context within a different publication e.g. maybe a writer needs to create a new publication instance (not a version) but 99% of the condition rules from a pre-existing publication are relevant to the new one. Is there any way of reusing it?

Thanks again,

Ann

Hi Ann,

Out of the Box, the tooling is not supporting through a UI feature the copying of a publication context from one publication to the next.

However the API is able to do so. So you could write up your own process which would synchronize one publication context from one pubication to another publication.

You can retrieve the field FISHPUBCONTEXT as a metadata property of the publication version using an requested metaddata structure as shown below

<ishfields><ishfield name='FISHPUBCONTEXT' level='version'/></ishfields>

Once the value is retrieved you can update/set the same property on the other publication version objects using a metadata structure as shown below

<ishfields><ishfield name='FISHPUBCONTEXT' level='version'>value of the retrieved property</ishfield></ishfields>

Do keep in mind that the ISHRemote Powershell library is a wrapper around the API layer and can be used to implement this type of process.

Kind Regards,

Raf