Constraints using Sage X3 and Sage X3 People on same site

Sage X3 and Sage X3 People can be installed on the same site in different versions with respect of following constraints
* They are installed as separate solutions
* They can share the same Syracuse server, as endpoints of the same website (on different applications)
* The sitemap (navigation page), menu entries and authorings associated with each application are all delivered and installed with Syracuse server.
Therefore, to avoid disfunctions related to links definition or authorings, Sage X3 People and Sage X3 solutions must be updated to the version that match the menus and authorings delivered with Syracuse server.
For example, the update 8 of Syracuse server will be delivered with the sitemap and authoring of the Sage X3 update 8 sitemap, while the Sage X3 People version will use the corresponding update 7 elements.
We can then use a Sage X3 Update 8 solution with a Sage X3 People version 7 solution with the same Syracuse Update 8 server.
* On the same Syracuse server we can use different endpoints representing different solutions. However, all solutions of the same Application (Sage X3 or Sage X3 People) must be updated to the same version as they share the same authorings and links definitions.
For example it is possible to have two Sage X3 solutions in Update 8 but not one Sage X3 Version 7 and another Sage X3 Update 8.

As of Update 8, Sage X3 / Sage X3 People compatibility matrix is :

| Syracuse | Sage X3 | Sage X3 People |
| ------- | ------- | ------ |
| Version 7 | Version 7 | Version 7 |
| Update 8 | Update 8 | Version 7 |
| Update 9 | Update 9 | Update 9 |