Idea to upvote - Use properties to manage entity ownership updates

[Jan Spurlin]

There is a feature in GRC that some customers view as a feature and some view as a challenge. I would like to see the product team make a system property to allow a customer to chose what they want to do.

Here is what is happening in the baseline - and why:

• When an Entity is created from a table in another record (source record), then the Entity owner is applied based on the Entity filter. Later, if the source record is changed to a different user - there is NO update to the GRC Entity record.
• Why? the logic is that when the entity is first created the owner is a suggestion and one that the GRC team may decide to override. When a change is made back on the source record at a later time, that might not be what the GRC team wants. More than likely the GRC team is not the group requesting the change to the source record.
• The same things happens between Entities and the Controls and Risks, but for a different reason. When a Control or Risk is generated, it inherits the owner from the Entity record. But if there is a change to the Entity record after the controls and risks are created, the controls and risks will not be updated.
• Why? Consider this scenario: Mary has been assigned a number of controls and has processed them. She has attested to the fact that a way to measure exists. She has responded to manual indicators and some of her controls are compliance and some are not. Now, Mary leaves the company. We don't (usually) want to automatically reassign all these controls to John - because it will look like he did the attestation and the assessment. He could be held accountable for the status of these controls.

Knowing this, we can create customization if the business reasons don't apply to our organization. However, I would love to have a system property that I can set that will turn these features on or off.

If you agree - could you go to this "idea" and upvote it?  And or add any comments to it.

https://community.servicenow.com/community?id=view_idea&sysparm_idea_id=8cbf03dd1b887010d46b62c4bd4bcbe2&sysparm_idea_table=x_snc_com_ideation_idea&sysparm_module_id=enhancement_requests

This our way to make sure the product development team is hearing what customer's want in the baseline.

Thanks!

Jan