Happy New Year from everyone at Sabisu, we hope you’ve enjoyed the Christmas break.
We’ve hit the ground running and are happy to roll-out some enhancements and performance improvements to Jidoka.
We’ve spent some time looking at improving performance on various areas of the system based on feedback from our customers.
On the main operational variables page you can now see a new results limiter which allows you to see as little or as many parameters as you’d like.
This should improve performance for customers using older versions of Internet Explorer who have a large number of operational variables available in the system.
We’ve added a new feature to the navigation side-bar in Jidoka which now allows users with Editor access to define which Sabisu Communities can see the node and it’s operational variables.
This means if there’s a part of your system you don’t want everyone to see, there are a few simple steps to follow to restrict access to a node area.
- Create a new Community in Sabisu.
- Invite the people you wish to have access to the node into the new Community. You can use an an existing Community to define access.
- On the tree view, edit the tree-node and then tell it which Communities are allowed to interact with it in the ‘Visible To‘ section.
Minor Fixes & Improvements
- There is a small update to the Trend chart in Jidoka to ensure that there aren’t any outages in the trend if some bad data is evident at source. In future, if there are any calculations which return an error or calculate a null value then a default of zero is shown on the chart.
- Resolved an issue in Actions where an error would be thrown if a hyperlink was used in a comment for an Action.
As always if you have any questions or suggestions, head over to our LinkedIn group and share your thoughts.