Announcing the Tines Storyboard
Continuing our Autumn 2019 feature spotlight, we’re excited to reveal what we consider to be the most significant update to the Tines security automation platform yet: the storyboard.
Since our first release, a core feature of Tines has been the automatically generated diagrams, which visually represented how agents in an automation story were connected. Before the storyboard, a typical Tines diagram looked something like this.
The diagram was effective, however, it had a number of issues opportunities for improvement:
- It was not interactive
- Building stories meant flipping between an action config and the diagram
- Viewing an action’s config meant leaving the diagram view
- It was hard to tell action types apart
- You couldn’t customize the layout
- The badges on actions showing counts of emitted events required a page refresh for updates
The Tines storyboard
With the Tines Autumn 2019 release, the storyboard replaces the diagram. It takes the best parts and adds many more capabilities.
"The storyboard makes building automation stories easier and faster – up to five times faster according to our benchmarks."
Creating new actions
With the storyboard, we can drag actions of any type from the left panel and drop them onto the storyboard.
Defining sources and receivers
Previously, defining an action’s sources and receivers, meant editing the action’s options and choosing the source or receiver from a list. However, with the storyboard, it’s as simple as dragging a string from the source action to the receiver.
From the library panel on the left hand side of the storyboard, we can search for action templates, both public and private, and drag them onto the storyboard.
Storyboard action properties
The right hand side of the storyboard contains the action properties panel. When an action is selected, the properties panel will display it’s common config and an editable options block.
*Please note we recently updated our terminology. Our "agents" are now known as "actions," but some visuals might not reflect this.*