It is my understanding that entities can be related to a Configuration Item (CI), such as a Service, Application, individual Server, etc (basically anything in the CMDB)
In Nigels case the CI is the Pegasus Service Offering, and the Risk Statement is the same for each Risk Nigel wants to add.
This is the information provided by the Service Now expert in our organization:
I don’t believe this is the correct approach. I believe that each Risk record relates to a unique combination of Entity and Risk Statement and therefore we should not be providing a workaround, and instead we need to look at why there are in effect duplicate Risks.
The challenge is that Pegasus has multiple suppliers and there is a support risk statement related to 2 of the suppliers. These are not duplicate risks but risks against the same CIs for different suppliers. Each would need to be tracked separately.
Also, should entities and CIs be identical?
What is the best way to make this happen? We have quite a few cases such as this.
