Category · 370 properties

ServiceNow ITSM: Incident, Problem & Change properties

These properties configure behavior across ServiceNow Incident, Problem, and Change processes, including settings associated with change conflict handling and related namespaces such as change and com.snc. Admins and developers can consult them when reviewing or adjusting system behavior, investigating configuration issues, or documenting how an instance is set up; examples include change.conflict.blackout and change.conflict.assigned_to.

Most common namespaces: com.snc 122 evt_mgmt 47 change 40 sn_devops 21 glide.ui 15 Other namespaces 11

`change.conflict.allow_contiguous_changes`	This property enables or disables conflict checking for change requests that overlap in timing, allowing for more flexible scheduling of changes.
`change.conflict.assigned_to`	This property enables conflict checking for change requests assigned to the same user, helping to avoid overlapping schedules.
`change.conflict.blackout`	This property enables or disables the consideration of blackout windows in change request conflict checks.
`change.conflict.ci_maint_sched`	This boolean property checks if a change request conflicts with the CI's defined maintenance schedule when assessing change conflicts.
`change.conflict.conflict_last_run.update`	This boolean property controls the update behavior of change requests during conflict checking, ensuring only the current record is modified.
`change.conflict.consolidated_conflicts`	This property determines whether conflicts are consolidated based on unique combinations of conflict type and schedule, reducing redundancy in conflict registration.
`change.conflict.currentci`	This property enables conflict checking for change requests against existing scheduled changes for the same CI, helping to prevent overlapping changes.
`change.conflict.currentwindow`	This boolean property specifies whether change requests should be checked for conflicts within the CI's maintenance window.
`change.conflict.execution.log`	This property configures the logging level for ChangeConflictExecution, with a default setting of 'Notice' to capture important events.
`change.conflict.handler.log`	This property configures the logging level for the ChangeConflictHandler, influencing how much detail is captured in logs about change conflicts.
`change.conflict.identifymostcritical`	This boolean property determines whether the system identifies the most critical service affected by configuration item conflicts, helping prioritize resolution efforts.
`change.conflict.information`	This property enables or disables the display of information windows during change request conflict checks, enhancing user awareness of potential issues.
`change.conflict.lockdown`	It activates the evaluation of Change Lockdown records during conflict detection for change requests, ensuring compliance with scheduled lockdown periods.
`change.conflict.log`	This property configures the logging verbosity for ChangeCheckConflict, allowing for different levels of detail in the logs.
`change.conflict.max_count`	This property specifies the maximum number of conflict records created per conflict type during conflict detection, ensuring efficient management of conflicts.
`change.conflict.mode`	This property configures whether the conflict check for changes is basic, which checks only the change's CI, or advanced, which checks all related affected CIs.
`change.conflict.next_available.choice_limit`	This property defines how many scheduling suggestions the Conflict Scheduling Assistant will calculate, impacting the response time based on the chosen limit.
`change.conflict.next_available.schedule_window`	This property sets the timeframe in days for identifying potential conflicts with other changes based on their planned start dates.
`change.conflict.populateimpactedcis`	This property enables the automatic inclusion of related business or application services for CIs with conflicts in the Impacted Cis/Services list, enhancing visibility during change assessments.
`change.conflict.refresh.conflicts`	This property triggers conflict detection automatically when changes are made to key attributes of a change request, such as the configuration item or planned dates.
`change.conflict.refresh.scheduled`	This property activates a scheduled process that checks for conflicts among changes, helping to prevent issues during implementation.
`change.conflict.relatedchildblackout`	This boolean property enables conflict checks for change requests against the blackout periods of child configuration items.
`change.conflict.relatedchildinformation`	This property enables the system to check for conflicts in change requests by including the information windows of child CIs.
`change.conflict.relatedchildwindow`	This boolean property enables conflict checks for change requests against the maintenance windows of child CIs, enhancing change management accuracy.
`change.conflict.relatedparentblackout`	This boolean property enables conflict checks for change requests against the blackout periods of parent CIs, preventing changes during critical maintenance times.
`change.conflict.relatedparentinformation`	This boolean property enables conflict checks against parent CIs' information windows during change request evaluations.
`change.conflict.relatedparentwindow`	This boolean property enables conflict checks for change requests against the maintenance windows of parent CIs, enhancing change management accuracy.
`change.conflict.relatedservices`	This property enables the system to check for conflicts in change requests based on maintenance or blackout periods affecting related Application Services.
`change.conflict.role`	This property defines a comma-separated list of roles that can access the conflict detection feature, ensuring they have permissions for the underlying change_request record.
`change.conflict.show_conflict_message`	This property determines whether a message is shown to users when a scheduling conflict arises during change request processing.
`change.conflict.usecomposed`	This property enables or disables the use of composed IN queries for checking conflicts in change requests, impacting how efficiently conflicts are identified.
`change.conflict.useprogressworker`	This property configures the use of Progress Workers for managing conflict detection during change processes, allowing for legacy behavior if enabled.
`change.mass_update_ci.remove_affected_ci`	Enabling this property ensures that all Affected CIs are removed from a Change Request when the Mass Update CI Class field is changed to false.
`change.refresh_impacted.include_affected_cis`	This property controls the inclusion of affected configuration items in the impacted services list during change record updates.
`change.request.extension.period`	This property specifies the number of minutes for the extension period of change requests, impacting how long changes can be delayed.
`change.risk.enable_view_details`	This property enables or disables the display of detailed risk calculation results through a popover and modal interface.
`change.risk.show_calculated_risk_score`	This property controls the visibility of the Calculated Risk Score in the change management interface, ensuring users see risk assessments when applicable.
`change.risk.show_risk_assessment`	This property configures the visibility of Risk Assessment results in the change management interface based on the assessment's completion status.
`change.risk.show_risk_condition`	This property configures the visibility of risk condition results in the change management interface based on the selected display option.
`change.risk.show_risk_intelligence`	This property controls whether the results of Risk Intelligence execution are shown in the 'View Details' modal, depending on the solution's ability to predict risk.
`cmdb.recent_outages.days_ahead`	This property configures the time frame for displaying future outages in the system, defaulting to 14 days.
`com.glide.cs.enable_auto_resolution`	This property activates the auto-resolution feature, allowing the system to automatically resolve incidents and requests based on predefined criteria.
`com.glide.cs.rich_converter_incident_html`	It configures the HTML layout for incident records, affecting how details are visually presented in the ServiceNow interface.
`com.glide.cs.task.transaction.enabled`	This property controls whether task transaction processing is active, impacting how tasks are managed within the system.
`com.glide.journal.new_changes_behavior`	This boolean property configures the behavior of change logging in the journal, impacting how modifications are captured and displayed.
`com.sn_rf.rule.52bbd85c07450110b34ce06b0fd30008.active`	This boolean property determines whether alerts can be repeated, impacting how notifications are sent to users.
`com.sn_rf.rule.6760441a07050110b34ce06b0fd3009f.active`	This boolean property activates incident creation for alerts associated with related CIs, enhancing incident response in the Service Operations Workspace.
`com.sn_rf.rule.7db9989807450110b34ce06b0fd300c4.active`	This boolean property activates the generation of similar alerts, enhancing alert visibility and management.
`com.sn_rf.rule.cdebdc5c07450110b34ce06b0fd30044.active`	This boolean property determines whether incidents are created for alerts associated with Configuration Items in the Service Operations Workspace.
`com.snc.change_management.change_model.default_read_roles`	This property specifies a comma-separated list of roles that are permitted to read change model records, impacting visibility and access control.
`com.snc.change_management.change_model.manage_workflow`	It activates workflow management for ChangeRequest API, allowing the system to execute the 'deleteDefaultWorkflowContext' method during certain state and type transitions.
`com.snc.change_management.change_model.type_compatibility`	This property activates Change Type Compatibility for Change Models, allowing changes to utilize both type-based workflows and Change Models if the necessary plugin is installed.
`com.snc.change_management.change_request.enforce_user_on_group_change`	It ensures that changes to the Assignment Group are only allowed if the assignee is included in the new group, preventing unauthorized changes.
`com.snc.change_management.change_task.enforce_user_on_group_change`	When enabled, it ensures that changes to the Assignment Group are only allowed if the assignee is included in the new group, preventing potential misassignments.
`com.snc.change_management.enforce_data_requirements`	It mandates that all updates to the Change Request table comply with defined data requirements, applying restrictions through multiple update channels.
`com.snc.change_management.lockdown.preview.max_changes`	It limits the number of change_request records shown in the Preview Lockdown Change Requests modal to a specified integer value.
`com.snc.change_management.risk_conditions.match_all`	This property configures whether to evaluate all risk conditions or just the first match, impacting how risks are prioritized in change management.
`com.snc.change_management.success_score.entry_level_score`	This property specifies the numerical entry-level score used in assessing change management success within the system.
`com.snc.change_management.success_score.maximum_score`	It defines the maximum permitted team score used in success score calculations for Change Management.
`com.snc.change_management.success_score.minimum_score`	This property defines the threshold score for determining the success of change management processes within the system.
`com.snc.change_request.associate_by_ci_class_type_extension`	This property enables or disables the association of change requests with configuration items according to their class type extensions, impacting how changes are tracked and managed.
`com.snc.change_request.auto.discovery`	This property determines how Discovery is initiated for Affected CIs, allowing options for automatic, manual, or no triggering.
`com.snc.change_request.copy.attributes`	This property defines a list of attributes that are automatically copied from the originating change request to new change records.
`com.snc.change_request.copy.related_lists`	This property specifies a comma-separated list of related lists that will be included when a change request is copied, impacting data continuity.
`com.snc.change_request.copy.rl.change_task.attributes`	It specifies a comma-separated list of attributes that will be copied from the Change Task related list when a change request is created.
`com.snc.change_request.copy.rl.task_ci.attributes`	It defines a comma-separated list of attributes from affected CIs that are copied when a change request is created.
`com.snc.change_request.copy.rl.task_cmdb_ci_business_app.attributes`	It defines a list of attributes that are copied from the Business Applications related list when a change request is processed.
`com.snc.change_request.copy.rl.task_cmdb_ci_service.attributes`	It defines a list of attributes to be copied from the task_cmdb_ci_service related list during the creation of a change request.
`com.snc.change_request.copy.rl.task_service_offering.attributes`	It defines a list of attributes from the task_service_offering related list that are copied from the originating change request.
`com.snc.change_request.disco.auto.state`	This property configures which Change Request states will initiate automatic Discovery processes, facilitating the management of configuration items associated with change requests.
`com.snc.change_request.disco.manual.state`	This property defines a comma-separated list of Change Request states where Discovery can be manually initiated, impacting how changes are managed.
`com.snc.change_request.disco.topdown.state`	This property specifies the Change Request state that activates Top Down Discovery, defaulting to 'Review'.
`com.snc.change_request.enable_copy`	This property allows users to copy existing change requests, facilitating easier management of similar changes.
`com.snc.change_request.enable_unauthorized`	This property enables or disables the ability to create unauthorized change requests within the ServiceNow platform.
`com.snc.change_request.event.state_updated.enabled`	It controls the generation of an event that triggers when a Change request's state is updated, facilitating better monitoring and automation.
`com.snc.change_request.event.state_updated.states`	It specifies which Change request state values will generate the 'sn_change.state.updated' event when changed, allowing for targeted event handling.
`com.snc.change_request.next_create_page`	This property activates the next experience interface for change request creation when Polaris is enabled, improving user interaction.
`com.snc.change_request.populate_business_application`	This property controls the population of the Business Application related list based on the impacted services and configuration items associated with change requests.
`com.snc.change_request.populate_service_offering`	This property determines whether the service offering related list is automatically populated based on the Impacted Services and CIs associated with a change request.
`com.snc.change_request.refresh_impacted.event`	This property controls whether the impacted CIs/Services related list is refreshed automatically in the background, notifying users upon completion.
`com.snc.change_request.refresh_impacted.include_affected_cis`	It enables the generation of the impacted CIs/Services related list based on the affected CIs listed in change requests, provided that Business Services have been converted to Application Services.
`com.snc.change_request.refresh_impacted_services.message.show`	It controls whether a message is shown to users when the refresh impacted services process starts.
`com.snc.change_request.standard_change.abort_insert_inactive_template`	It blocks the creation of Change Requests that reference inactive Standard Change Templates, enforcing the use of active templates.
`com.snc.change_request.standard_change.link_task.valid_fields`	It specifies which reference fields in task records are valid for linking to change requests, enhancing traceability and management of changes.
`com.snc.change_request.standard_change.use_user_criteria`	It configures whether User Criteria is applied to Standard Change Templates when accessed via the REST API, impacting user access to change creation.
`com.snc.iam.conference_call_escalation_workflow`	This property defines the default workflow to be used when escalating conference calls for incident alerts, ensuring a standardized response process.
`com.snc.iam.incident_alert_task.closure`	This property sets the state of open Incident Communication Tasks to either Skipped or Complete based on the closure status of the related Incident Communication Plan.
`com.snc.iam.on_call_escalation_level`	This property configures the escalation level for on-call personnel, affecting who is contacted during incident communication.
`com.snc.iam.reset_timer_on_snooze`	This property configures the behavior of the timer for overdue Incident Communication Tasks when snoozed, affecting how overdue notifications are managed.
`com.snc.incident.autoclose.basedon.resolved_at`	It determines whether incidents are automatically closed using the resolution date or the updated date, affecting incident management workflows.
`com.snc.incident.clone_fields_on_reopen`	This property defines a list of fields that are duplicated from the original incident to the reopened incident, facilitating continuity in incident tracking.
`com.snc.incident.communicate_prb_workaround_to_inc_worknotes`	When enabled, it journals all communications from a problem record into the worknotes of the related incident, enhancing visibility and tracking.
`com.snc.incident.communication_recipients_excluded_tables`	This property defines which tables are not considered when determining recipients for Incident Communication Plans, impacting notification delivery.
`com.snc.incident.copy.attributes`	This property defines a list of attributes that will be copied from the originating incident to new incidents, ensuring important details are retained.
`com.snc.incident.copy.enable`	This property determines whether users can copy incidents, facilitating easier incident management and replication.
`com.snc.incident.copy.related_lists`	This property defines a comma-separated list of related tables that will be copied when an incident is created, affecting how related information is handled.
`com.snc.incident.copy.rl.task_ci.attributes`	It specifies a comma-separated list of attributes to be copied from affected configuration items associated with an incident.
`com.snc.incident.copy.rl.task_cmdb_ci_business_app.attributes`	It defines a list of attributes that are copied from the Business Applications related list when an incident is processed.
`com.snc.incident.copy.rl.task_cmdb_ci_services.attributes`	It defines a comma-separated list of attributes that are copied from the task_cmdb_ci_service related list when an incident is processed.
`com.snc.incident.copy.rl.task_service_offering.attributes`	It defines a comma-separated list of attributes that are copied from the task_service_offering related list when an incident is processed.
`com.snc.incident.copy_comments_to_non_resolved_childInc`	It enables the automatic copying of comments from a parent incident to its non-resolved child incidents, enhancing visibility and context.
`com.snc.incident.create.child.enable`	This property allows users to create child incidents linked to parent incidents, facilitating better incident management.
`com.snc.incident.create_from_interaction.save`	This boolean property determines whether incidents are created in a saved state when initiated from an interaction.
`com.snc.incident.incident_alert.closure`	It automatically closes any open Incident Communication Plans when the associated Incident is closed or canceled, streamlining incident management.
`com.snc.incident.incident_task.closure`	It configures the system to close related Incident Tasks upon the closure or cancellation of an Incident, maintaining task integrity.
`com.snc.incident.link_to_task.problem`	It configures the ability to add incidents to a problem record through a UI action, enhancing incident management capabilities.
`com.snc.incident.ot_incident_task.closure`	It updates the state of open OT incident tasks to Closed Incomplete or Closed Skipped based on the closure or cancellation of the related OT incident.
`com.snc.incident.populate_business_application`	This property controls whether the Business Application related list is automatically populated for incidents in the system.
`com.snc.incident.populate_service_offering`	This property determines whether the Service Offering related list is displayed for incidents, impacting how incidents are categorized and managed.
`com.snc.incident.refresh_impacted.event`	This property controls whether the impacted CIs/Services related list refresh occurs in the background, notifying users when complete.
`com.snc.incident.refresh_impacted.include_affected_cis`	It enables the population of impacted services in incident management based on affected CIs, provided that business services have been converted to application services.
`com.snc.incident.strike.count`	It specifies how many times the system will attempt to reach a caller before automatically resolving the incident if no response is received.
`com.snc.incident.strike.wait_period`	This property sets the interval in business days between attempts to contact a caller about an incident, influencing the auto-closure process of unresolved incidents.
`com.snc.integration.verizon_ebonding.category`	This property specifies the category used for incidents associated with Verizon eBonded Tickets, defaulting to 'VZ eBonding'.
`com.snc.integration.verizon_ebonding.correlation_display`	It specifies the correlation ID displayed in the Incident's correlation_display field for Verizon-related incidents.
`com.snc.itsm.add_ci.no_query`	This property controls data loading behavior for specific CI-related pages, allowing for configuration of which tables to reference when enabled.
`com.snc.on_call.announcement_message`	This property activates a message that informs users about the new On-call experience within the SOW on classic On-call pages.
`com.snc.on_call_rotation.allow_manage_members`	It allows the management of Rota members through specific UI actions, enhancing roster balance during updates.
`com.snc.on_call_rotation.allow_rota_overlap`	This property enables or disables the allowance of overlapping shift schedules for on-call rotations, affecting how shifts are assigned.
`com.snc.on_call_rotation.cover.color`	This property defines the color used to represent on-call coverage for roster members, enhancing clarity in scheduling displays.
`com.snc.on_call_rotation.escalation_rule_rota_overlap`	This property determines the escalation rules for overlapping shifts, allowing escalations to outgoing, incoming, or all shifts based on the selected option.
`com.snc.on_call_rotation.ie_minimum`	It specifies the minimum Internet Explorer version, currently set to 10, necessary for the On-Call Calendar to function properly.
`com.snc.on_call_rotation.landing_page.show_pending_actions`	It controls whether pending actions are shown on the On-Call Schedules landing page, enhancing visibility for users managing on-call duties.
`com.snc.on_call_rotation.max_rotation_repeat_count`	This property restricts the maximum allowable days for on-call rotation spans based on the configuration of rotation intervals and roster sizes.
`com.snc.on_call_rotation.pto.configuration`	This property specifies the conditions under which On-Call users can submit PTO requests, including options for requiring manager approval or prohibiting requests altogether.
`com.snc.on_call_rotation.reports.max_duration_in_days`	It limits the number of days for which on-call hour reports can be generated, ensuring manageable report sizes.
`com.snc.on_call_rotation.timeoff.color`	This property defines the color used to represent time-off spans in the on-call rotation interface.
`com.snc.outage.auto_refresh_service_offerings`	When enabled, this property automatically updates the related service offerings in the affected CI's list upon adding a CI to an outage record.
`com.snc.problem.create_from_incident.attributes`	It specifies a list of attributes that are automatically copied from an incident to a new problem record, facilitating streamlined problem creation.
`com.snc.problem.create_from_incident.copy_attachments`	This boolean property determines whether attachments from an incident are copied to the associated problem record.
`com.snc.problem.create_from_interaction.save`	This property determines whether problems can be automatically saved when created from user interactions, influencing problem management efficiency.
`com.snc.problem_management.models.enabled`	It configures the system to use Problem and Problem Task Models for new records, while older records will retain their previous lifecycle processes.
`com.snc.project.allow_start_on_relations`	It allows tasks to maintain their start on date when they are related to other tasks, preventing automatic adjustments that could disrupt project timelines.
`com.snc.project.change_planned_date_from_actual_for_manual`	When enabled, this property adjusts the planned end date of manual projects using the actual start date and the planned duration, providing more accurate scheduling.
`com.snc.project.enable_alter_of_planned_dates`	It allows changes to planned start dates for tasks regardless of their current state, facilitating project management flexibility.
`com.snc.project.move_project.wip`	This property allows projects in WIP status to be moved, facilitating changes to their planned start dates and associated tasks.
`com.snc.project.rollup.cost`	This property allows for the automatic updating of a parent project's cost based on changes made to its child tasks, facilitating better financial management.
`com.snc.project.rollup_project_start_date`	When enabled, this property rolls up the planned start date of a project from the earliest task's planned start date, ensuring alignment between tasks and the overall project schedule.
`com.snc.project.sync_original_dates_with_planned_dates`	The property synchronizes original and planned dates when creating or updating projects or tasks, ensuring consistency in date management.
`com.snc.project_task_cascade_delete`	This property configures the cascading deletion behavior for project tasks when a project is deleted, affecting task removal based on the boolean value set.
`com.snc.service.offering.field`	This property determines whether the Configuration Item or Service Offering field is utilized for matching tasks with service offerings, impacting related plugins.
`com.snc.sla.always_populate_business_fields`	It controls whether business fields are filled with actual values or left empty when a Task SLA lacks a schedule.
`com.snc.sla.calculate_planned_end_time_after_breach`	It configures whether the breach time for Task SLAs is modified after a breach, based on any pause time that has occurred.
`com.snc.sla.calculation.always_run_relative_duration_script`	This property, when set to true, forces the relative duration script to execute for every calculation of a Task SLA's duration, rather than just at attachment.
`com.snc.sla.calculation.percentage`	This property sets the threshold percentage for stopping regular updates of Task SLA time values by scheduled jobs, helping to manage performance and data accuracy.
`com.snc.sla.calculation.use_time_left`	This property configures the SLA breach determination method, allowing the use of the Business time left field instead of the Business percentage field, which may round values and affect breach status.
`com.snc.sla.compatibility.breach`	This property configures whether a Task SLA's stage is set to breached when the breach time is exceeded, aligning with legacy behavior from 2010.
`com.snc.sla.condition.case_sensitive`	This property configures the SLA engine to perform either case-sensitive or case-insensitive matching for conditions in SLA Definitions.
`com.snc.sla.condition.timers`	This property activates all SLACondition timers, allowing for comprehensive testing of SLA functionalities within the system.
`com.snc.sla.contract.tables`	This property allows the system to manage SLAs associated with service contracts and internal agreements, enhancing compliance and tracking.
`com.snc.sla.debug`	This property activates detailed logging for SLA calculations, which can help identify issues during testing.
`com.snc.sla.default_conditionclass`	This property allows the configuration of the default script include for SLA condition evaluation, enabling customization of SLA condition rules.
`com.snc.sla.engine.async`	This property configures the SLA engine to run asynchronously, creating a scheduled job for task updates, or synchronously for immediate visibility.
`com.snc.sla.engine.version`	This property configures the system to utilize the 2011 version of the SLA engine, enabling updated functionality and performance improvements.
`com.snc.sla.flow.run_for_breached`	This property enables the execution of a flow for a task SLA that is already breached upon attachment, overriding the default behavior of not running the flow in such cases.
`com.snc.sla.get_task_from_db`	This property configures the SLA processing to fetch records directly from the database for specified Task tables, preventing the use of outdated information.
`com.snc.sla.maximum_duration`	This property defines the upper limit for SLA durations, preventing SLAs from being set beyond the specified number of days.
`com.snc.sla.repair.audit`	This property determines whether auditing is active when performing SLA repairs, impacting how repair actions are logged.
`com.snc.sla.repair.enabled`	This property enables the activation of SLA Repair modules and associated UI Actions within the ServiceNow platform.
`com.snc.sla.repair.use_repair_workflow`	This property, when set to true, directs the system to utilize a designated Repair workflow for SLA repairs, overriding the default SLA Definition workflow.
`com.snc.sla.repair.workflow`	This property defines the specific Repair workflow name utilized in SLA processes, impacting how repair tasks are managed.
`com.snc.sla.run_old_sla_engine`	This property controls the activation of the old SLA engine, affecting how SLAs are processed in the system.
`com.snc.sla.task_sla.timers`	This property activates TaskSLA timers, allowing for their testing and evaluation in the ServiceNow environment.
`com.snc.sla.timers`	This property allows the activation of SLA calculation timers, which are typically disabled in production environments.
`com.snc.sla.workflow.log`	This property configures the logging level for TaskSLAworkflow, with a default setting of Notice, affecting how much information is recorded in the logs.
`com.snc.sn_ot_incident.copy.attributes`	This property allows the configuration of specific attributes to be copied from a parent incident to its child incidents, enhancing data consistency.
`com.snc.sn_ot_incident.create.child.enable`	It allows users to create child incidents linked to existing OT incidents, facilitating better organization and management of related incidents.
`com.snc.sow_on_call.supported_tables`	This property defines the tables that can be utilized for on-call scheduling, with 'incident' as the default value.
`com.snc.task.add_change_request`	This property defines a list of task types, such as problem and incident, that permit the addition of change requests via a user interface.
`com.snc.task.refresh_impacted_services`	It defines a list of task types that allow the 'Refresh Impacted Services' action, impacting how service disruptions are managed.
`com.snc.time_worked.update_task_timer`	This property determines whether the task timer field is updated automatically when task time worked values are modified.
`enable.approval.entitlement`	This property enables or disables approval entitlements, affecting how approvals are managed within the ServiceNow platform.
`eventrule.group.usenormalizedtext`	This property determines whether normalized text is utilized for event rule recommendations, impacting how events are grouped.
`evt_mgmt.active_interval`	This property specifies the active interval for reopening closed alerts in Event Management, influencing how new events are processed in relation to existing alerts.
`evt_mgmt.ai_refresh_time_interval`	This property defines a 5000-millisecond interval during which alert updates are suppressed to optimize system performance.
`evt_mgmt.ai_refresh_time_to_wait_after_manual_action`	This property determines the delay before the alert list refreshes after a manual action, with a default setting of 30 seconds.
`evt_mgmt.alert.management.activated`	This property determines whether the Alert Management functionality is active, impacting how alerts are handled within the system.
`evt_mgmt.alert.management.enable_legacy_alert_action_rules`	This property determines whether legacy alert action rules are enabled, affecting how alerts are processed and managed within the system.
`evt_mgmt.alert_ack_on_close`	This property determines whether an alert is automatically acknowledged upon manual closure, enhancing alert management consistency.
`evt_mgmt.alert_auto_assignment_field`	This property defines which fields are used to automatically assign alerts to appropriate teams, enhancing incident response efficiency.
`evt_mgmt.alert_auto_close_interval`	This property specifies the interval in hours after which open alerts are automatically closed, enhancing alert management.
`evt_mgmt.alert_black_list_fields`	This property defines a comma-separated list of fields that are excluded from being copied to alert fields during event processing.
`evt_mgmt.alert_closes_incident`	This property configures the behavior of closing alerts in relation to associated incidents, allowing for automatic closure of unresolved incidents when an alert is closed.
`evt_mgmt.alert_groups_reasoning.enable_worknotes`	This property determines if worknotes are generated to document the reasoning behind alert groupings, impacting how alert information is recorded and displayed.
`evt_mgmt.alert_insight_alert_history_min`	This property configures the duration for which Alert Insight retrieves historical alert data, allowing for the identification of recurring alerts.
`evt_mgmt.alert_insight_alert_same_as_filter`	This property specifies a comma-separated list of alert fields that must be equal for alerts to be deemed similar, impacting alert management processes.
`evt_mgmt.alert_insight_closed_alert_window`	This property specifies the duration in minutes after an alert's last updated date during which related CI tasks can be retrieved for closed alerts.
`evt_mgmt.alert_insight_group_mapping`	It configures the scoring mechanism for relationships between alerts in the same group, impacting alert prioritization.
`evt_mgmt.alert_insight_level_1_mapping`	This property defines the scoring mechanism for level 1 relationships in alert insights, impacting alert prioritization and response strategies.
`evt_mgmt.alert_insight_level_2_mapping`	This property sets the score for level 2 relationships in Alert Insight, influencing alert prioritization and management.
`evt_mgmt.alert_insight_level_3_mapping`	This property sets the score for level 3 relationships in Alert Insight, influencing how alerts are prioritized based on their relationship depth.
`evt_mgmt.alert_insight_max_affected_ci_change_requests`	This property limits the number of change requests associated with affected CIs that Alert Insight retrieves, with a default value of 20.
`evt_mgmt.alert_insight_max_tasks`	This property limits the number of related tasks returned for Alert Insight, impacting how alerts are analyzed and displayed.
`evt_mgmt.alert_insight_related_cis_topology_levels`	This property specifies the maximum depth of CI relationships to be retrieved for Alert Insight, affecting how interconnected CIs are displayed.
`evt_mgmt.alert_insight_task_history_min`	This property sets the minimum time period for fetching related CI tasks associated with alerts, ensuring that historical context is available for alert insights.
`evt_mgmt.alert_management_scoped_active`	This property determines whether scoped alert management is active, impacting how alerts are processed and managed within the system.
`evt_mgmt.alert_reopens_incident`	This property specifies the behavior of incident processing when an associated alert is reopened, affecting whether incidents are reopened, created, or left unchanged.
`evt_mgmt.alert_rule_delay`	This property configures the time delay before alert management rules are executed, helping to reduce duplicate alerts and noise in the system.
`evt_mgmt.alert_tags_prefix`	This property defines a string prefix that is prepended to all alert tags generated by the event management application.
`evt_mgmt.alert_tags_state`	This property controls the storage and visibility of alert tags defined in event rules, affecting how alerts are managed and displayed within the system.
`evt_mgmt.avoid_int_enabled`	It prevents incidents from being created for secondary alerts when a primary alert already has an associated incident.
`evt_mgmt.custom_field_values_list_to_ignore_in_binding`	This property defines a comma-separated list of custom field values that will be ignored during the binding process, enhancing the efficiency of event management.
`evt_mgmt.enable_alert_correlation`	This property determines whether alert correlation is performed, helping to group related alerts for better incident handling.
`evt_mgmt.enable_group_level_event_rules`	It activates team-based functionality for defining event rules and field mappings, allowing for integration-specific configurations.
`evt_mgmt.eventrule_composition_fallback_withoutregex`	This boolean property determines whether a fallback option is activated to handle StackOverflow Errors during event rule composition without regular expressions.
`evt_mgmt.eventrule_composition_using_regex`	This boolean property determines whether regular expressions are utilized in the processing of event rule compose fields, affecting how events are matched and processed.
`evt_mgmt.flap_frequency`	This property sets the minimum number of occurrences required for an alert to enter the flapping state within a specified time frame.
`evt_mgmt.flap_interval`	This property sets the duration in seconds that must pass before an alert can be updated based on identical events, helping to reduce redundant notifications.
`evt_mgmt.flap_quiet_interval`	This property sets the time interval in seconds that must pass before an alert can be updated based on identical events, helping to suppress redundant notifications.
`evt_mgmt.ignore_custom_field_values_in_binding`	This property specifies if custom field values should be ignored in the event binding process, affecting how events are processed based on user-defined criteria.
`evt_mgmt.ignore_empty_event_fields`	This property configures the system to ignore empty event fields during the alert field override process, enhancing data relevance.
`evt_mgmt.ignore_last_event_description`	This property determines whether the alert description is updated based on the closing event description, affecting how alerts are displayed.
`evt_mgmt.impact_calulation.alert_group_support`	This property allows the creation and management of alert queries, facilitating the grouping of similar alerts for improved incident management.
`evt_mgmt.incident_closes_alert`	It configures the system to automatically close alerts linked to resolved incidents, enhancing incident management efficiency.
`evt_mgmt.include_maint_alerts_in_console`	This property includes alerts with a maintenance flag in the alert console, enhancing the visibility of such alerts for administrators.
`evt_mgmt.max_worknotes_on_alert`	This property limits the number of work notes recorded for each alert to a specified integer value, enhancing data management.
`evt_mgmt.open_new_incident_ignore_fields`	This property configures the fields that are excluded from consideration when generating a new incident from an event, impacting how incidents are logged.
`evt_mgmt.override_alert_short_description`	This boolean property determines whether the short description of an alert can be overridden, allowing for tailored alert messaging.
`evt_mgmt.rule_based_manual_closure`	It controls the closure behavior of secondary alerts in relation to their primary alert, allowing them to remain open or close automatically based on the primary alert's status.
`evt_mgmt.write_remediations_to_alert_work_notes`	This property enables or disables the logging of remediation execution details in alert work notes, enhancing visibility into incident resolution efforts.
`glide.approval.delegation.version`	This property allows administrators to select between different versions of approval delegation, including support for granular delegation features.
`glide.approval_engine.change_request`	This property determines whether the approval engine is active for processing change requests, impacting how approvals are managed within the system.
`glide.approval_engine.change_task`	This property configures the approval engine for Change Request Tasks, allowing selection of different processing methods.
`glide.bulk_proposed_change.view_name`	This property specifies the name of the view used when generating bulk propose changes, allowing for customization to fit specific needs.
`glide.connect.enabled`	This property controls the visibility of the 'Create or Join Chat Room' link on the Incident form based on the Chat plugin status.
`glide.discovery.certs.enable_incident_creation_for_expired_certificates`	It activates the Scheduled Job that generates incidents for expired certificates, facilitating better tracking and management of certificate issues.
`glide.ecmdb.change_end_date`	This property configures the end date field for Change Requests, defaulting to 'work_end' to facilitate tracking of change timelines.
`glide.ecmdb.change_start_date`	This property specifies the default start date for change requests, impacting how changes are scheduled and managed within the system.
`glide.escalation.sticky`	This property controls the timing of escalation assignments, allowing them to be fixed at ticket creation or recalculated on subsequent updates.
`glide.itil.assign.number.on.insert`	This property configures the system to assign task numbers exclusively during the insertion of new tasks, avoiding the allocation of numbers for tasks that are not finalized.
`glide.problem.interaction.allow_create`	This property allows users to create problem records from interaction records, enhancing the integration between incident management and problem management.
`glide.sla.calculate_on_display`	It updates the SLA timings in real-time each time the Task form is accessed, providing up-to-date information for users.
`glide.ui.autoclose.time`	This property determines the automatic closure period for resolved incidents, with a default setting of 7 days, and can be disabled by setting it to zero.
`glide.ui.change_request_activity.fields`	This property configures the fields shown in the Change Request activity formatter, allowing for tailored user experiences based on organizational needs.
`glide.ui.incident_activity.fields`	This property defines a comma-separated list of fields shown in the Incident activity formatter, affecting how incident details are presented to users.
`glide.ui.incident_activity.image.comments`	This property sets the image icon displayed for additional comments in the Task Activity formatter, allowing for customization of the comment interface.
`glide.ui.incident_activity.image.work_notes`	This property sets the image displayed for work notes in the Task Activity formatter, influencing the visual representation of work notes in the system.
`glide.ui.incident_activity.style.comments`	This property specifies the CSS style for the background of additional comments in incident activities, impacting how they are visually presented in the user interface.
`glide.ui.incident_activity.style.work_notes`	This property sets the background color for incident work notes, allowing for visual customization in the incident management interface.
`glide.ui.incident_alert_activity.fields`	This property configures the fields shown in the incident communication plan activity formatter, affecting how incident details are presented.
`glide.ui.problem_activity.fields`	This property specifies the fields that appear in the problem activity formatter, allowing customization of displayed information.
`glide.ui.rm_epic_activity.fields`	This property specifies the fields shown in the epic activity formatter, allowing customization of displayed information.
`glide.ui.rm_release_scrum_activity.fields`	This property specifies which fields are visible in the Scrum release activity formatter, impacting how release activities are tracked and managed.
`glide.ui.rm_scrum_task_activity.fields`	This property configures the fields shown in the Scrum Task activity formatter, affecting how task details are presented to users.
`glide.ui.rm_sprint_activity.fields`	This property specifies which fields are shown in the sprint activity formatter, allowing for tailored visibility of relevant data.
`glide.ui.rm_story_activity.fields`	This property configures the fields shown in the story activity formatter, allowing customization of displayed information for better user experience.
`glide.ui.timer.started`	This property determines whether the task timer initiates automatically upon displaying a task, facilitating real-time tracking of task duration.
`problem.acceptrisk.move_to_closed`	This property, when enabled, allows Problems to transition directly to Closed status upon risk acceptance, bypassing the Resolved state.
`problem.closed.can_create_tasks`	This property allows the creation of Problem Tasks on closed Problems, impacting task management and workflow processes.
`problem.closed.cancel_open_tasks`	This boolean property cancels any open Problem Tasks automatically upon closing a Problem, streamlining task management.
`problem.closed.role.reanalyze_from_canceled`	It specifies the user role that has the authority to re-analyze a problem that has been canceled, with a default setting of 'problem_manager'.
`problem.closed.role.reanalyze_from_closed_riskaccepted`	It specifies the user roles allowed to re-analyze closed problems marked as risk accepted, impacting problem management workflows.
`problem.closed.role.reanalyze_from_completed`	It specifies the user role that can initiate a re-analysis of a problem that has already been marked as completed.
`problem.duplicate.records_to_move`	It defines a comma-separated list of task records to be moved when a problem is marked as a duplicate, ensuring proper linkage between related records.
`problem.fix.records`	This property specifies which related task records are monitored for completion or cancellation, impacting notifications to the Coordinator.
`problem.role.relate_closed_incidents`	This property specifies the user role that can link closed incidents to problems, impacting how incidents are managed within the problem management process.
`problem_task.closed.can_reassess_on_closed_problem`	This boolean property determines whether problem tasks can be reassessed after their related problems are marked as closed.
`problem_task.closed.role.reaassess_from_closed`	It specifies the user role allowed to re-assess completed or canceled problem tasks, impacting task oversight and management.
`sa.qbs.max_num_of_cis`	This property restricts the number of CIs returned in SLA configurations to enhance system performance and stability.
`sa_analytics.agg.group_alert_with_same_group_by_fields`	It specifies which fields' values must match for alerts to be grouped, enhancing the correlation of related alerts.
`sa_analytics.agg.learner_group_by_property`	This property determines the specific field by which alerts are grouped during the alert aggregation process, facilitating better organization and analysis of related alerts.
`sa_analytics.agg.learner_rca_detection`	This property activates root cause analysis specifically for Automated groups based on configuration item (CI) grouping, allowing for deeper insights into incident patterns.
`sa_analytics.agg.mi_graph_enabled`	This property determines whether the Mutual Information Graph Aggregator is active, affecting how data is aggregated and analyzed.
`sa_analytics.agg.query.group_logic_order`	This property configures the execution order of various alert grouping methods, allowing for tailored alert aggregation strategies.
`sa_analytics.agg.query_customer_feedback_enabled`	This property determines whether customer feedback is utilized for forming new alert aggregation groups, impacting how alerts are categorized and prioritized.
`sa_analytics.agg.query_network_traffic_correlation_enabled`	This property activates the correlation of alerts based on network traffic, allowing for more accurate grouping and streamlined alert management.
`sa_analytics.aggregation.include_service`	This property configures the inclusion of all CIs in alert aggregation, impacting how alerts are processed based on their relation to business services.
`sa_analytics.disable_prc`	This property, when set to true, stops the system from performing Probable Root Cause Analysis on change requests.
`sm.flapper.affected.services_range`	This property specifies the available ranges of affected services for the CI change flapper detection mechanism, influencing how changes are evaluated.
`sn_atf.test.triage.task.type`	This property specifies the default task type for automated testing task creation, primarily set to incident.
`sn_change_cab.com.snc.change_management.cab.check_duplicated_agenda_item`	It enables or disables the selection of duplicated agenda items for CAB meetings, impacting how meeting agendas are structured.
`sn_change_cab.com.snc.change_management.cab.refresh_group_attendees`	It enables or disables the automatic updating of CAB attendees based on changes to the CAB board group membership.
`sn_change_cab.com.snc.change_management.cab.refresh_group_attendees.meeting_state`	It specifies the CAB meeting state values that trigger updates to CAB attendees based on changes in the Board group membership.
`sn_change_cab.com.snc.change_management.cab.use_sow_meeting`	This boolean property enables or disables the use of SOW meetings during CAB discussions, impacting how changes are evaluated and approved.
`sn_chg_model_ui.landing_page.enable_legacy_preapproved_title`	Enabling this property changes the tab label from 'Standard changes' to 'Preapproved' on the Change model landing page.
`sn_chg_soc.change_soc_initial_limit`	This property defines the initial limit of change request records shown on the Change Schedule load, with a default of 40.
`sn_chg_soc.change_soc_scroll_load_limit`	This property defines the integer limit on the number of change request records shown during scrolling in the Change Schedule interface.
`sn_chg_soc.change_soc_total_limit`	This property defines the limit on the number of change_request records displayed in the Change Schedule, with a default of 1000.
`sn_chg_soc.landing_page.pinned_notification`	This property enables or disables the display of an information message when a change schedule is pinned, affecting user notifications.
`sn_chg_soc.schedule_window_days`	It sets the range of days around a change request's timeline for displaying relevant blackout and maintenance windows on the Change Schedule page.
`sn_cmp.changerequestnormal`	This property sets the default value for change request status to 'Normal', influencing how change requests are processed within the application.
`sn_cmp.changerequeststandard`	This property sets the default value for change request standards, influencing how change requests are categorized and processed.
`sn_cmp.cloud_change_type_for_approval`	This property specifies the change request type for approvals in cloud operations, defaulting to 'normal'.
`sn_cmp.cloud_change_type_for_nonapproval`	This property specifies the type of change request generated automatically when approval is not required, defaulting to 'standard'.
`sn_cmp.create_change_request_for_provision`	This property enables or disables the automatic creation of change requests for provisioning operations within the Cloud Provisioning and Governance application.
`sn_cwm.agile_enabled`	This property determines whether Agile features are available in CWM, allowing for the creation of Agile items and enabling Sprint planning.
`sn_deploy_pipeline.change_management.default.model`	This property configures the default model of change requests by specifying a sys_id, impacting how changes are managed in the deployment pipeline.
`sn_deploy_pipeline.change_management.default.template`	This property specifies the sys_id of the default template used when creating change requests in the Deployment Pipeline application.
`sn_deploy_pipeline.change_management.enabled`	This property activates the integration of change management features within deployment pipelines, facilitating better tracking and governance of changes.
`sn_devops.auto_close_change_subflow`	This property specifies the subflow that triggers the automatic closure of change requests when a pipeline finishes, enhancing workflow efficiency.
`sn_devops.awaiting_states`	This property specifies the awaiting states for change requests, impacting how the system tracks and manages pending actions.
`sn_devops.cancel_change_on_associated_stage_cancel`	This boolean property cancels a change request when the associated pipeline stage fails or is canceled, enhancing control over change management.
`sn_devops.cancel_change_on_pipeline_cance`	This property enables the automatic cancellation of change requests linked to failed steps in a DevOps pipeline, streamlining the management of unsuccessful changes.
`sn_devops.change.requestor`	This property defines the default user who is designated as the requestor for DevOps change requests, impacting how requests are logged and processed.
`sn_devops.change_request.apply_attributes_on_creation`	This property enables the application of change request attributes during creation, rather than after, when business rules are used.
`sn_devops.change_request.approved_approval`	This property specifies the string value for the approval status in DevOps change requests, defaulting to 'approved'.
`sn_devops.change_request.auto_close_allow_override_end_time`	It determines whether the Actual end time can be overridden, impacting the automatic closure of change requests based on pipeline completion.
`sn_devops.change_request.auto_close_allow_override_start_time`	This boolean property determines whether the Actual start time can be overridden during the auto-closing of change requests in the DevOps Data Model.
`sn_devops.change_request.auto_close_failure_code`	This property specifies the close code used for change requests that are automatically closed due to failure, impacting how these requests are categorized in the system.
`sn_devops.change_request.auto_close_partial_successful_code`	It specifies the close code used for change requests that finish with issues, impacting how such requests are categorized in the system.
`sn_devops.change_request.auto_close_successful_code`	This property specifies the close code used for successfully completed change requests when the autoCloseChange feature is active.
`sn_devops.change_request.cancel_state`	This property sets the integer value used to indicate that a change request has been canceled, which is essential for managing change request states effectively.
`sn_devops.change_request.closed_state`	This property sets the integer value for the closed state of a change request, which is essential for managing the lifecycle of change requests in the DevOps Data Model.
`sn_devops.change_request.implement_state`	This property sets the default implementation state for change requests, influencing the callback mechanism to third-party tools based on the change model's state.
`sn_devops.change_request.post_implement_state`	This property sets the integer value representing the post-implementation state for change requests, influencing their status in the DevOps process.
`sn_devops.custom_change_categorization`	This property allows for the categorization of DevOps change requests, improving clarity and management of changes.
`sn_devops.enable_change_creation_with_partial_data`	It enables the creation of change requests in scenarios where DevOps data retrieval encounters errors.
`sn_devops.enable_change_receipt_state_transition`	It automatically transitions change request states in the DevOps Data Model when change receipts are enabled, facilitating seamless pipeline operations.
`sn_devops.enable_change_request_state_transition`	This property enables the transition of change request states specifically for the DevOps Change Request Manual Approval Flow.
`sn_devops.reused_model_change_request_subflow`	This property specifies the subflow for handling reusable change requests within the DevOps framework, impacting how change requests are processed.
`sn_dex.alert.correlation_rule.device.period`	This property specifies the time interval for correlating alerts generated from the same metric rule, allowing for efficient grouping of alerts.
`sn_dpm.standard_needs_attention`	This property allows administrators to opt into the DPM Standard Needs Attention feature, providing enhanced flexibility over the legacy functionality.
`sn_dpr.out_of_band_release_allowed`	This property determines whether releases can be created with arbitrary dates without requiring a predefined release target.
`sn_dpr.release_related_record_types`	It configures which record types are associated with digital product releases, impacting user access to related tasks.
`sn_dpr_model.allow_any_release_dates`	This property determines whether users can create releases regardless of the specified date constraints, impacting release scheduling flexibility.
`sn_dpr_model.release_related_task_types`	This property specifies a JSON array of task types that can be linked to a Release, allowing for better organization and tracking of related tasks.
`sn_em_tbac.tag_excluded_alert_fields`	This property defines a list of alert fields that are excluded from the selection options during the creation of Alert Clustering Tags, impacting how alerts are grouped.
`sn_inc_uni_req.incident.universal_request.copy_fields`	It specifies a list of fields to be copied from Universal Request to Incident upon creation, facilitating data consistency.
`sn_major_inc_mgmt.com.snc.incident.mim.major_incident_creation`	It configures whether a candidate is promoted to a major incident or if a new major incident is created from the candidate, linking them as a child incident.
`sn_major_inc_mgmt.com.snc.major_incident.create.copy.attributes`	It defines a list of attributes, such as short_description and impact, that are automatically copied from child Incidents to Major Incidents during their creation.
`sn_major_inc_mgmt.major_incident_management_group`	This property defines the sys_id of the group that is automatically assigned to manage major incidents during the promotion process.
`sn_major_inc_mgmt.notify_webrtc_number`	It configures a Notify Number that facilitates direct voice calls for Major Incident Management users through the browser interface.
`sn_major_inc_mgmt.pir_export_pdf_ui_page`	This property defines the URL for the custom UI page associated with the post-incident report feature in Major Incident Management.
`sn_sow.initial_metric_fetch_window`	This property configures the time period from which initial metrics for a CI are retrieved, affecting incident management and resolution processes.
`sn_sow.playbook.tables.em_alert`	This boolean property determines whether emergency alerts are shown in the Service Operations Workspace, impacting user awareness of critical issues.
`sn_sow.playbook.tables.incident`	This boolean property determines whether incident tables are included in the Service Operations Workspace playbooks, affecting how incidents are handled in the application.
`sn_sow.remove.action.related.list.tables`	This property configures the removal of specific related list tables in the Service Operations Workspace, impacting how information is displayed to users.
`sn_sow.service_desk_groups`	This property allows the specification of service desk group sys_ids, enabling the assignment of agents to relevant user groups for streamlined operations.
`sn_sow_collab.max_chats_in_collaboration_tab`	This property defines the maximum number of chats that can be fetched and shown in the collaboration chat tab, impacting how users interact with chat features.
`sn_sow_inc.autoclose_origin.interaction`	This property automatically changes the state of an origin interaction record to Wrap up or Closed Complete based on the resolution of its associated incident.
`sn_sow_inc.pir.publish.hours`	This property sets the deadline for publishing a Post Incident Report following the resolution of an incident, with a default value of 24 hours.
`sn_sow_itsm_admin.experience_redirection_enabled.sow.incident`	This property determines whether Incident modules redirect users to Core UI16 or Service Operations Workspace, based on specified values.
`sn_sow_itsm_admin.experience_redirection_enabled.sow.mim`	This property determines whether users are redirected to Core UI16 or Service Operations Workspace when accessing Major Incident Management modules.
`sn_sow_mim.playbook_ids`	This property configures which playbook executions are shown in the Major Incident Playbooks side panel of the ServiceNow Operations Workspace.
`sn_sow_problem.defect.create_from_problem.attributes`	This property defines a list of attributes that are automatically transferred from a problem record to a defect record during creation.
`sn_sow_problem.enhancement.create_from_problem.attributes`	It specifies a comma-separated list of attributes from the problem record that will be included in the new enhancement.
`sn_sow_problem.improvement_initiative.create_from_problem.attributes`	It specifies a list of attributes, such as short description and priority, that are automatically copied from a problem to an improvement initiative.
`sn_uni_req.associated_ticket`	This property specifies whether associated tickets are created at the department level or service level, affecting how agents manage inter-departmental requests.
`sn_uni_req.com.snc.universal_request.copy.attributes`	It defines a list of attributes that are transferred from the originating universal request to new records created in the Universal Request application.
`sn_uni_req.com.snc.universal_request.copy.enable`	This property allows users to duplicate the details of an existing Universal Request, streamlining the process of creating new requests based on previous ones.
`sn_uni_req.transfer_type`	This property configures the transfer type for primary tickets, allowing selection between routing to Universal Request or a specific department.
`sn_uni_req.universal_request_needs_resolution_review_state`	This property sets the state and reason for review in the Universal Request application using a comma-separated key-value format.
`sn_uni_req.universal_request_route_state`	This property configures the state and reason for a primary ticket's transition back to Universal Request, affecting how tickets are processed.
`tsp1.project.allow_start_on_relations`	This boolean property determines whether the start on constraint is maintained for tasks when relations are established.
`tsp1.project.auto_close_milestones`	This property configures the automatic closure of milestone tasks based on changes in their work state, enhancing project workflow efficiency.
`tsp1.project.calculate_roi`	This property enables or disables the calculation of ROI for projects, impacting financial reporting and analysis.
`tsp1.project.copy.additional_attributes`	This property defines a list of additional attributes that are transferred when copying project tasks, enhancing the duplication process.
`tsp1.project.date_change_cascade`	This boolean property determines whether changes to the Demand or Project start date will cascade to update related planning dates.
`tsp1.project.date_change_cascade_persist_resource_plan_state`	Enabling this property ensures that the resource plan's state is preserved when the start dates for the Change Resource Plan, Cost Plan, and Benefit Plan are modified.
`tsp1.project.enable_alter_of_planned_dates`	This boolean property allows users to modify planned dates for tasks that are currently WIP or Closed, impacting project management workflows.
`tsp1.project.move_project.wip`	This property allows the relocation of WIP projects, impacting how project management is handled in the system.
`tsp1.project.portfolio_workbench.confirm_to_create_project`	This boolean property controls the confirmation prompt for creating projects from portfolio workbench demands, impacting user workflow and project management.
`tsp1.project.rollup.cost`	This property allows the cost of a project task to automatically update the cost of its parent project, ensuring consistent financial reporting.
`tsp1.project.rollup_project_start_date`	This boolean property controls the aggregation of the project start date based on the start dates of related tasks, impacting project timeline accuracy.
`tsp2.project.allow_start_on_relations`	This boolean property determines whether the start on constraint remains active for tasks when relations are established, impacting task scheduling.
`tsp2.project.auto_close_milestones`	This property configures the automatic closure of milestone tasks in projects based on changes to their work state.
`tsp2.project.calculate_roi`	This property enables or disables the calculation of ROI for projects, affecting financial reporting and decision-making.
`tsp2.project.copy.additional_attributes`	This property defines a list of extra attributes that are included when copying project tasks, enhancing data consistency in project management.
`tsp2.project.date_change_cascade`	This boolean property determines whether changes to the Demand or Project Start Date will automatically update the start dates of associated Resource, Cost, and Benefit Plans.
`tsp2.project.date_change_cascade_persist_resource_plan_state`	Enabling this property ensures that the resource plan's state is preserved when the start dates of the Change Resource Plan, Cost Plan, or Benefit Plan are modified.
`tsp2.project.enable_alter_of_planned_dates`	It allows users to modify planned dates for tasks that are not in an active state, impacting project scheduling.
`tsp2.project.move_project.wip`	This property allows the relocation of WIP projects, facilitating better project management and organization.
`tsp2.project.portfolio_workbench.confirm_to_create_project`	This boolean property determines whether users receive a confirmation prompt before creating projects from demands in the portfolio workbench.
`tsp2.project.rollup.cost`	This property controls whether the estimated and actual costs of project tasks are rolled up to their parent projects.
`tsp2.project.rollup_project_start_date`	This boolean property controls the aggregation of project start dates from related tasks, impacting project scheduling.
`tsp3.portfolio.enter_budget_plannning`	This boolean property determines whether users can input budget planning information for portfolios, impacting financial oversight and resource allocation.
`tsp3.project.allow_start_on_relations`	This boolean property determines whether the start on constraint remains active for tasks when relations are established.
`tsp3.project.auto_close_milestones`	This property configures the automatic closure of milestone tasks based on changes in their work state, enhancing project workflow efficiency.
`tsp3.project.calculate_roi`	This property enables or disables the calculation of ROI for projects based on their estimated costs and net value.
`tsp3.project.copy.additional_attributes`	This property defines a list of additional attributes that are included when copying project tasks, enhancing data consistency in project management.