A.2 Changes in version 12-50
-
In the Operational Content Execution Window and the Operational Content Editing Window, users can now set a hierarchical group to which Operational Contents belong. Additionally, in the Operational Content Editing Window, users can now change the groups of multiple Operational Contents to the same group (or integrate groups) at once.
Following these changes, the following information was added or modified:
-
A description of how to handle a group name specified in the Member group name text box in the Add Operational Content window and the Copy Operational Content window, if the name includes two consecutive backslashes (\\)
-
A description of how hierarchical groups are displayed in the View Lists tab in the menu area of the Operational Content Execution Window and the Operational Content Editing Window
-
The Change Groups and Integrate Groups menu items in the menu area of the Operational Content Editing Window
-
The Execution settings tab in the Operational Content Settings window
-
-
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:
-
Tasks that Content Creators perform in a flow from creating to publishing Operational Contents
-
JP1 resource groups that appear in the Add Operational Content window and the Copy Operational Content window when a Content Creator logs in
-
JP1 resource group check boxes that can be selected in the Resource Settings window when a Content Creator logs in
-
-
The Store label information too. check box was added to the Attribute Settings windows for check box parts and radio button parts. This check box is used to specify whether to connect the displayed string and the value with a linefeed code (\r\n) and store them as a cache value.
-
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:
-
A note about JavaScript Plugin parts that contain client-side JavaScript
-
The Execute in the browser check box in the Attribute settings window (JavaScript Plugin part)
-
Setting the default value of the input parameter in the Attribute Settings window (JavaScript Plugin part)
-
A note about whether to select the Execute in the browser check box in the Attribute Settings window (JavaScript Plugin part) when the JavaScript Plugin parts use JavaScript API provided by Navigation Platform
-
Information about whether each method of JavaScriptPluginManager (JavaScript Plugin Manager class) can be used in JavaScript that runs on a web browser (on the client-side)
-
A note about the return value of the getParam method
-
A note about the methods of RestClient (REST caller class)
-
-
Automatic Operation Service Execution Plugin parts now can accept property values including a linefeed (\n) or tab (\t).
Following this change, the following information was modified:
-
Unacceptable characters for the Property Value text box in the Attribute Settings window
Additionally, a description indicating that properties with the data type of composite cannot be used was removed.
-
-
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 design and layout of the Dashboard window were changed. Additionally, the following specifications were changed:
-
A menu icon was added at the upper left of the Select Dashboard window to display commands to navigate between the windows of the Dashboard window.
-
A change was made so that clicking on a graph can allow setting filters for values on the horizontal axis or the vertical axis (when the axis is color-coded).
-