Why are there duplicate Related List items available for the Entity Type module? [OOTB]

spacecowboy · ‎11-06-2019

[OOTB] I noticed that the Related Lists for the Entity Type form contains duplicate items. These duplicate items are illustrated in the screenshot below. What purpose do these duplicate items serve?

Dexter Parre_o · ‎11-06-2019

There are two fields labeled as Profile Type in the control and risk tables, both of them inherited from their parent table sn_grc_item. The first one is source_list (List type) and the other one is profile_type (Reference type). See below:

By default, the two fields are not shown in the form. Also, by default, only the source_list is populated when a control/risk is created by adding a profile type to a risk statement/control objective.

The two similar related lists that you see for Control, Risk, and Control/Risk when you configure the related list has different queries. If you would display one pair of both similar related list, open a profile type and go to the related list's filter and right-click on it and select 'Open new window':

You would notice that the first related list has a different query from the second:

https://devxxxx.service-now.com/sn_risk_risk_list.do?sysparm_query=source_list%3D6305c264dbd3330045c6e9c948961956%5E

https://devxxxx.service-now.com/sn_risk_risk_list.do?sysparm_query=profile_type%3D6305c264dbd3330045c6e9c948961956%5E

The first one queries all risks/controls whose source_list is the profile type indicated, while the second one will show all risks/controls using the profile_type value as the filter. Since OOB, the profile_type field is not auto-populated, then the related list is normally empty.

View solution in original post

Phil Swann · ‎11-06-2019

The control table has two fields which reference the Entity Type , in source and source_list field

As control and risk both extend the sn_grc_item table, I refer to these equally as 'Items'

Control objective and Risk statement both extend sn_grc_content table, I refer to these equally as 'Contents'

When an Item is generated by mapping an Entity Type to a content - the system knows where they came from by maintaining the source_list field. I think the source field is obsolete as this is a reference, and source_list is a list.

In this way, if an entity (say Business Service A) belongs to two Entity Types. They are both mapped to Control Objective 101...this will only create a single Control, but it would have two sources. Thus, if one is unmapped - the Control remains active, until the 2nd is unmapped..

The other two you highlighted Control/Risk , I would need to double check but I expect it can be explained with a little investigation.

Notorious BFG · ‎11-06-2019

Oh man you beat me to it again Phil! I was trying to answer a few of these in the queue while my SNPI students are doing their lab and I thought _for sure_ that I'd get to this one first. Well played sir.

Phil Swann · ‎11-07-2019

sorry!! 🙂

spacecowboy · ‎11-12-2019

Thank you Phil. Apologies for the delayed gesture. I appreciate your fast response.