{"id":28848,"date":"2017-08-01T08:19:21","date_gmt":"2017-08-01T00:19:21","guid":{"rendered":"http:\/\/localhost\/help\/?page_id=28848"},"modified":"2026-08-13T22:33:59","modified_gmt":"2026-08-13T14:33:59","slug":"explorer-release-4-5-2","status":"publish","type":"page","link":"https:\/\/oihelp.corporate.ifs.com\/help\/p2-explorer\/explorer-releases\/explorer-release-4-5-2\/","title":{"rendered":"Explorer Release 4.5.2"},"content":{"rendered":"\n

\"P2_RGB<\/p>\n

P2 Explorer 4.5 addresses the need for users to build their own Explorer pages and trends. With the addition of two critical components, the Performance Curve and the Embedded Trend, Studio\u2019s Toolbox has a comprehensive set of controls, enabling you to create the pages that you need, in order to optimise the way you display your data.<\/p>\n

Explorer 4.5 offers a more usable Design Mode, and a Display Mode that makes it simpler for users to navigate through the displays, and easier to understand data and trends.\u00a0Navigation has been streamlined to give a better user experience, allowing users to link to pages, trends or related information on external URLs through hyperlinks or drill-down charts on pages, as well as view a trend or point details of data displayed on pages. Workspaces are easier to work with than before, and the ribbon tabs have been consolidated.<\/p>\n

Patch Release 4.5.2 introduces a new Text Input component, plus a variety of enhancements to the trend, performance curve, triggers, and printing as suggested by customers. It also addresses several other issues raised through P2 Customer Support.<\/p>\n

\n

Text Input Component<\/h2>\n

The Text Input component allows a user to type some text or a number that is used as input for a variable. This can be used to change the data displayed on the page, and is retained in snapshots and page links.<\/p>\n

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

This can be used for a variety of situations, such as allowing the user to filter a dataset based on description.<\/p>\n

The variable is bi-directional, meaning that it will update other variables on the page if the text input changes, and the text displayed in the input box will also change if something else changes the variable value (such as a value from a combo box).<\/p>\n

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

In design mode, the page designer simply specifies the variable that stores the user-supplied input, and some text that appears as a tooltip as well as a placeholder inside the input box.<\/p>\n

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

The default value for the variable can be specified using Page Defaults, and both Text and Number data types can be used.<\/p>\n

Style designers can change the font size, family, weight, alignment, and case of the input text and placeholder text. Note that the colour can also be changed for the input text, but placeholder text will always be grey regardless of the colour specified in the style.<\/p>\n

Read more: Text Input<\/a><\/p>\n

 <\/p>\n

\n

Performance Curve<\/h2>\n

The Performance Curve receives a number of feature and usability enhancements for page designers in this release. Some of the enhancements apply to each curve, some of them apply to the performance curve as a whole, and some of them apply to both.<\/p>\n

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

Legend<\/strong>: There is now a \u2018Show Legend\u2019 check box, which allows you to display a legend below the chart, showing the name and colour of each curve.<\/p>\n<\/td>\n

\u00a0\"\"<\/a><\/td>\n<\/tr>\n
\n

Name<\/strong>: You can specify a name for each curve, which will appear in the legend. Only curves with an explicitly defined name will appear in the legend.<\/p>\n<\/td>\n

\u00a0\"\"<\/a><\/td>\n<\/tr>\n
\n

Colour<\/strong>: You can specify the colour of each curve, rather than colours being automatically allocated.<\/p>\n<\/td>\n

\u00a0\"\"<\/a><\/td>\n<\/tr>\n
\n

Line Thickness<\/strong>: You can change the thickness of each curve. Use 0 to hide a curve, or specify any number of pixels to make the line as thick as you want.<\/p>\n<\/td>\n

\u00a0\"\"<\/a><\/td>\n<\/tr>\n
\n

X-Min <\/strong>and X-Max<\/strong>: The previous Min and Max fields have been renamed to X-Min and X-Max. These now apply to both the whole Performance Curve and to each Polynomial Curve (does not apply to XY curves). When applied at the Performance Curve level, it determines the scale on the X-axis. When applied at the individual curve level, it reflects the leftmost position on the x axis that the curve starts and the rightmost position that the curve ends.<\/p>\n<\/td>\n

\u00a0\"\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Step<\/strong>: This has been removed from the Performance Curve. Instead, the optimal value is calculated for each curve, based on the curve\u2019s X-Min and X-Max values.<\/p>\n

Y-Min <\/strong>and Y-Max<\/strong>: These new limits apply to both the whole Performance Curve and to each Polynomial or XY Curve. When applied at the Performance Curve level, it determines the scale on the Y-axis. When applied at the individual curve level, it determines what parts of the curve to display, and will only show the portion that appears between the specified minimum and maximum values on the Y scale. In the example below, the curve only appears between 50 and 150 on the Y axis.<\/p>\n\n\n\n
\"\"<\/a><\/td>\n\"\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Re-ordering curves<\/strong>: You can now re-order curves in the editor by using up\/down buttons.<\/p>\n

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

Read more: Configuring a Performance Curve<\/a>, Using a Performance Curve<\/a><\/p>\n

 <\/p>\n

\n

Trend<\/h2>\n

The trend has received a substantial facelift in order to maximise the size of the trace window, which was one of the most significant feedback items we received from a number of customers during our annual Customer Advisory Board workshop.<\/p>\n

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

Trace Table<\/strong><\/p>\n

The amount of space taken by the trace table has been significantly minimised. The table will now only take as much space as is required to show all the traces, plus a blank row for adding new traces. The trace table will grow as needed up to 8 rows, and then will display a scrollbar if there are more than 8 traces.<\/p>\n

The Axis column has been moved to the far left, and a Delete \"\"\u00a0icon has been added to the trace name. To remove a trace, click this Delete icon or highlight the row and press the Delete key.<\/p>\n

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

Changing the Display Min and Display Max values no longer requires a double click. Clicking the \"\"\u00a0to clear a custom value will return the value to that set by the tag.<\/p>\n

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

The toolbar containing the Add Trace button, and other options, has been removed. The Add Trace button is no longer needed as an additional blank row will always be present in the trace table to add a new trace, and the other options have been moved to the ribbon (see below).<\/p>\n

Controls in the Ribbon<\/strong><\/p>\n

In the ribbon, the existing View buttons (Controls, Range Selector, Trace Table) have been compacted to stack vertically.<\/p>\n

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

The following controls have been moved from the trace table and the trace window, providing a single point of configuration for the entire trend.<\/p>\n

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

From the trace table: Auto Range, Y Axis, Y Range<\/p>\n

From the trace window: Hairline (renamed from Hairlines), Y Scale (renamed from Y Scale Type)<\/p>\n

The New Calc<\/strong> \"\"\u00a0button has also been removed from the Trend ribbon, as this functionality is now available using the Calculation Editor in the trace table.<\/p>\n

Performance Improvements<\/strong><\/p>\n

This release sees some changes to the way the trend renders traces, to improve load times.<\/p>\n

The trend will now open with a duration of 8 hours as the default timebase, instead of 1 week. This is configurable in the web.config file (DefaultTrendDuration<\/em>).<\/p>\n

To prevent overloading the trend with too much data, the available Sample Interval will now change depending on the selected timebase. For example, if the timebase spans 4 weeks the smallest sample interval available will be 20 minutes. But if the timebase spans 1 day, the smallest Sample Interval available will be 10 seconds. This responsive sampling behaviour is designed to prevent accidental loading of too much data when a user modifies the sample settings, and better reflects the actual sampling combinations likely to be used to produce useful results.<\/p>\n

When displaying raw data, the trend will limit the timebase to 8 hours, however this can also be changed in the web.config file (MaximumRawDuration<\/em>).<\/p>\n

Keyboard Shortcuts<\/strong><\/p>\n

You can now use the following keyboard keys and shortcuts in the trend:<\/p>\n