Namespace

`sn_devops`

91 ServiceNow system properties in this namespace, with what each one does.

`sn_devops.ado_tool_project_map`	This property configures the relationship between Azure DevOps projects and ServiceNow, facilitating data synchronization and workflow management.
`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.bitbucket_default_branch`	It sets the default Bitbucket branch used for import requests, impacting how integration with Bitbucket is configured.
`sn_devops.bulk_flow_timeout`	This property defines the timeout limit for bulk flow operations, defaulting to 60,000 milliseconds, which can impact data processing efficiency.
`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.cascade_delete_threshold`	This property defines the limit for cascading deletions in the DevOps Data Model, ensuring that operations do not exceed the specified threshold.
`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.change_request_callback_timeout`	This property defines the timeout period in minutes for processing change request callbacks in DevOps pipelines, with a default value of 120 minutes.
`sn_devops.change_request_handler_subflow`	This property defines the subflow that populates default values for various fields in DevOps change requests, allowing for customization of the change request creation process.
`sn_devops.change_request_reusability_subflow`	This property specifies the subflow used to determine the reusability of change requests within the DevOps Data Model.
`sn_devops.commit_rel_change_step_type`	It configures the step types that will use the same commit logic as Prod Deploy for determining commits associated with a Change.
`sn_devops.commit_to_artifact_version.ignore_branch`	This property determines if commits from all branches or only the current branch are linked to artifact versions during pipeline executions.
`sn_devops.committer.score.default`	It defines the baseline integer score for committers, which can be adjusted to reflect their contributions in the DevOps framework.
`sn_devops.committer.score.multiply.factor`	This property defines an integer multiplier that affects the calculation of the committer score within the DevOps framework.
`sn_devops.credential_expiration.notify_before_days`	This property configures the advance notification period for tool credential expirations, triggering tasks to alert users.
`sn_devops.credential_expiration.notify_on_expiration`	This property triggers notifications to update tool credentials upon expiration, ensuring that users are alerted to renew access in a timely manner.
`sn_devops.custom_change_categorization`	This property allows for the categorization of DevOps change requests, improving clarity and management of changes.
`sn_devops.default_test_type`	This property specifies the default test type used in DevOps orchestration pipelines, impacting how tests are categorized and reported.
`sn_devops.devops_log_level`	This property allows selection of the log level from options such as Error, Warning, Information, Debug, or Trace, influencing the detail of log output.
`sn_devops.discover.folder.depth`	This property defines how many levels deep the discovery process will search for orchestration tasks and pipelines within folders.
`sn_devops.discover.max.pipelines.ado`	This property defines the upper limit for the number of Azure DevOps pipelines that can be discovered, impacting the import process for DevOps projects.
`sn_devops.discover.request.claim.limit`	This property limits the number of discover requests processed in a single job run, impacting the efficiency of the DevOps Data Model.
`sn_devops.discovered.user.auto.assign.role`	This property configures the default role assigned to active DevOps users, impacting their access and capabilities within the system.
`sn_devops.enable_ado_bulk_run_commits`	This property enables or disables the requirement for Azure DevOps Run Commits to be derived from the last successful pipeline build, impacting commit accuracy.
`sn_devops.enable_ado_generic_connection`	This property enables the creation of a Generic Connection for Azure DevOps, which is necessary for certain integration tasks.
`sn_devops.enable_automatic_associations`	This property allows repositories to be automatically associated with applications when a pipeline is executed, enhancing workflow efficiency.
`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.enable_debug`	This property previously enabled debug logging for the DevOps application but is now deprecated in favor of a more flexible log level configuration.
`sn_devops.enable_github_run_commits`	This property configures whether to derive GitHub Run Commits from the most recent successful workflow run, impacting commit visibility.
`sn_devops.enable_import_polling`	This property controls whether the system actively polls for updates on import requests, enhancing the management of DevOps processes.
`sn_devops.enable_metric`	This property toggles the logging of DevOps metrics, impacting how performance data is captured and reported.
`sn_devops.enable_to_call_sublfow_asynchronously`	This boolean property determines whether master flows execute subflows asynchronously or synchronously, impacting the flow execution speed.
`sn_devops.flow.cap.per.node`	This property defines the cap on concurrent DevOps flows per node, influencing system resource allocation and flow management.
`sn_devops.flow.context.count.cache.update.interval`	This property defines the interval, in seconds, for refreshing the flow context count stored in the cache, impacting data accuracy and system responsiveness.
`sn_devops.gcf_event_last_timestamp_for_flow_limit`	This property stores the timestamp of the last GCF event triggered when active flow executions surpass the specified limit, aiding in flow management.
`sn_devops.github.api_url`	This property defines the endpoint for the GitHub API used by the DevOps Data Model, impacting how data is retrieved from GitHub.
`sn_devops.github.api_version_path`	This property defines the API version path for GitHub integrations, impacting how data is retrieved from GitHub.
`sn_devops.github.url`	It sets the base URL for GitHub API calls used in the DevOps Data Model, enabling integration with GitHub services.
`sn_devops.glide.script.block.client.globals`	This boolean property, when set to true, blocks the use of client-side global variables in scripts, enhancing security in the DevOps Data Model.
`sn_devops.health_report_duration`	This property defines the number of days for which the DevOps system health report remains valid and accessible.
`sn_devops.import.coding_tool.branches.per_page`	This property sets the limit on how many coding tool branches are shown on a single page, enhancing user experience during branch management.
`sn_devops.import.coding_tool.commits.per_page`	This property configures the maximum number of commits shown on a single page when importing data from GitHub or Bitbucket.
`sn_devops.import.coding_tool.repos.per_page`	This property sets the maximum number of coding tool repositories shown on each page during data imports, affecting how data is navigated and processed.
`sn_devops.import.max.pages.processing.per_import`	This property limits the number of pages processed at once during an import, impacting the speed and efficiency of data imports.
`sn_devops.import.max.processing.time.seconds.per_page`	This property defines the maximum processing time in seconds for each page during the import process, impacting how quickly data can be imported.
`sn_devops.import.max.retries.per_page`	This property defines the limit on retry attempts for data import operations, impacting how the system handles failures during the import process.
`sn_devops.import.orchestration_tool.executions.maximum`	This property defines the upper limit for orchestration tool executions during data imports, impacting system resource usage and import efficiency.
`sn_devops.import.orchestration_tool.executions.per_page`	It configures the pagination limit for orchestration tool executions in the DevOps Data Model.
`sn_devops.import.planning_tool.issues.per_page`	It configures the maximum number of planning tool issues shown on a single page in the DevOps Data Model.
`sn_devops.import.request.claim.limit`	This property limits the number of import requests processed in a single job run, directly impacting the speed and efficiency of data imports.
`sn_devops.import.save.payloads.as.attachments`	This property configures the system to save payloads as attachments to Import Request Page records when enabled.
`sn_devops.import_based_evidence_collection`	This boolean property determines whether import-based evidence collection is activated for orchestration tasks within the DevOps Data Model.
`sn_devops.inbound.event.claim.limit`	This property limits the number of inbound events processed in a single job run, impacting how quickly deferred events are handled.
`sn_devops.inbound_events_retry_deferred_frequency`	This property defines how often deferred events are retried for processing, with a default setting of 10 minutes.
`sn_devops.inbound_events_retry_error_list`	This property defines specific errors that, when encountered, will result in the retry of inbound events within the DevOps Data Model.
`sn_devops.inbound_events_retry_error_mins_ago`	This property configures the retry interval for processing inbound events that encountered errors, with a default value of 1440 minutes.
`sn_devops.last_event_received.critical`	This property specifies the inactivity period in days that triggers critical alerts for events or webhooks, helping maintain operational awareness.
`sn_devops.last_event_received.warning`	This property configures the duration in days for displaying warning alerts when events have not been received, helping to maintain awareness of system performance.
`sn_devops.logging.destination`	This property configures where DevOps logs are sent, allowing for flexibility in log management and storage.
`sn_devops.max_retry_count_discover`	It defines how many times the discover action will be retried after hitting a rate limit, with a default value of 10 retries.
`sn_devops.max_retry_count_inbound_event`	This property defines the limit on how many times the system will attempt to process an errored inbound event before giving up.
`sn_devops.max_retry_count_inbound_event_deferred`	This property defines the limit on how many times the system will attempt to process deferred inbound events before giving up.
`sn_devops.non_admin_software_quality_summary_flag`	This boolean property controls access to software quality summaries for non-admin users within the DevOps Data Model.
`sn_devops.permission_check_timeout`	This property determines the timeout duration for permission validation checks against external tools, impacting how quickly errors are reported during tool connections.
`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_devops.sq_ui_category_preferences`	This property configures the default categories for software quality metrics shown in the Pipeline UI, impacting how quality data is presented to users.
`sn_devops.supported_webhook_capabilities`	This property specifies the string values representing the supported webhook capabilities, such as code, plan, orchestration, and artifact.
`sn_devops.table_auto_archive_duration`	This property defines the time period after which DevOps data tables are automatically archived, with a default setting of nine months.
`sn_devops.throttle.reset.time.default`	It defines the default duration, in minutes, that events remain deferred due to throttling when a tool does not specify a reset time.
`sn_devops.token_auth.user`	It sets the user account for token authentication, defaulting to 'devops.system', which is required for completing DevOps integration tasks.
`sn_devops.tool_capabilities`	This property defines the tool capabilities available within the DevOps Data Model, including code, plan, orchestration, artifact, and test.
`sn_devops.track.azure.pullrequests`	This property configures the automatic setup of Azure pull request web-hooks when a tool or project is configured in the DevOps Data Model.
`sn_devops.track.github.issues`	This property configures ServiceNow to track GitHub Issues for specified repositories, facilitating integration and management of work items.
`sn_devops.track.gitlab.pullrequests`	This property determines whether GitLab pull requests and their events are tracked in the DevOps Data Model.
`sn_devops.waiting_event_reconcile_handler.window_end`	This property specifies the end time for the reconciliation window, impacting how waiting events are processed in the system.
`sn_devops.waiting_event_reconcile_handler.window_start`	This property specifies the time format for the starting point of the reconciliation window in the WaitingEventReconcileHandler.
`sn_devops.webhook_check_timeout`	This property configures the maximum wait time for webhook checks, impacting how quickly the system responds to webhook events.