Dear all,
I noticed that when you save a component with Pipeline Pilot 2017 the component and protocols get saved as ppxml file. We are currently setting up a development environment with a PP 2017R2 server. When I tried to deploy a package created on a 2017R2 server on a 9.5 or 9.1 server I couldn't install it at all just because the extension ppxml isn't recognized. However, by simply renaming the ppxml extension to xml, installation proceeded successfully on a 9.5 server.
What are recommended practices here? Is there any backwards compatibility foreseen or not at all?
Thanks
Peter
I noticed that when you save a component with Pipeline Pilot 2017 the component and protocols get saved as ppxml file. We are currently setting up a development environment with a PP 2017R2 server. When I tried to deploy a package created on a 2017R2 server on a 9.5 or 9.1 server I couldn't install it at all just because the extension ppxml isn't recognized. However, by simply renaming the ppxml extension to xml, installation proceeded successfully on a 9.5 server.
What are recommended practices here? Is there any backwards compatibility foreseen or not at all?
Thanks
Peter
