{"id":20170,"date":"2016-10-03T15:16:32","date_gmt":"2016-10-03T07:16:32","guid":{"rendered":"http:\/\/localhost\/help\/?page_id=20170"},"modified":"2026-08-13T22:33:59","modified_gmt":"2026-08-13T14:33:59","slug":"explorer-release-4-4-4","status":"publish","type":"page","link":"https:\/\/oihelp.corporate.ifs.com\/help\/p2-explorer\/explorer-releases\/explorer-release-4-4-4\/","title":{"rendered":"Explorer Release 4.4.4"},"content":{"rendered":"\n

\"P2_RGB<\/p>\n

P2 Explorer 4.4 reinvents P2 Explorer into a prime data visualization tool<\/strong>. It uses new technologies to support cross-browser<\/strong> compatibility and new, sleeker visualizations. Content is key, allowing you to zoom in on and diagnose problem areas<\/strong>, so they can be addressed quickly and effectively.<\/p>\n

In P2 Explorer 4.4, elements on a page can interact with other elements on the same page to drive dynamic, information-rich displays<\/strong>, while cross-referencing of data enables further comparison and analysis of related information. An approvals<\/strong> process also allows anyone to submit their own displays for publishing to a wider audience within the organisation.<\/p>\n

What sets this version apart from previous releases is the focus on usability<\/strong>. The new data selector makes data-driven pages easier to design, and a set of predefined styles for selected components significantly improves the ability to customise displays.<\/p>\n

Release 4.4.4 of P2 Explorer includes several new components and features, and also incorporates component enhancements, a more visual hierarchy navigator, and descriptions on the trend\u2019s trace table.<\/p>\n

Note: P2 Server 4.4.4 is a prerequisite for P2 Explorer 4.4.4.<\/p>\n

\u00a0<\/p>\n

Icons in the Hierarchy Navigator<\/h2>\n

In P2 Server, icons can be added to entities at their primary template level.<\/p>\n

With this release of P2 Explorer, entities in P2 Server that have a primary template with an assigned icon will display this icon alongside the display name, in the hierarchy navigator.<\/p>\n

In the slide-out attribute panel for an entity, attributes and attribute values that are assigned to a dataset have a dataset \u00a0icon; for all other attributes, a tag icon appears alongside the\u00a0 attribute and attribute value.<\/p>\n\n\n\n\n
Entity Icons in the Hierarchy Navigator<\/em><\/td>\nTag and Dataset Icons in the Attribute Panel<\/em><\/td>\n<\/tr>\n
\"entity-icons\"<\/a>\u00a0<\/td>\n\"tag-icons\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Read more: Tag Search and Hierarchy Navigation<\/a><\/p>\n

\u00a0<\/p>\n

Layering in Precision Layout<\/h2>\n

Components that are placed onto a Precision Layout page can now be layered, one on top of the other, to build better schematics. The three levels are: Foreground, Middle, and Background. As a page designer, change a component\u2019s placement by selecting the component, then choosing its layer from the drop-down list, instead of moving, copying, cutting and pasting components to get the completed page design.<\/p>\n

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

Read more: Precision Layout tutorial<\/a><\/p>\n

 <\/p>\n

Status Tile<\/h2>\n

The Status Tile component displays the value of its configured data, and is coloured according to the relationship between this value and a defined limit. A short description is displayed below the value. This could be a description of the relationship between value and limit. The status tile can contain a hyperlink to another Explorer page or trend, or an external URL.<\/p>\n

\"status-tile-components-2\"<\/a><\/p>\n

To the end user, it is immediately apparent whether the value is over, under, or equal to the limit, depending on the status tile\u2019s colour. (Note<\/strong>: colours may vary if a different style is applied).<\/p>\n

The status tile is typically grouped with related tiles, as shown here. Hover over a tile for the full value (with decimals), as well as the data\u2019s origin.<\/p>\n

\"status-tile\"<\/a><\/p>\n

Read more: Status Tile tutorial<\/a><\/p>\n

 <\/p>\n

Treemap<\/h2>\n

The Treemap component is used to display a set of related data entities (for example, areas, wells, equipment such as crushers) as a grouping of rectangles, or regions. Entities are graded in two ways: firstly, the value of an aspect of their data (for example, a pressure reading) relative to that of the other entities, and secondly by comparing an aspect of their data (for example, temperature) against a defined minimum and maximum value. The component can also be configured to use a region\u2019s entity name to update a page variable,\u00a0 when the user clicks it.<\/p>\n

Grading by Size<\/strong>:\u00a0A defined aspect or attribute of data is used as the criterion for comparison between the entities. For example, each entity\u2019s pressure reading is compared against the other pressure readings.\u00a0Those entities with the largest value are displayed as large rectangles in the top left, while those with the smallest value are displayed as small rectangles in the bottom right. The full range of regions is distributed between the largest and smallest, top left to bottom right, \u00a0with size proportional to value. If the number of regions is limited (to say, 10) then only those entities with the highest values are displayed \u2013 the rest are displayed in an aggregated region called \u2018Other\u2019 (collectively, this could be the largest group).<\/p>\n

Grading by Colour<\/strong>:\u00a0A defined aspect or attribute of data for each of the entities is used as the criterion (for example, temperature) as compared against the component\u2019s configured minimum and maximum values. Each displayed region has its colour determined by whether this data is above the maximum (coloured red, in example below) or below the minimum (coloured turquoise, in the example below). Those with values between minimum and maximum have interpolated colours based on how close they are to the minimum\/maximum (greys in the example below). The aggregate region has its own colour (purple in the example below).<\/p>\n

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

 <\/p>\n

Wind Vane<\/h2>\n

The Wind Vane is a component styled as a compass. It is designed to show wind direction readings in relation to other, configurable angles which are used to depict three zones: a warning zone, a danger zone, and a normal zone (with minimum, average and maximum marked out as blue lines). The warning zone is marked out by light grey, which turns yellow when the current wind direction is in that zone. The danger zone is a darker grey, which turns red when the current wind direction is in that zone.<\/p>\n

The circumference is coloured in yellow for wind direction in the warning zone, and red for wind direction in the danger zone; otherwise it remains grey.<\/p>\n

Note<\/strong>: Colours may vary, if different styling is used.<\/p>\n\n\n\n\n
\u00a0\"wind-default-state\"<\/a><\/td>\n\u00a0\"wind-warning-state\"<\/a><\/td>\n\u00a0\"wind-danger-state\"<\/a><\/td>\n<\/tr>\n
Showing current wind direction above average, but below the maximum<\/em><\/td>\nShowing current wind direction in the warning zone<\/em><\/td>\nShowing current wind direction in the danger zone<\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Hover over the Wind Vane to see a tooltip displaying the current direction angle, as well as average, min and max angles.<\/p>\n

\"wind-tooltip\"<\/a><\/p>\n

Read more: Wind Vane tutorial<\/a><\/p>\n

 <\/p>\n

Box Plot<\/h2>\n

The Box Plot component is used to show the distribution of a set of data, using a Median and Quartiles.<\/p>\n\n\n\n\n
\u00a0\"box1\"<\/a><\/td>\n\u00a0\"box2\"<\/a><\/td>\n\u00a0\"box3\"<\/a><\/td>\n<\/tr>\n
The lines at the top and bottom represent Post Q and Pre Q respectively. The grey box represents the distribution between Q1(bottom) and Q3 (top), with the median line and value shown in the centre of the box.<\/em><\/td>\nHover over the box plot to see actual values.<\/em><\/td>\nThis box plot is configured to show the minimum and maximum values (used for scalability).<\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

An advantage of the box plot as a statistical display, is that outliers do not change the distribution of data. In the two sets of data represented below, all data points are identical except for the maximum: 450 and 100, respectively. Note how this only slightly alters Post Q: the rest of the distribution is the same for the two Box Plots.<\/p>\n\n\n\n\n
\u00a0\"box4\"<\/a><\/td>\n\u00a0\"box5\"<\/a><\/td>\n<\/tr>\n
Max value is 450<\/em><\/td>\nMax Value is 100<\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

If you group several box plots, using the same scale, the relative distribution patterns between similar sets of data becomes clear. Note<\/strong>: The box plot on the left has been configured to show a scale between the minimum and maximum display values.<\/p>\n

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

You can configure the box plot to be vertical (as shown in the above examples) or horizontal, as shown below:<\/p>\n

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

 <\/p>\n

Table Layout Ordering<\/h2>\n

When a Table Layout uses child entities of a selected node to populate its rows, these entities have the same ordering that they have in a hierarchy control, which is based on the ordering of the hierarchy in P2 Server.<\/p>\n

 <\/p>\n

Entity Selector: Infinite Scrolling<\/h2>\n

The Entity Selector component now uses infinite scrolling instead of paging, which means less clicking for the end user. Remember to limit large \u00a0result sets, using the \u2018Search entities\u2019 keyword filter option, as well as the \u2018Find under\u2019 to search for entities under a node.<\/p>\n

Read more: Using the Entity Selector<\/a><\/p>\n

\u00a0<\/p>\n

Hyperlink and Hotspot<\/h2>\n

The link type<\/em> for controls which include a hyperlink no longer defaults to \u2018Open Page\u2019, but rather to \u2018Select a type\u2019, which means that a hyperlink does not need to be defined. This is particularly relevant for the new Status Tile control, where the hyperlink feature is optional.<\/p>\n

In addition, the drop-down lists for workspaces is filtered to those that contain trends for the \u2018Open Trend\u2019 type, and those that contain pages for the \u2018Open Page\u2019 type.<\/p>\n

Read more: Hyperlink tutorial<\/a>, Hotspot tutorial<\/a><\/p>\n

\u00a0<\/p>\n

Trend Tag\/Entity Descriptions<\/h2>\n

Tags and Attribute Values that have descriptions defined in P2 Server have these descriptions displayed next to their name, in the trace table of a Trend. Hover over the name or description of a trace, to see the full name\/description in a tooltip.<\/p>\n

\"trend-desc\"<\/a><\/p>\n

Read more: Creating a Trend<\/a><\/p>\n

\u00a0<\/p>\n

Font Family for Styles<\/h2>\n

Explorer now has four font families to choose from when adding component styles that include the Font Family property (for example, the Text Label and Gauge component styles). These are:<\/p>\n