Property reference

`glide.security.strict.updates`

Double-checks security for inbound form submissions and field updates. With the default value of true, updates require appropriate permissions rather than relying only on field visibility.

Default: true
Type: boolean
Application: Global
Category: Security & Access Control

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do?	It enforces strict security validation for inbound transactions during form submissions, ensuring that user permissions are verified.
What area does it affect?	Form submission security
What does the default mean?	The default value is "true", which means this behavior is enabled by default.
When should you review it?	Review this property when configuring security settings or troubleshooting form submission issues.

Out of the box property record

Raw metadata from the property record.

Property name	`glide.security.strict.updates`
Sys ID	`52276a9b0a0a0b6b00a2f9e59d8cb959`
Type	boolean
Application	Global
Default value	`true`
Description	Double check security on inbound transactions during form submission (rights are always checked on form generation)
Updated	2024-05-25 04:02:01

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs Available system properties ↗

Context preview Snippet 1

... timed-out Ajax requests. • Type: true | false • Default value: true • Location: Add the property to the System Property [sys_properties] table. glide.security.checkacl.before.setvalue Controls how the high security setting glide.security.strict.updates processes ACLs. When true, the instance checks ACL rules for all columns before applying any updates to a row. When false, the instance applies ACL rules as each column is ...

Brazil docs Double check inbound transactions ↗

Context preview Snippet 2

... company names, product names, and logos may be trademarks of the respective companies with which they are associated. 216 Documentation Updates proper permissions are allowed to update a form. If "glide.security.strict.updates" is not set to the recommended value of "true", then updates are not strict meaning they are able to modify fields visible to them regardless of whether they have the ...

Additional source link Another external reference for this property

Open reference

More in `glide.security`

Other properties in the same namespace.

glide.security.scripting_governance.enabled This property restricts script authorship to authorized users, ensuring that only those with the script-writer glide.security.scripting_role.auto_provisioning This property determines whether a scheduled job runs to automatically update group memberships for the Condit glide.security.scripting_role.provisioning_job_running This boolean property tracks the status of the initial provisioning job for Scripting Governance, affecting us glide.security.strict.actions It requires conditions for UI actions to be validated before execution, rather than just during form rendering glide.security.strict.user_image_upload This property enforces table ACLs on image uploads to the Photo field, restricting uploads to authorized users glide.security.strict_elevate_privilege This property enforces strict privilege elevation requirements for 'admin' role users, enhancing security by c glide.security.url.whitelist This property restricts external URL redirection based on a defined whitelist, enhancing security by preventin glide.security.url.whitelist.strict_check This property restricts external URL redirection based on the configured allowlist, preventing unauthorized ac

All 64 properties in glide.security →