Change RISK APPETITE SCALE - deactivate and create new? or modify existing?

[Don Dom]

Hello.

This is OOTB Risk Appetite Scale:

Inside a see a warning: Warning: This is a Medium Risk file that might get updated again in later releases. Do not alter this file unless necessary.

Because of the update and upgrade I would like to DEACTIVATE this one and create 5 new.

While I try to deactivate I see popup with warning.

We do not have ANY published RAM yet and those which was published are now back to DRAFT - so no active assessments.

Is it safe or what is the best practice here - can I deactivate the 5 OOTB because in case of update/upgrade they will not be touched, and create 5 new or should I update the 5 OOTB ones?

I did it in the PDI and I see system created 1 additional PROPERTY inside my Update SET:

The update set I want to move TEST and then PROD. It will not break something ?

Please advise the best option.

Thx

WD

[jaikishan1 · Accepted solution]

Hi @Don Dom ,

The warning indicates that if the file is modified, any further updates would not be available for the customer. Even if you deactivate it, it would be treated as a customisation and the further updates would not be available.

You can follow any approach of 
1. Updating the current records
2. Deactivating the existing records and treating them as backup and creating new records.

If the customer wants any future updates, the customer would need to revert the customisations, upgrade/update the application files and then reapply the customisations.

Regards,
Jai

[jaikishan1 · Accepted solution]

The appetite scales are used the configure the rating criteria for the assessments(inherent,residual etc) defined under the RAM.
If you wish to change the appetite scale, the rating criteria should also be mapped to the new appetite scales.
There is no other dependency on the appetite scale.

[jaikishan1 · Accepted solution]

You can update the existing records without necessarily deactivating and creating new records. You can take either approach.

The impact in both cases would be the same i.e. you would not receive any update for these files on app upgrade due to customizations.
To receive future updates, you must revert the customizations and upgrade the app.

[jaikishan1 · Accepted solution]

Hi @Don Dom ,

The warning indicates that if the file is modified, any further updates would not be available for the customer. Even if you deactivate it, it would be treated as a customisation and the further updates would not be available.

You can follow any approach of 
1. Updating the current records
2. Deactivating the existing records and treating them as backup and creating new records.

If the customer wants any future updates, the customer would need to revert the customisations, upgrade/update the application files and then reapply the customisations.

Regards,
Jai

[Don Dom]

I would ask rather is it a good approach to deactivate it and just create 5 new appetite records instead of modifying existing - because I do not know are there any dependencies below.

[jaikishan1 · Accepted solution]

The appetite scales are used the configure the rating criteria for the assessments(inherent,residual etc) defined under the RAM.
If you wish to change the appetite scale, the rating criteria should also be mapped to the new appetite scales.
There is no other dependency on the appetite scale.

[Don Dom]

I'm sorry my totally bad explanation - I do not want to change a scale. 
I need to change name example:

1 - Averse in to 1 - Negligible  (Value and display order still will be 1)


but because of those "warnings" during "un-activation" I was not sure If I can just RENAME "1 - Averse" or I should first "Deactivate" 1 - Averse and create "1 - Negligible" as a new record.

I'm sorry for confusion. I just want to be sure that during update/upgrade the OOTB records like "1 - Averse" are ok but system still works with new "names" records.