Updating description of my Risk Statements moves retired risks back to draft

[JH4]

When I went in to update the description of Risk Statements, it moved all retired risks that inherits that risk statement back to draft mode.  I don't understand why it did that.  Please assist.

[Community Alums]

Hi @JH4 ,

Not to worry, this is a OOTB behavior. it's just not only the Description field but other fields like Name, Category, parent, Additional information, if you make any changes to these fields in the Risk Statement then the associated Retired Risks would go to "Draft" state.

This Happens due to a Business rule running in the backend called "update root of a risk statement" .

[Sebastien Fix]

@Community Alums @JH4  The Business Rule is NOT "update root of a risk statement" but "Cascade Changes". It will change every Risk record from whatever state is it in back to Draft (see screenshot for script reference). This is not dramatic for Retired Risks but is for Risks which are in Monitor state since you then have to reperform a Risk Assessment for all of them. 

The same BR exists against Control Objectives; and I would suggest to modify it to provide better control over the consequences of people updating one comma in one field 🙂

[Community Alums]

@Sebastien Fix  Apologies i din see that , you are right it's "Cascade Changes"

[JH4]

I think what you're noting addresses my issue.  However, I don't understand what you mean by:

"This is not dramatic for Retired Risks but is for Risks which are in Monitor state since you then have to reperform a Risk Assessment for all of them. 

The same BR exists against Control Objectives; and I would suggest to modify it to provide better control over the consequences of people updating one comma in one field"

Can you please clarify?  So if I make a correction to a misspelling for example in Description, I wouldn't want it to put all of the Retired risk back into Draft mode.  Thus, what should I do to address that?  Otherwise, when it is put into Draft mode, it causes confusion when we've already agreed with the risk owner that those specific risks should have been retired already. 

This seems to be the out of the box functionality and I can understand it if you're making a significant update that needs re-evaluation, but a misspelling shouldn't put this back to draft.  Thanks.