The json editor to edit policy must be more open when we modify values with Json Edit.

Currently it enforces to enum defined in the UI.

 

Edit:

This is unfotunately impossible to fix with the current implementation of the JSon editor lib (it supports Json Schema V3/v4. It could be done with a Json schema V6 as it supports the key examples:

{ "title" : "Match anything", "description" : "This is a schema that matches anything.", "default" : "Default value", "examples" : [ "Anything", 4035 ] }

This could be used instead of the enum keyword, so that the value will not be enforced.