{"id":41862,"date":"2018-11-01T13:37:56","date_gmt":"2018-11-01T05:37:56","guid":{"rendered":"http:\/\/localhost\/help\/?page_id=41862"},"modified":"2026-08-13T22:33:59","modified_gmt":"2026-08-13T14:33:59","slug":"explorer-release-4-6-4","status":"publish","type":"page","link":"https:\/\/oihelp.corporate.ifs.com\/help\/p2-explorer\/explorer-releases\/explorer-release-4-6-4\/","title":{"rendered":"Explorer Release 4.6.4"},"content":{"rendered":"\n

\"P2_RGB<\/p>\n

P2 Explorer 4.6 consolidates what was previously three installers into one. It also combines the three separate databases of P2 Server, P2 Explorer, and P2 Security into a single database.\u00a0<\/p>\n

This release introduces the concept of the Info Zone \u2013 an area on the right side of the Explorer screen which displays context-sensitive information in a new Explore<\/em> panel. This takes the concept of the \u201cTable of Contents\u201d in previous releases of Explorer, to the next level. For this release, comments and display information will appear in this zone, with more to come in future releases.<\/p>\n

P2 Explorer version 4.6.4 is a patch release, with new features including a rich text editor, clickable images, new line styles in the trend, and a new Action Button component.<\/p>\n

Rich Text for Commentary and Case Management<\/h2>\n

Text fields in Explorer\u2019s display mode can now be edited with a Rich Text Editor control.<\/p>\n

For example, a case\u2019s Description or Commentary (on a page or in the Explore Panel) can have a bold<\/strong> or italic<\/em> font, have different font sizes, or be given a different colour.<\/p>\n

\"\"<\/a><\/p>\n

Likewise, comments on an Explorer page, or in the Explore Panel, can be highlighted in this way, as can Knowledge Management and Commentary, for a display, or from an Info Button on a page.<\/p>\n

In some of the text areas (such as Commentary fields, and Comments), the Rich Text Editor is initially hidden but appears when some text is selected. Other text areas (such as a Case description), have the Rich Text Editor always on display.<\/p>\n

\"\"<\/a><\/p>\n

Read more: Case Management<\/a>, Using Comments for Collaboration<\/a><\/p>\n

Rename Workspaces<\/h2>\n

Users who have the Workspaces<\/strong> Edit<\/strong> privilege (this is also inherited from the Explorer<\/strong> Admin<\/strong> module privilege) can rename public Explorer workspaces.<\/p>\n

Workspace names must still be unique, and private workspaces (i.e. My Workspace<\/em>) cannot be renamed.<\/p>\n

To rename a workspace, first click the Settings<\/strong> button in the Workspace, and then the Rename<\/strong> button.<\/p>\n

\"\"<\/a><\/p>\n

Type in the new workspace name, and then click the Rename<\/strong> button at the bottom of the dialog box.<\/p>\n

\"\"<\/a><\/p>\n

Read more: Explorer Workspaces<\/a><\/p>\n

New Line Styles on the Trend<\/h2>\n

There are three new line styles available for traces in the Explorer trend: Dashed Line (---<\/strong>), Dotted Line (\u2026.<\/strong>) and Dash-Dotted Line (._._._<\/strong>). This addresses customer issue 372733.<\/p>\n

The style picker on the trend now has a total of eight different styles to select from:<\/p>\n

\"\"<\/a><\/p>\n

Read more: Trend Trace Table<\/a><\/p>\n

New Component: Action Button<\/h2>\n

P2 Explorer now allows you to add a button to a page that can be configured to change the status of a case.<\/p>\n

The Case ID is passed to this component from a page variable, which the user can select (from, for example, a Combo Box), or which they can update by typing into a Text Input component.<\/p>\n

When the user clicks the Action Button, the selected Case ID is updated to the Case Status selected for the component (such as Investigating<\/em> or Closed<\/em>).<\/p>\n

After the button is clicked, a message appears to confirm that the action has been completed: \u2018Update Successful\u2019. If the Case ID does not exist, an error message appears.<\/p>\n

An Action Button can have 3 states:<\/p>\n

Disabled<\/strong>: The button will be disabled if no default value has been specified and the user has not specified a Case ID, or the if the input case ID is not a number.<\/p>\n

\"\"<\/a><\/p>\n

Enabled<\/strong>: The button will be enabled when a valid default has been specified, or if the user inputs a number for the Case ID.<\/p>\n

\"\"<\/a><\/p>\n

Hover<\/strong>: When a user hovers the cursor over an enabled button, the hover state is enabled. The button can be designed to show a different colour when the user hovers over it.<\/p>\n

\"\"<\/a><\/p>\n

In Design Mode<\/strong>:<\/p>\n

In Explorer Studio, the Action Button component has been added to the Control group in the Toolbox.<\/p>\n\n\n\n
\"\"<\/a><\/td>\n\"\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

In design mode, the page designer specifies the text that appears on the button (e.g. Close Case<\/strong>), the variable that stores the Case ID, and what the status should be for the target case.<\/p>\n

In this release, there is a single Action Type available for this component, called Set Case Status<\/strong>, which allows users to update the status of a case.<\/p>\n

The variable storing the Case ID should be a Number<\/em> type, and can also be specified using Page Defaults.<\/p>\n

Style designers can change the font size, family, colour, weight, and case for the button\u2019s label. For the button itself, the border\u2019s radius, colour, width and style, can be changed, as well the background colour of the button in both the normal state and the hovered state.<\/p>\n

Read more: Configuring an Action Button<\/a><\/p>\n

Clickable Images<\/h2>\n

In this release, images can be made clickable by adding a Link Action in the image component itself, rather than having to add a hotspot over the image.\"\"<\/a><\/p>\n

This means that images can now be configured to be interactive. For example: a user clicks on an image, and an Explorer page opens in a new tab.<\/p>\n

Images on existing pages will not have a Link Action selected, however a Link Action can be applied after an upgrade to this version.<\/p>\n

Available Link Actions are:<\/p>\n

Open Page<\/strong>:\u00a0Opens the specified Explorer page. Variables can be mapped from the current page to the destination page.<\/p>\n

Open Trend<\/strong>:\u00a0Opens the specified Explorer trend. Variables can be mapped from the current page to the trend.<\/p>\n

Open URL<\/strong>:\u00a0Opens the specified URL. Variables can be mapped from the current page to the URL.<\/p>\n

New Trend<\/strong>:\u00a0Opens a new Explorer trend. Variables can be mapped from the current page to the new trend.<\/p>\n

Set Variables<\/strong>:\u00a0Sets page variables to specified fixed values or variables, when the image is clicked.<\/p>\n

Read more: Configuring Images<\/a><\/p>\n

Adaptive Raw Sample Method on Pages<\/h2>\n

The Adaptive Raw sample method, introduced for Trends in version 4.5.4, is now available on Explorer pages as well. The Adaptive Raw sample method fetches far fewer points than the Raw sample method (a maximum of 2000 points) but with a similar fidelity of data to Raw. Server fetches the raw data points from the Historian, then uses an algorithm to reduce the number of points, before sending these on to Explorer.<\/p>\n

While any time series data on an Explorer page can now be configured to use the Adaptive Raw sample method, this would be most useful on a chart or an embedded trend component.<\/p>\n

The default value for the page variable pageSampleMethod <\/em>can also be set to Adaptive Raw.<\/p>\n

\"\"<\/a><\/p>\n

Read more: Adaptive Raw<\/a><\/p>\n

Pie Chart Colours<\/h2>\n

In this release, page designers are now able to assign and specify colours for each segment in a Pie Chart individually, if they don\u2019t want to use the default colour assignment. This addresses customer request 403566.<\/p>\n

\"\"<\/a><\/p>\n

This can be configured in Studio by using the Add or Autofill buttons in the new Segment Colours<\/strong> section. Note that the Name for a segment must match the value of the Name Column<\/em> property.<\/p>\n

Top Tip: Turn on the legend to see what the name values should be.<\/p>\n

Read more: Configuring a Pie Chart<\/a><\/p>\n

Autocomplete in the Entity Selector<\/h2>\n

In this release, autocomplete has been added to the Find Under field in the Entity Selector. The field is enabled when the Entity Selector is configured with a Start Node.<\/p>\n

\"\"<\/a><\/p>\n

Read more: Configuring an Entity Selector<\/a><\/p>\n

Comments and Comment Button Label Change<\/h2>\n

When configuring the Comments or Comment Button component, it was not obvious that you the control could also be used to add comments for tags. To make this clearer, the \u2018Entity\u2019 property has been renamed to \u2018Target\u2019. The functionality remains unchanged.<\/p>\n\n\n\n\n
This release (4.6.4):<\/em><\/td>\nEarlier versions:<\/em><\/td>\n<\/tr>\n
\"\"<\/a><\/td>\n\"\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Pie Chart's Selected Property<\/h2>\n

In this release, the Pie chart's 'Selected' property has been changed from being a Data Item to being a Variable only. This is consistent with the Selected property for other components such as the Treemap, and fixes an issue where snapshots were not being saved correctly.<\/p>\n

When upgrading from a previous version of P2 Explorer, only pages using a variable for the \u2018Selected\u2019 property will continue to be configured correctly. Pages that did not use a variable for the \u2018Selected\u2019 property will need to be reconfigured.<\/p>\n

Here is an example of a Pie Chart configured to use a variable in the previous version:<\/p>\n

\"\"<\/a><\/p>\n

In this release, page designers must specify a variable for this property.<\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

Trend Auto Range Change<\/h2>\n

In the Explorer trend, the Auto Range is now zero or higher, unless there are values to be plotted below zero. Previously, the minimum could be a negative value, which was confusing for the user when there were no points to be plotted below zero. This was introduced in release 4.5.5 and addresses customer request 398786.<\/p>\n

 <\/p>\n

Page Defaults Match BabelFish Defaults<\/h2>\n

When a new page is added in Studio, the default values for startTime and endTime now match those in P2 Explorer 2.6 and earlier (BabelFish).<\/p>\n

Note<\/strong>: This change will not affect existing pages, only new pages created in Studio will use the new defaults.<\/p>\n

In this release, the startTime<\/strong> is now a Relative Datetime<\/em>, set to 1 Day from the endTime<\/strong>, which is now Current Datetime<\/em> with a Refresh Interval<\/em> of 1 minute.<\/p>\n

In version 4.6.2 and earlier, startTime and endTime were defaulted to a Fixed Datetime with the endTime being today and the startTime the previous day.<\/p>\n\n\n\n\n
startTime and endTime defaults in this release (v4.6.4):<\/em><\/td>\nstartTime and endTime defaults in earlier versions:<\/em><\/td>\n<\/tr>\n
\"\"<\/a><\/td>\n\"\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

\n

Previous Releases<\/span><\/h2>\n

For a complete list of P2 Explorer release notes, see Explorer Releases<\/a>.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

P2 Explorer version 4.6.4 is a patch release, with new features including a rich text editor, clickable images, new line styles in the trend, and a new Action Button component.<\/p>\n

Read more<\/i><\/a><\/p>\n","protected":false},"author":1,"featured_media":41866,"parent":28831,"menu_order":129,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":"","_members_access_role":[],"_members_access_error":""},"categories":[7],"tags":[],"class_list":["post-41862","page","type-page","status-publish","has-post-thumbnail","hentry","category-release-notes","Version-4-6-4","Product-ex"],"_links":{"self":[{"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/pages\/41862","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/comments?post=41862"}],"version-history":[{"count":2,"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/pages\/41862\/revisions"}],"predecessor-version":[{"id":45480,"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/pages\/41862\/revisions\/45480"}],"up":[{"embeddable":true,"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/pages\/28831"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/media\/41866"}],"wp:attachment":[{"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/media?parent=41862"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/categories?post=41862"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/oihelp.corporate.ifs.com\/help\/wp-json\/wp\/v2\/tags?post=41862"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}