Known limits and issues with Sage X3 People v7.1
Last update of this list: June 17th 2014
The 'Business Intelligence' feature is not available with release 7.1 (before patch 5).
Workaround:None. The full feature and the Sage Business Objects component for version 7 will be provided with patch list 5.
When connected to the web "Syracuse" server in a language other than English, some terms on the user interface for technical functionalities may still be displayed in English.
Workaround:None. Depending on the language selected, texts and messages in the technical layer may not be exhaustively translated. However, translation will be completed along with further patch lists.
Errors can occur during folder generation if the folder contains inactive modules, other than the Manufacturing module.
Workaround:Activate all the modules when generating a folder. This constraint does not apply to the Manufacturing module, which can be disabled.
When connected to the web "Syracuse" server on the 'X3' endpoint, some error messages can be observed on the header panel when navigating through the different entries of the Home Page section.
Workaround:None. These error messages are normal because the X3 endpoint does not contain any business application data feeding the requests in the home page entries. These error messages will be filtered in a future patch list.
On a client machine, when using simultaneous browser instances (or tabs) on different endpoints for a web "Syracuse" server, a 'refresh' action (F5) on the current instance will automatically change the endpoint with the one used in the last connected instance.
Workaround:Do not perform a 'refresh' action when using different browser instances on different endpoints for a Web "Syracuse" server. The unexpected endpoint change in this context will be controlled in a future patch list.
When a user exits the application by closing the browser, the web "Syracuse" session will remain on the server until time-out (around 20mn). This will result in unnecessary allocation of memory on the server side for this session, and potentially consumption of a licence badge until time-out.
Workaround:It is recommended to always exit the application by clicking the 'Log out' icon. In a future patch list, a warning message will be displayed when a user tries to exit the application by closing the browser.
You cannot add a non-standard legislation or language (for example, Arabic, Danish, and so forth) in a child folder definition. This restriction results from a control preventing the addition of legislations and languages, which are not present in the non-modifiable X3 (root folder) definition.
Workaround:This restriction will be removed in a future patch list. Meanwhile, you can contact Customer Support for a 'hotfix' (R&D ticket #100929).
You cannot specify a custom legislation or language in a child folder definition. This restriction results from a control in the licensing system, preventing the addition of legislations and languages not referenced in the license file.
Workaround:This restriction will be removed in a future patch list, and it will be possible to add custom legislations and languages beginning with character 'Y'. Meanwhile, you can contact Customer Support for a 'hotfix' (R&D ticket #100929).
When connected to the application in the Polish language, you cannot access functions in 'classic mode'. The error message: "Can't retrieve session shared resources on web server. Your session will be closed." displays because of a json file generation issue in this context.
Workaround:A fix for this issue will be added in patch list 5. Meanwhile, you can contact Customer Support for a 'hotfix' (R&D ticket #100837).
The uninstallation of a local documentation server can fail. The error message: "java.lang.OutOfMemoryError: GC overhead limit exceeded" displays because of a java memory limitation with iZpack.
Workaround:None. This issue will be resolved with a future delivery of the documentation server setup program, shipped with a future patch list.