Help with proper setup of CMDB - Workspace view

[Travis Michigan]

We are looking to the CMDB Workspace to try and make use of it, and I am trying to add some functional views for some of the forms that don't default with a CMDB - Workspace view.  I created one for cmdb_ci_endpoint_db2sql under cmdb_browse so it would work like those there originally.  However it seems to still pull up those I create, like cmdb_ci_endpoint_db2sql with the default view instead of the newly created CMDB - Workspace.  Whereas ones that already had a CMDB - Workspace view show that specific view when I bring them up in the workspace.  Is there something else I need to adjust to get these to default to the view with more options within this workspace?

Anyone have any tips for how I should be doing this?  Or if I'm on the completely wrong path, some more direction would be appreciated.  Thank you!

[Manuel Stimac]

Hi @Travis Michigan, 
I am on the same page... have you found a proper solution to create the views?

regards,

Manuel

[Travis Michigan]

I have gotten this to work for the most part, sometimes there is some cleanup in the scopes that I'm not quite certain about so I wonder if I am doing part of this incorrectly but yeah here are the basic steps I do now:

Go to System UI > Views.  Make sure you are in the CMDB Page Template Scope.  Look through the list for cmdb_browse (name) CMDB - Workspace (title) and open it.
You will see a list of tables on the Forms tab.  Click on the New button to add a new one (if you don't see the button you are in the wrong scope).
Select the table and then click on Submit.
Next you will need to go to Workspace Experience > Forms > Workspace View Rules and click on New.
Pick a name for the view rule (usually "table-name - browse") and I uncheck the Experience Restricted Checkbox, not sure if you will need to or no.
Open the View Rule you just created, down below you will want to click on Edit and add a UX View Rule Configuration (CMDB Workspace View Rules).
At this point some of them are complete and functional (It will create the form to be similar to the Default View) so if you had that close there shouldn't be much to adjust but you should ensure you can Configure the Layout properly.

However I have run into a couple of problems to double check.  For some reason if you go back to the cmdb_browse in the System UI > Views, and look through the table list, there will sometimes be a duplicate for the table just created.  If this is the case you will need to remove one of them.  One but not the only reason is if it allows you to create that in the wrong scope which I have done a couple times, but also I have ended up with duplicates that are both the CMDB Page Template scope and I'm uncertain what I do that causes that.  I hope this helps out!

[Manuel Stimac]

Hi @Travis Michigan,

thank you for taking the time to describe the process in such detail! It helped a lot! I was able to create the view and the rules as expected. 

What I really struggled with, was the fact that there were some form sections in different scopes on the same form which results in always "read-only" mode in the form designer. Took me some time to realize. I simply deleted all the sections and built the form from scratch. Maybe this will help some fellers coming after us 😁

Why is this not created for all ci classes OOTB?!

regards,

Manuel

[Tony Branton]

There are over 800 CI classes so creating a form view for every one is impractical.  CMDB Page Templates offers OOTB support for a number of CI classes, and then a generic layout for the rest. It's possible to use the CMDB - Workspace form view to change the fields displayed in the attribute sections, and modify which related lists are displayed for a particular CI class.

As @Travis Michigan described (excellent work there!), more fine-grained control is possible within the CMDB Page Templates application scope.

We're currently designing a new CI form UX to replace the current form layout in CMDB Page Templates that we hope to release with CMDB Workspace sometime in 2025.