Looking for compatibility matrix for Publication manager, authoring bridge, condition manger and content importer for 15.1, is it backwards compatible? Where can I find this information?
Looking for compatibility matrix for Publication manager, authoring bridge, condition manger and content importer for 15.1, is it backwards compatible? Where can I find this information?
Hi Frank,
Thank you for that link, that is the one I was mentioning in my post title, this link no longer list Publication manager, authoring bridge, condition manager etc. Does this information still exist in documentation?
Hi Frank,
Thank you for that link, that is the one I was mentioning in my post title, this link no longer list Publication manager, authoring bridge, condition manager etc. Does this information still exist in documentation?
Hi Akheil,
I do see the client tools were listed in the version 14 documentation, but not in version 15. I can ask about this in our next engineering meeting.
When we release Tridion Docs we test and qualify with matching client tools and server versions. When we released version 15.0, we also released matching 15.0 client tools. When version 15.1 was released, we released matching 15.1 client tools. Only the matching client tools are tested and qualified for each release.
What we have done with some customers is when a newer version of the client tools has a feature or fix, they would like to leverage, we have used them, only if they are the same major version. As an example, 15.1 client tools should work fine on 15.0, the key word here is “should”. Where this combination is not tested and qualified it is use at your own risk. Engineering would also require any issue reported to them to be replicated on matching versions of software.
Version 15 client tools should not be used on previous major version such as version 14 SP4 and earlier.
Hi Frank,
Thank you for the clarification, we were towing with the idea of upgrading the Client tools first to 15.1 with Content Manager 14 SP3 and then running a second phase to upgrade content manager to 15.1. We had done something similar for user in the same major release, but the case is different here. Thanks for clarifying..