QUESTION: Tell me about the new NoetixViews Workbench.
ANSWER: NoetixViews Workbench is a new product from Noetix that makes it easy to create and manage customizations to Noetix views. It provides a tremendous leap forward in simplifying that process for Noetix customers.
NoetixViews Workbench supports:
- Making the most common customizations through a wizard-based user interface. Features include adding, modifying, or suppressing columns, adding or removing tables in a view, and adding, modifying, or removing where clauses from a view.
- Modifying the properties of a view or its columns, including view essays, column descriptions, and links for joining to other views.
- Adding an entirely new view using the SQL code that defines that view.
- Managing all of the customizations that have been created, including deploying them independently to multiple environments (such as Development, Test, and Production).
In my last column, I discussed the way in which NoetixViews is based on metadata. One benefit of that metadata-based design is realized when a view is modified. Rather than changing the view code itself, the administrator changes the metadata entries that define the components of the view.
Prior to the release of NoetixViews Workbench, customers needed to write SQL code using the NoetixViews Software Development Kit (SDK) to make those changes. While that process was extremely powerful, it could often be tedious. With the launch of NoetixViews Workbench, the entire customization process is now much easier. In addition, because of the customization management features of NoetixViews Workbench, it’s much easier to keep track of the changes that have been made.
We are very excited about this new product and expect that it will greatly increase the value that every customer gets from their Noetix investments. Feedback from all of our early adopter customers confirms that those high hopes will be realized. We look forward to sharing this exciting new product with you.
Submit a question to Noetix and check back for the answer in an upcoming blog post!