Different sys_popup per view

[raulron]

Hi,

i know how to customize the sys_popup for reference fields. however, a requirement came up to have different content in the sys_popup in different cases.

For example, when i look at requested items lists, on one list the popup should include some fields, on another, it should include other fields,

The main difference between those lists that i can use as an indicator is that they are defined for different views. one is the default view, and another is a view i have created.

anyone knows how this can be achieved?

Thanks.

[bcronrath]

Hello Chandresh,

My solution is pretty hacky, but what I did was just filled the sys_popup with a bunch of fields, and created ACLs to restrict how the fields show based on the user.   Was hoping there might be a better way but this was the best I could come up with.

[Chandresh]

Thank you Brian for the response, though I considered that option already and since there are lot of fields in my table so this option will be too tedious.

[kobby_adu-nti]

Hello Chandresh,

Actually you can see that there are several sys_popup view records that are configured to only display with specific views   OOB. Try opening the following URL on your instance:

https://<yourInstanceName>.service-now.com/sys_ui_view_list.do?sysparm_query=nameLIKEsys_popup

Service Now has not produced any official documentation to instruct our end users on how to configure sys_popup views that display only with particular form views. However following the instructions below you will find a workaround that is well suited to your business requirement.

• Form view specific OOB sys_popup sys_ui_view records use the following naming convention to be identified:

                  Name: sys_popup,<viewName>

• As an example of how this would work take an OOB instance and navigate to the incident table, there you will find we have a view named "portal". Therefore if you wanted to create a unique sys_popup for the portal view you would name it sys_popup,portal

• You can create your own view record following the convention above. For instructions on how to create a new view please see the link below

                  View Management - ServiceNow Wiki

                 

• Instead of configuring your new sys_popup view It would be advisable to configure the standard sys_popup view following the directions on the product wiki.

                  Customizing the Reference Icon - ServiceNow Wiki

• However after you have modified the default sys_popup view navigate to sys_ui_view table and find the record named "sys_popup". Open the record, there you will find a "Form Sections" labelled section, Locate the section record with the heading for the table where you modified the sys_popup view, for instance the "incident" table. Open the "Form Section" record and alter the view from "sys_popup" to "sys_popup,portal". Finally update the record.

• Taking the example above, if you traverse to the incident table in a default list view you will see the default unmodified sys_popup when hovering over the reference icon. However, if you change the list view to "Portal" you will see the modified preview

[Inactive_Us2219]

I just had a HI incident on this subject and thought it may help this discussion, because I found several helpful items from the above post.

Issue was when trying to view the reference Icon for Stories it would not show the Default info, just the Notes section.   Here's Service Now analysis/solution.

Issue:

The rm_story list was not showing the expected popup view when hovering next to a story record. Instead of the Default view popup, users are seeing only the "Notes" section for the form.

Analysis:

- OOB "rm_story functions" business rule is applied to the rm_story table. When opening an rm_story record, the Scrum view will be shown. This also applies to the popup that is seen when hovering over the reference icon. Since the forced view that is seen is Scrum of the rm_story form, when hovering, the scrum view is shown in the popup as well.    

- I've observed that in the form section related list of the "Scrum" view, the "Notes" section was listed on top and none of the Title fields for each section record were set to true. The Title field defines the section that is considered the top form section and that is the section that is seen when hovering over the reference icon. Since none of the form sections had a Title value of true, the first form section that appears in the list is the section that is shown. This is why it was picking the "Notes" section by default as it was on the top in the list.

Root Cause:

In the "Scrum" view, the default/blank (position 0) section title was not set to true

Solution:

Set the default/blank (position 0) section Title field in your scrum view for rm_story to true rather than false

Hope this helps anyone that has stumbled on this thread.

-Aaron

[Inactive_Us1705]

That was a very interesting and insightful reply there. Well it helped me out and also go me understanding the Views more and more importantly explained what those sys_popup,<view_name> records were.

Thanks very much, much appreciated.

Snake