Some interesting Sabisu related developments this week with two new sites launched:
CapitalEyes exploits Sabisu’s unique hybrid-cloud architecture to deliver a powerful value proposition; total real-time visibility throughout the supply-chain of a large capital project for less than a vendor spends on his project controls capability.
Genba addresses the needs of a growing segment of Sabisu users; development teams. By extending Builder to become a full-featured integrated development environment and exposing key parts of the platform through our API, the platform can deliver huge productivity gains for in-house and outsourced development teams.
These support our SME offering, Rinku, which has had significant coverage on start-up focused sites and is garnering a loyal following.
This week the team are focused on deploying Sabisu Appliances – but we do have a nice feature planned for release next Monday which will add significant capability to Sabisu, CapitalEyes, Rinku and of course Genba, developing the platform’s already credible offering as a single place to get everything in your work life done.
It’s now possible to restrict on-premise users so that they can’t join an external community and download a file. This further secures the platform and cements communities as the first line of defence against malicious activity.
We’ve resolved an issue introduced by the latest beta of Google Chrome, where header menus could appear behind the header bar.
Users tagged in the Hub or header ‘Share’ now have hovercards showing the communities the you share with them and allowing you to start a chat.
Builder & Genba
Everything that’s in the Builder is also available as part of the Genba offering (see above).
We’ve updated more documentation this week, focusing on documenting the widget subcomponents. This should really help developers exploit the platform.
A new ‘Data’ subcomponent has been added. All it does is retrieve data, making it available to other subcomponents in the widget. Little as this is, it’s quite powerful, as that subcomponent can then be reused across widgets, or modified slightly when back-end data is moved.