---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Check UI action conditions before execution

# Check UI action conditions before execution {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Use the glide.security.strict.actions property to enable checking of UI actions conditions in forms and lists before they execute. When you set this property to
true, it adds an extra
layer of validation on the table UI actions before they are executed.

## More information {#sc-check-ui-action-conditions-before-execution__section_more_information}

{#sc-check-ui-action-conditions-before-execution__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Property name | glide.security.strict.actions |
| Configuration type | System Properties (/sys_properties_list.do) |
| Category | [Access control](https://servicenow-prod.fluidtopics.net/xAmazkRh5FKyeb7q4TQGWw "The access control category audits the process of protecting resources from unauthorized access through granting and denying requests based on a permission model. This includes ensuring an entity accessing a resource holds valid credentials to do so, creating and protecting a well-defined set of roles or permissions and ensuring role or permission controls are protected from replay and tampering.") |
| Purpose | To ensure an extra layer of validation on the table UI actions before they are executed. |
| Data type | Boolean |
| Recommended value | true |
| Default value | true |
| Security risk rating | 3.3 |
| Functional impact | This remediation only adds an extra layer of validation to check for UI actions on the target table/page on the instance. As long as the access controls are set appropriately on the customer instance, there should not be an impact here. |
| Security risk | (Low) Access request is always checked when transactions happen between two zones. This operation validates any UI actions before the form renders for the end user. |
| References | [High security plugin](https://servicenow-prod.fluidtopics.net/bj_jKmHWfChG2IBu_4WVEA "When you activate the High Security plugin, it creates or updates hundreds of different configurations to control the level of security on your instance. These configurations mitigate many of the top OWASP attacks by enabling strict access control, input validation, and output encoding.") |
[ ]

{#sc-check-ui-action-conditions-before-execution__table_ajc_b43_3kb}

To learn more about adding or creating a system
property, see [Add a system property](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=australia&pubname=australia-platform-administration&ft:locale=en-US).