Enable a way for New UI to only present configured fields given a set of conditions

Greg 2 months ago in Digital Asset Management updated 1 month ago 4

A current advantage of the Assets Studio is that you can selectively choose what field groups appear for an asset based on what classification/classification tree they are a part of.  In the New UI, any field you configure in each content type will always show up for every asset.  We need a way to configure the environment to more selectively show metadata so end users are only presented with what is more relevant.  I could think of two potential solutions while testing.

1. Enable the classification Logic in Assets studio to affect the New UI: If the asset in New UI is classified in a classification that does not have the field group registered, the fields will not display even if they are configured in New UI.

2. Alter the functionality of the showEmpty attribute: When reading through the admin guide I thought by setting the container level showEmpty to False, and every item level showEmpty to True, the following two use cases would be solved, that ultimately creates this Voice requests use case.
- All items within a container, filled in or empty, will display as long as at least one of the items has a value.
- the entire Container along with all it's items to not display, If And Only If, every single item within that container is blank

UX Fields / Attributes

Will keep it on shelved at the moment to see if there is interest from other customers.

Hey Petra,

I've been working through some of my old requests, and came up with an alternate solution to this one.  Instead of setting conditions on a system level to dictate the fields that are visible, we can allow for the custom field configuration by space.  I thought of 2 ways to accomplish this.

1.  the field configurations could be templatized, and you could choose the template you want to use by Space.

     Pros:  It's convenient, and allows for customization by space
     Cons:  It would limit you to the templates themselves unless it could sophisticated enough to allow you to edit the             template after applying it to the space

2.   You could configure more customized field displays on the field config page.
      Pros:  You can attain a higher level of precise customization for a more personalize experience.
      Cons:  It would take more work, and require more complex maintenance as things change and require updates.

Let me know what you think.

You are able to see additional details around this use case, particularly the attempts to configure showEmpty, in ServiceNow Case - CS0027942.