Collaborations & Updated Versions

[DEWright_CA]

If you build a collaboration between 2 systems, both are 11.3, then you update both to 11.5. Should you break the collaboration and reconnect them so they reflect the the updated versions?

I have a couple different systems between Secured and Public facing with different controlled collaborations and even though they were built out at 11.1, then upgrade to 11.3, and now 11.5; they show 11.3 as the build.

[RyanUthoff]

As long as the collaborations are still functional, I don’t see any reason to redo the collaborations unless you really want them to reflect the correct version.

I know restarts are a part of upgrading Portal, but it might be worth restarting both Portals and then initiating a manual collaboration sync if you haven’t done that already. I encountered an instance where an existing collaboration would not detect a new workspace that was created until Portal was restarted, even after doing manual syncs.

[DEWright_CA]

I have a couple that are failing to sync, but I am thinking I need to update certs on both ends also; so will take that step first.