Inherit from risk statement becomes read-only

[Momiji]

Hello! I hope you could help me out. I cannot find the configurations behind this. Do you have any idea why the 'Inherit from risk statement' checkbox become read-only after creating a risk?

[Community Alums]

Hi @Momiji ,

Inherit from risk statement , If this option is selected, the risk creation happens in the previous manner. This means that there can be only one instance of risk statement and entity combination. However, if this option is not selected, the system allows the risk statement hierarchy to be used as categorization and sub-categorization hierarchy and associates multiple risks to the same risk statement and entity combination. This option also enables the first line to associate their newly identified risks to the risk hierarchy at a level they want to. When this new option is not selected, the system assumes that the name and description of the risk is overridden and must not be the same as the risk statement name and description.

This Checkbox is always true for Advanced Risks i believe and it's open for Classic Risks.

[Momiji]

Thanks for your response @Community Alums . But my concern is about being not able to uncheck it (since the checkbox is already read-only) once the risk form is saved during creation.

I'm just wondering since we used the load data to import bulk risks and risk statements. And when we checked the imported risks, the 'Inherit from risk statement' checkbox was automatically checked.

[Community Alums]

Hi @Momiji ,

As i told on the previous reply, it's enabled in Classic risks not for Advanced risks.

[HenkHeath]

Hi @Momiji 

Maybe check the value you have in the property sn_risk.risk_statement_mandatory