E.2 Changes in version 12-50
-
For cases where JP1/Base is used for user authentication, Content Creator, a user who has permission to access an Operational Content as a creator (with the JP1 permission level HNP_Creator), was added.
Following this change, the following information was added or modified:
-
Procedure for adding the JP1 permission level HNP_Creator for Content Creators when a JP1/Base version earlier than 12-50 continues to be used without upgrading.
-
Operations that users with the JP1 permission level HNP_Creator can perform
-
Tasks required depending on whether plugins and custom windows are used
-
Setting access permissions for Operational Contents
-
Destinations of notifications when static files used in Operational Contents are stored in a directory on the web server
-
-
Users can now create Operational Contents for offline execution and configure them so that they can be executed in an offline environment. Additionally, JavaScript Plugins can now contain client-side JavaScript.
Following these changes, the following information was added:
-
Offline Plugin and Online Plugin
-
JavaScript Plugins that contain client-side JavaScript
-
Configuring Operational Contents to allow or disallow offline execution
-
Operation log and audit log for Operational Contents that are configured to allow offline execution
-
The ucnp.setup.server.cosminexus.ejbserver.session.timeout property (the default session timeout interval) in the user setup property file (ucnp_setup_user.properties)
-
-
Users can now add non-system default font families to the set of fonts that can be applied to resources in Operational Contents.
Following this change, the following information was added:
-
User style property file (ucnp_style_user.properties)
-
-
A note was added about the operation log of data within the scope of the upgrade.
-
The character encoding of the property files, except for the service property file, was changed to UTF-8.
Following this change, the following information was added:
-
Procedure for converting the character encoding of existing property files to UTF-8 when JP1/Navigation Platform is upgraded from a version earlier than 12-50 to 12-50 or later
-
-
Operational Contents can now belong to a hierarchical group.
Following this change, the following information was added:
-
A note about cases where JP1/Navigation Platform is upgraded from a version earlier than 12-50 to version 12-50 or later, and the names of groups to which Operational Contents belong include a backslash (\)
-
Specifying a hierarchical group with the ucnp.base.client.menu.group.default property (the default group name) in the user property file (ucnp_user.properties)
-
A note about importing Operational Contents that were exported from a JP1/Navigation Platform version earlier than 12-50
-
A note about the maximum name length of a group to which Operational Contents belong
-
-
For cases where a directory server (Active Directory) is used for user authentication, LDAPS is now supported as a server communication protocol.
Following this change, the following information was added or modified:
-
The ucnp.setup.server.ldap.protocol property (the communication protocol of the directory server) in the user setup property file (ucnp_setup_user.properties)
-
Unsetup procedure when using LDAPS
-
Procedure for restoring the entire system when using LDAPS
-
Procedure for changing uCosminexus Portal Framework settings
-
Setup procedure when using LDAPS
-
-
Google Chrome was added to the web browsers that can be used to access the Dashboard window from a machine.
A note was added about support for Windows(R) Internet Explorer(R) 11.
-
The maximum length of the installation directory path of Navigation Platform was changed from 60 characters to 40 characters.