TOPi® Browser Hyperion Release Notes 2021-10

TOPi® Hyperion 2021.10.0 enhances TOPi® Browser features to define and run both process information and production planning calculations in a more diverse way.

Landscape with sea and darkening sky

TOPi® Hyperion 2021.10.0 offers new applications and enhanced user experience to create KPIs from energy related data, based on e.g. R programming language, which is widely used for developing statistical software and data analysis. New release also supports wider energy production fleets even better than before by adding more flexible categorization and data linking features. Intuitive ease of use is strengthened by implementing multiple improvements in process displays, shift logbook and several other tools.

Supported browsers:

  • Mozilla Firefox ESR 91
  • Mozilla Firefox ESR 78
  • Google Chrome (latest version at the time of release)
  • Microsoft Edge (Chromium-based) (latest version at the time of release)

General:

  • The architecture of TOPi® Browser has been changed to enable easier addition of new major features
    • One addition is the possibility of configuring and running R, Python, GAMS or Solvo calculations
  • Do not display a black outline around tabs that are clicked on in the user interface (LA004660-4066)
  • Terminology was changed: "site" (which can be used to group e.g. report templates and displays and then specify permission to them for only some users) is now "category", which should be a more generic term and cover more use cases than before (LA004660-2216)
  • Unnecessary indexes dropped from system_log database table. This will reduce database disk usage. (LA004660-4048)
  • Do not show confirmation dialog when saving into a private folder and the user has selected the category to be "No category" (previously "No site") (LA004660-4312)
  • Fixed a problem on login page when using Form login as the authentication method. If the user typed the username and password really fast or if the Internet connection was slow, the login did not always succeed even if the credentials were correct. (LA004660-4300)

Data sources:

  • Timescale: Implement workaround for bad query performance (LA004660-4083)
  • PostgreSQL / Timescale: Possibility to optimize the performance of fetching the last value for a lot of variables. Useful in e.g. Configurator and ProView. The optimization is disabled by default because it slows down writes to the variable tables. (LA004660-4198, LA004660-4306)
  • Aspen: When saving values, ensure that the values have been saved before continuing. Previously some batch updates did not properly update all the values. The system property common.aspen.msecstosleepafterinsert was used to work around the problem but it wasn't reliable. (LA004660-4145)
  • Timescale: Fixed a bug where it was not possible to rename a Timescale variable with compression on (LA004660-4254)

Dashboard:

  • Fixed a bug where an uploaded background image does not appear immediately after upload (LA004660-3698)
  • It is now possible to configure whether links attached to elements are opened in the same or a new browser window / tab. Previously they always opened to the same window / tab. LA004660-4199)
  • Links from a dashboard to another dashboard work now. Previously they did nothing. (LA004660-4276)

Report:

  • Fixed a bug where buttons / links were overlapping after exiting Modify data mode (LA004660-4065)
  • Columns with data from a formula or an ad hoc formula are not editable in Modify data mode anymore. Previously it was possible to edit the values but trying to save them would cause an error. (LA004660-4064)
  • Fixed positioning of the "copy values down" tool in Modify data mode (LA004660-4315)
  • Fixed a problem with time and value filtering tables in Analysis view where it was not always possible to scroll the last row into view (LA004660-4308)

Recalculation:

  • Possibility to configure a category (site) and a folder (group) for a recalculation directly in the database (LA004660-582)

OP:

  • Possibility to configure a category (site) and a folder (group) for an OP display (LA004660-3985)

ProView:

  • Editor: performance improvements (LA004660-4134, LA004660-4144)
  • Editor: When using the Check Process View functionality, elements with no specified tag are not considered as a problem any more (previously they were displayed with the following problem message: Missing tag "null"."null") (LA004660-4233)
  • Editor: Added shortcut (button E) for opening the Object properties dialog (LA004660-4001)
  • The ProView text at the top is now a link to the ProView initial view / default display (if there is one) (LA004660-4200)
  • It is now possible to configure whether links attached to elements are opened in the same or a new browser window / tab. Previously they always opened to a new window / tab. (LA004660-4199)
  • Added possibility to save a value directly from a ProView display. The variables / elements whose values can be edited are defined in the Editor. This is useful e.g. for changing constant parameter values quickly. (LA004660-3881)
  • A more informative error message is displayed if the display has a variable that does not exist (LA004660-4232)
  • Added possibility to define a separate ProView default display for each category (site). Previously it was possible to specify only one default display, which was not good in cases where some users didn't have access to the category of the default display. It is also possible to define a default display for users with no default category (site) defined or for users whose default category does not have a corresponding default display. The configuration is done directly in the database. (LA004660-4216)
  • Possibility to optimize the fetching of the last value for a lot of PostgreSQL and/or Timescale variables. The optimization should improve the performance of the displays in real-time mode. The optimization is disabled by default because it slows down writes to the variable tables. (LA004660-4198, LA004660-4306)
  • Added new library components that are included in all installations. New components were added to the following sections: Blowers and pumps, Dampers, and Valves and sprayers. (LA004660-4035)

Logbook:

  • Hungarian translations updated (LA004660-4091, LA004660-4132)
  • Increased the maximum length of entry, entry comment and notification texts from 4000 to 10000 characters (LA004660-4213)
  • Added possibility to configure a manual ordering for Logbook locations. The ordering can be defined in the Admin section by specifying an order number for each location. Note that the "Order of locations" setting in the Logbook Admin Settings section has to be set to "Order number" so that the order number has any effect. (LA004660-4037)

RunGuide:

  • Improved data fetching performance (LA004660-4162)
  • Added possibility to hide Wake up tool (LA004660-4163)

Time Series Importer:

  • Initial version of the application which allows requesting and importing time series data from another system (LA004660-4043)

Security:

  • The application user interface has been completely changed
  • Possibility to use OAuth 2.0 as an authentication method instead of the other methods

Configurator:

  • Show user-friendly status in status column and raw status in tooltip (LA004660-4143, LA004660-4155)
  • Possibility to optimize fetching of the last value for a lot of PostgreSQL and/or Timescale variables. The optimization should improve the performance of variable status loading in Configurator. (LA004660-4198, LA004660-4306)
  • Fixed a bug where the possible error message when saving one variable was just "undefined" (LA004660-4263)
  • Fixed a bug where it was not possible to rename a Timescale variable with compression on (LA004660-4254)
  • Improved the robustness of the application when a category (site) that is in use is deleted (LA004660-4274)

Monitor:

  • Added possibility to define a separate Monitor default display for each category (site). Previously it was possible to specify only one default display, which was not good in cases where some users didn't have access to the category of the default display. It is also possible to define a default display for users with no default category (site) defined or for users whose default category does not have a corresponding default display. The configuration is done directly to the database. (LA004660-4217)