Risk are created in Retired state.

[HelloCAD]

I see that few risks were created in Retired state. When is this possible? Do we have a script that creates Risks in Retired state?

[aman_sharma_07]

Hi @HelloCAD ,

As per my knowledge in GRC, the risks associated with the entity gets retired most probably on these conditions:

   - Entity is no longer active in GRC.

   - Entity Type is itself not Activated (as mentioned by @Community Alums )

   - The respective Risk Statement (or Framework) is no longer applicable to the Organization.

Please note, there could also be some other criteria as well which can manipulate the risk state as retired (most probably a customization like Business Rule). So make sure to check them as well post your initial investigation.

Thanks for your read, if I'm able to resolve your query, please mark it as helpful 🙂.

[Rakesh Chigari]

@HelloCAD  There is no ootb business rule which create risk in retired state unless it is customized, and i dont see any use case where we create risk in retired state. 

[HelloCAD]

Hi All, @Community Alums, @aman_sharma_07 , @Rakesh Chigari 

Thank you for replying.

I was checking the Risk records on the dev instance, but the actual Risk records in Production were created in Draft state and were moved to Retired when the Entity was made inactive.

The Dev environment Risk record showed only the last activity and so it seemed that the Risk was created in Retired state.

Is it possible that during cloning, some records will only show the latest activity in sub-prod environments? 

[Community Alums · Accepted solution]

Hi @HelloCAD ,

Yes it's possible!!

[HelloCAD]

@Community Alums,

Why does this happen? Is this a known ServiceNow issue? Do you have any idea?