Most system properties with "empty" or blank value evaluate to the default value instead of being ignored
Sometimes attempts to remove some system property records are made empty to force the system to ignore them. However, if it set to blank or "empty", in most cases the value takes the default value, for example, glide.email.forward_subject_prefix. If the value of the property is empty or is not preset, it takes the value of "fw:,fwd:".
|Sys_properties value||If empty or blank||Default value||If you want the property ignored|
|glide.email.forward_subject_prefix||Default value||fw:,fwd:||Set it to value that does not match the forward suffix|
|glide.email.reply_subject_prefix||Default value||re:,aw:,r:,Accepted:,Tentative:,Declined:||Set it to value that does not match the reply suffix|
|glide.security.url.whitelist||Ignored||empty||Empty the value|
|Warning: Do not delete sys_properties records. Instead, set the property to a value that avoids the unwanted behavior. Deleting one property could cause only one node to have a blank value (which takes the default value) and the other application nodes would have the cached old value. If this occurs, create the property again and set it to a value that does not match.|
This problem occurs when:
- You have set the a system property value to blank or "empty" and the default is still used.
- You have deleted the sys_properties record.
- You have set the system property from blank or "empty" to another value but the application nodes have not refreshed the cache.
System property values are parsed and used by the application nodes. Each module or part of the application interprets blank and empty values differently. A general rule is that properties (for example, glide.email.forward_subject_prefix) usually take the default value as if they do not exist.
Set the system property value to a value that does not trigger the unwanted behavior.
For example, to avoid email suffixes being recognized:
- Set the glide.email.forward_subject_prefix value to "xxxrandomtextxxxxx:"
- Flush the instance by going to /cache.do or wait for the cache to be flushed automatically.
- Validate that the property is not matched any further.