edgeCore 4.1.0 Release Notes
edgeCore Security Updates
EC-334 – Upgrade jQuery from 3.4.1 -> 3.5 (CVE-2020-11022 and CVE-2020-11023).
EC-562 – Upgraded server dependencies (Log4j 2.13.1 – CVE-2020-9488, Spring Security – CVE-2020-5408, DOM 4J – CVE-2020-10683)
EC-567 – Upgraded Apache Tomcat 9.0.35 (CVE-2020-9484)
EC-553 – Improved handling of expired sessions redirecting a user to the login page, previously it would happen when the mouse moved or some other activity was detected.
edgeCore New Features
edgeCore Visualization Platform updated to Angular v9 providing:
- Enhanced and Updated HtmlTemplate Code Patterns using the latest Angular Syntax.
- Improved performance while rendering Page Context changes and Data Updates.
- Improved styling of controls and themes.
- Improved Admin Pipeline view with additional detail and status information on the node.
- Updated to support the latest Angular 9 coding syntax.
- Revised Reference Help delivered with the HTML Template visualization editor.
- (Upgrade Required) – Custom HTML Template Visualizations will update required.
- Improved client-side logging of HTML Template errors; providing improved references to specific HTML Template Visualization the error occurs.
- Updated default login page, replacing Angular dependency with JQuery.
- Custom Login pages are copied to a staging path: ‘static-web/login’ to ‘static-web/login-pre4.1’; this is by design as it will allow customers to upgrade their login pages.
EC-447 – About screen product icon updates.
EC-117 – Emit metric for visualization/pipeline construct usage.
EC-399 – Checkhealth URL now provides additional information including is the server licensed, is it clustered, and if clustered is the cluster available (to help determine if admin tasks are available).
EC-32 – ForEach transform – This transform iterates over each record in one source dataset (master), and for each row, it uses an attribute value to retrieve data from another dataset (detail) with the attribute value from the master data as the nodeVar for the detail data. The aggregation of this returned detail data is the result of the ForEach transform. The additional benefit of setting max requests used to queue up parallel requests on a detailed source.
EC-28 – Data cache persistence – Feeds can be flagged as persisted, which will store the results to the filesystem instead of just in memory. This data is then available following a restart before the feed would otherwise have data from a new query. This also reduces memory consumption on the server for persisted data.
EC-80 – Added ability to hide system nodes in the Pipeline.
EC-288 – H2 Upgrade 1.4.199+ from 1.4.196 (general performance gains/improvements).
EC-397 – Unable to use secVars (all the Vars) in ENV settings for script sources.
EC-97 – Prometheus count metrics for any page status updates by upstream node and state (success, stale, error).
EC-97 – Prometheus count metrics for run updates by status.
EC-488 – Added refresh buttons to allow a user to refresh the pipeline topology and/or pipeline status.
EC-344 – Improved controls to hide system pipeline nodes in the topology and the search filter.
EC-388 – Added ability to upload server assets.
EC-152 – API calls to manipulate applications, access dashboards, and application details.
EC-398 – The CLI tool / API should provide a way to load/update an adapter.
EC-429 – RPA Privileges and Configuration Script updates used to enable/control RPA script access.
EC-438 – RPA Server License Feature Control to enable/disable script access (per server).
edgeCore Management Console New Features
EC-125 / EC-132 – Added es-cli commands and repo on EMS to push/pull snapshots from edgeCore Clusters.
EC-129 / EC-130 – Update cluster service for EMS snapshots.
edgeCore Resolved Issues
EC-579 – Resolved issue where HTML Template fireAttributeClickEvent/Click Attribute action did not update pageVars reported on v3.11.5
EC-474 – Improved cache settings on the login page.
EC-481 – Improved performance when creating a JSON Feed, allowing the overall sampling to be tuned.
EC-85 – Windows CLI Shuts Down Due To Powershell Issue.
EC-400 – Improved detection of systemd when running the configure script in AWS cloud-init.
EC-244 – Fix need to restart after partial restore.
EC-362 – Resolved Client memory leak.
EC-83 – “No Data To Display” message on top of web content Visualization when used in show visualization.
EC-164 – Fix issue that blocked Administrators from editing LDAP Domain Config if a deleted Group was referenced by the Group Mapping Config.
EC-292 – Removed ‘Refresh’ control enabled when an LDAP Domain is selected on the Domains Configuration Page (the request was actually deleting the domain, there is already a delete button available).
EC-44 – Improved DateTime Formatter configuration screen.
EC-352 – Improved Date Parser configuration screen layout and controls.
EC-49 – Improved field highlights and checks in JSON parsing screens.
EC-50 – Resolved issue configuring icon renderer in list visualization.
EC-102 – Improved Topology Visualization’s link formatting config window.
EC-379 – Various bugs in provisioning Domain UI (improved validation test code).
EC-380 – The user listing in Provision Domain/Provision Users UIs is a bit confusing.
EC-384 – LDAP Domain Editor bug fixes when switching type (OpenLDAP, ActiveDirectory, or Generic).
EC-396 – LDAP Connection UI doesn’t check for the duplicate names.
EC-100 – Partial backups do not include nodes referenced fetched within JS Feeds or Transforms.
EC-427 / EC-430 – Additional error handling in restore processing (Missing Password Policy / All Users Group Initialization).
EC-317 / EC-327 – Resolved incorrect handling of endpoint properties are getting attached to the connection property list (with default values). In cases of File/Script Connection, a re-edit would show the default value instead of the initial configured value.
EC-150 – Server writes to local.properties too frequently.
EC-94 – Edge SessionLog Appender database errors.
EC-41 – Error messages about ‘edgeSuite Job Status’ connection not being licensed.
EC-628 – Job Status records deleted too early.
EC-42 – SQL results processing problems in the EMS server when using MySQL.
EC-616 – Table visualization – Search filter now supports values that contain a single quote.
EC-610 – Table visualization had extra padding along the right side.
EC-418 – Tabular preview data now preserve attribute order.
EC-597 – Improved support for headless Java installations (avoiding issues where image rule-sets would fail).
EC-576 – Updated handling of temporary Snapshot filesystem artifact (cleaning up filesystem space).
EC-574 – Unable to register Cluster when running with MySql8.
edgeCore Known Issues
Custom Login Page Compatibility
Login pages built on versions prior to edgeCore v4.1 are not compatible. An upgrade script is included to help stash custom login pages into ‘static-web/login-pre4.1’ and the customizations will require manual migration to the new default template.
Bootstrap 4 Updates
Due to the significant upgrade to Bootstrap 4, systems with customizations in the following areas should be tested to determine if they will require updates:
HTML Template Visualizations
Example: Glyphicons are no longer included. If you have custom HTML Templates that used them, in v3.11 they will all be empty.
Common Table Expression ‘WITH’ Clauses
edgeCore uses the H2 database in support of the SQL Transforms. SQL that uses Common Table Expression (CTE) ‘WITH’ clauses have been identified as causing two issues.
- Lock Timeouts: Transforms fail to run as temporary tables fail to be cleaned up.
- Memory Leaks: The temporary table results are not being cleaned up properly in all instances, and it will trigger Out Of Memory on the JVM.
For additional information on this known issue, and remediation options, see SQL Transform.
- Errors connecting to 3rd party https webdata/webcontent sources.
edgeCore fails to connect over HTTPS to backend data sources. In this case, one likely solution is to enable SNI, this is a global configuration so on some systems it might have the opposite affect.
# — SNI Options; may need to be enabled when connecting to 3rd party https webdata/webcontent sources.