Workbook functionality has been steadily removed from Workspace over the past several releases. I can no longer view/edit rules, processes, chores, or the set editor in a widget. Instead I am forced to use workbenches which are completely different from workbooks and lack the ability to add textbox widgets or multiple objects on one tab (among many other things).
I spent a long time building a ton of administrative workbooks that had textboxes for notes and step-by-step instructions with tabs with multiple objects on them for updating related rules, processes, chores, etc. It was so convenient to have everything in one book for a given task. It was honestly the best part of PAW for me. Now the workbooks are only about 30% effective. I thought I would just add a navigation button from the workbook to the workbench with the other objects, but apparently only navigation to workbooks is allowed.
Users: I'd be interested to know if I'm the only user frustrated by this deprecation or if others are feeling the same way. Is it just me or does workbench leave you feeling like it's just not as useful as workbooks?
IBM: It might help me deal with this loss if I can understand why this direction was taken. I understand tasks performed by modelers vs consumers are different, but couldn't that just be addressed by subscription appropriate context menus or trees instead of limiting modelers to be forced to workbench which is limited in many ways compared to workbooks? Is the plan to add a ton more functionality to workbenches and if so, why force the switch before it's ready?
In case you're wondering, I'm a cloud client, so I can't continue to use the older version.
------------------------------
Kirk Stolworthy
------------------------------
#PlanningAnalyticswithWatson