Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property enables the application of User Criteria records in place of Roles fields within the UX Framework, facilitating more tailored user experiences. |
| What area does it affect? |
UX Framework variants |
| What does the default mean? |
The default value is "false", which means this behavior is disabled by default. |
| When should you review it? |
Review this property when configuring user access and experience settings in the UX Framework. |
Out of the box property record
Raw metadata from the property record.
| Property name |
glide.ux.user_criteria_enabled |
| Sys ID |
623a47da73205010fd843c78caf6a772 |
| Type |
boolean |
| Application |
Global |
| Default value |
false |
| Description |
Enable use of User Criteria records instead of Roles fields for UX Framework variants. |
| Updated |
2024-05-25 03:54:36 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... to fit a specific role based on one or more criteria. For example, you could create an audience for an ITSM user in Europe who is not a manager. The glide.ux.user_criteria_enabled property needs to be set to true to configure access for users based on role, department, group, location, or company. See Enable the user criteria property, for more information. Set ...
Context preview
Snippet 2
... required tables, highlighted field records for migrations, and the migration process. Associated system property If ITSM Agent Workspace contains list modules that use group-based list applicabilities, then only enable the glide.ux.user_criteria_enabled property mentioned in the System Property [sys_properties] table. How the migration utility identifies list categories and modules for migration The Migration utility for SOW identifies the list categories and modules ...
Related properties