Page 1 of 1

Profiling condition set: Binding to DITAVAL doesn't work for custom document type

Posted: Wed Apr 26, 2017 6:29 pm
by Frank Ralf
Hi,

When importing profiling attributes from a DITAVAL file oXygen creates an associated Profiling Condition Set that is bound to the DITAVAL file. In the Condition Set dialog, "Use DITAVAL File" is selected. However, when switching the Document type from "DITA*" to "My DITA*", the "Use DITAVAL file" field becomes deselected and greyed out.

I suppose this has something to do with our custom DITA framework which is based on oXygen 16.1. Could there be some Java library dependency missing?

Kind regards,
Frank

Re: Profiling condition set: Binding to DITAVAL doesn't work for custom document type

Posted: Wed Apr 26, 2017 7:49 pm
by Radu
Hi Frank,

Looks like a bug to me, I added an internal issue for it.
In the meantime you can define the profiling condition set on the *DITA* document type pattern, it should also cover you document type name,

Regards,
Radu

Re: Profiling condition set: Binding to DITAVAL doesn't work for custom document type

Posted: Tue May 02, 2017 5:14 pm
by Frank Ralf
Hi Radu,

Your workaround does work. Many thanks for the pointer.

Best regards,
Frank

Re: Profiling condition set: Binding to DITAVAL doesn't work for custom document type

Posted: Mon Oct 02, 2017 2:26 pm
by sorin_carbunaru
Hello Frank,

The recently released oXygen 19.1 has this issue fixed.

Regards,
Sorin Carbunaru
oXygen XML

Re: Profiling condition set: Binding to DITAVAL doesn't work for custom document type

Posted: Wed Oct 25, 2017 1:05 pm
by Frank Ralf
Thanks for the update!

Frank