You can now download the current view when in ‘PONC Analyser’ mode, which displays the cumulative PONC over a period of time, allowing you to take the data elsewhere for further analysis.
Users with self-referencing calculations will have found that the Dependency Map doesn’t accept this configuration causing an error. We’ve resolved this in the latest release.
Where values calculate to NULL they have been displayed as 0 (zero). This is effectively a false positive, causing confusion and makes it hard to identify bad parameter references on the main Jidoka table. They now calculate to ‘BADCALC’ making it clear how the calculation has failed.
A new syntax rule has been added so that tag names with embedded mathematical operators can properly be dealt with. For example, tv-2314.pv would be interpreted as ‘tv minus 2134.pv’. Encapsulating the tag with ‘[[‘ and ‘]]’ will see it dealt with as it should be, e.g., server.[[tv-2314.pv]]
We’ve also resolved an issue with deleting parameters in Internet Explorer, where an internal browser error could cause the delete process not to work.
We’ve always considered Sabisu as ‘one place for everything you need’. Though the emphasis has often been on providing high quality real-time data, we understand that sometimes you need to look at earlier circumstances.
Well, now you can.
Any Publication is now versioned, whether published as data or as a static widget. As soon as you publish something with Sabisu Publisher it’s versioned.
If you choose not to share that data outside the original Community you published to then the data is still versioned. The original Community will always see the latest version and will have access to all the published versions.
If you choose to use Publication Approvals to approve the data for consumption by a different Community then it’s versioned and made available. The third party Community will only be able to access versions approved for them.
It’s easy to access versions. Simply go to ‘Widget Menu’ \ ‘Version history’ and you’ll be presented with
- Cell Range
- Tags (for easy searching in the Widget Store)
To rollback the widget to an earlier version simply click the version you want to see.
To get back to the current version, simply refresh. (Or you’ll get a new version if you select it manually, or by default next time you log in.)
This not only works with static and dynamic Publications; it also works with any data derived from those Publications. So if you have charts built using data which has been ‘published as data’, then they’re also version controlled.
We have resolved an issue seen when two widgets are closely located on the page which caused the Widget Conversation, or Publication Details, or other widget menu item open behind the next widget. The widget and any side bars now come to fore when clicked on.
Advanced users and developers can now configure a point size and shape for a data series in a Google Chart.
We have tightened up the security around data connectors so as to prevent verbose messages being returned. Only On-Premise Administrators will see such messages.
Notifications have been speeded up temporarily, pending a more thorough overhaul.
Shika continues to grow in use both as a calculation and process data historian. It can now calculate the aggregates of tag data over a specific period, e.g., yearly, monthly, daily, hourly or minutely.
We will soon be implementing complex non-linear interpolation.
As the platform has matured it’s clear that some components in the Builder are not used, have been superseded by better methods, or have become less reliable as browser versions have moved forwards. The following components have been deprecated:
- Gantt (replaced with a new Gantt, currently in beta with certain customers)
Before deprecating each of these components we checked all widget configurations to ensure no customers will see a loss of functionality. Hence we expect you will see no impact.
The collapsible table component now accepts width values.
We’ve also introduced a new calendar component which allows users to visually represent time/task data in Sabisu. Where the Gantt chart currently in beta is great for complex schedules, the calendar component is ideal for simple schedules or task plans. The calendar provides a full set of mappable properties which should allow it to fit almost any dataset.
Builder users also have some unique features for manipulating the calendar such as use $WidgetValue(calstart) and $WidgetValue(calend) to get the start and end dates of the user’s currently selected calendar. You can also provide your own custom click events for when a user clicks on each item in the calendar. Your custom event will receive an object called ‘item’ which contains all of the information on the item the user has clicked on in the calendar which was passed to the calendar control.
As always if you have any questions or suggestions, head over to our LinkedIn group and share your thoughts.