clario 2.0 - What to Expect: Less Rework

When it rolls out this fall, clario 2.0 will represent a herculean development and testing effort on the part of our team. Previously, I wrote about the clario development roadmap, stating that the user community’s feedback is the lifeblood of our approach. This invaluable feedback continues to roll in and as a result we are constantly refining and enhancing our development initiatives. In a series of short posts over the next few days I will present the most important fixes and features included in clario 2.0.

First, less rework:

The Issue: As many who develop software know, in the delicate balance between functionality and release dates, functionality frequently loses. One such sacrifice in clario 1.x was what we refer to as destructive metadata. In clario today, any change to the configuration of nodes “upstream” results in the configuration of all subsequent nodes being cleared. This has been the user community’s single largest complaint and is our highest development priority.

The Resolution: clario 2.0 implements “non-destructive metadata” which dramatically reduces unnecessary rework. How does it work?

• Change an attribute’s name: clario simply updates the attribute’s name wherever it is used in the workflow.
• Change an attribute’s type or delete an attribute: A waterfall resolution algorithm is fired in the subsequent nodes that may require the user to take action, but preserves all non-affected configuration.
• Add an attribute: The new attribute is immediately made available in downstream nodes for inclusion in configuration.
• Disconnect a node: All downstream configurations are preserved. When a new connection is created on a node that has been previously configured, the resolution algorithms described above execute.

Hopefully you find these updates valuable. Please continue to leverage the forums on clarioanalytics.com and the support phone/email to submit your comments, questions, suggestions and concerns.

Matt
Co-Founder & CTO
clario Analytics