Namespace

`sn_ca`

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

`sn_ca.add_users.event_stagger.campaign`	It specifies the delay in seconds between campaign events during scheduled job execution, allowing for better resource management.
`sn_ca.add_users.event_stagger.users`	This property configures the delay between user addition events during the execution of the Content Experiences scheduled job, allowing for smoother processing.
`sn_ca.add_users.max_events`	This property limits the number of events that can add users to a campaign, ensuring controlled processing during scheduled jobs.
`sn_ca.add_users.max_run_time`	This property limits the execution time of the scheduled job responsible for updating campaign audiences, ensuring it finishes processing the current item within the specified duration.
`sn_ca.add_users.max_users_per_event`	This property limits the number of users added per event to a maximum of 1,000, affecting how user additions are processed during campaigns.
`sn_ca.all_must_approve`	This property enforces that every approver must give their approval for scheduled content, impacting the publishing workflow.
`sn_ca.campaign.max_records_create`	This property limits the number of records created per job run to optimize performance and resource usage during campaign execution.
`sn_ca.campaign.max_records_process`	This property limits the number of targets processed per job run for campaigns, helping to manage system load and performance during execution.
`sn_ca.campaign.max_run_time`	It limits the execution time of scheduled jobs related to Content Experiences, ensuring they finish processing current items after the specified time has elapsed.
`sn_ca.campaign.pending.event_stagger`	This property determines the interval in seconds between each execution of the scheduled job that processes pending non-portal campaign content.
`sn_ca.campaign.preview.portal_url_suffix`	This property configures the URL suffix for rendering campaign previews in the Service Portal, allowing for targeted content display.
`sn_ca.campaign.published.event_stagger`	This property sets a 2700-second delay for the publication of a campaign, allowing for orderly execution of related actions in the system.
`sn_ca.campaign.reevaluation_frequency`	It defines the interval in days for re-evaluating the audience of a campaign, allowing for timely updates to campaign targeting.
`sn_ca.glide.script.block.client.globals`	This boolean property, when set to true, prevents the use of global variables in client-side Glide scripts, enhancing security and performance.
`sn_ca.min_admin_count`	It enforces a minimum of two active admin users for Content Experiences, preventing system misconfiguration and ensuring administrative continuity.
`sn_ca.notification.event_stagger`	It configures the interval for staggering notification events to optimize processing during scheduled jobs.
`sn_ca.notification.max_events`	This property limits the number of email events queued for processing during scheduled jobs, impacting the efficiency of email notifications.
`sn_ca.notification.max_run_time`	This property limits the execution time of scheduled jobs for sending notifications, ensuring they finish processing the current item without starting new tasks.
`sn_ca.notification.max_users_per_event`	This property limits the number of users included in each email notification event to optimize processing and delivery.
`sn_ca.publish.campaign.immediately`	This property enables immediate triggering of the campaign publishing process, bypassing scheduled jobs and allowing for instant audience targeting and content delivery.
`sn_ca.purging.days_after_campaign_end`	It determines the delay period for purging campaign data following the end of a campaign, allowing for data retention during that timeframe.
`sn_ca.purging.days_after_user_removed`	It specifies the duration in days for delaying the purging of campaign data after a user has been removed from a campaign.
`sn_ca.purging.max_run_time`	This property defines the maximum run time for the Content Experiences scheduled job, limiting it to a specified number of seconds.
`sn_ca.purging.max_users_per_job`	This property limits the number of users purged during each execution of the purge job, with a default setting of 25,000 users.
`sn_ca.purging.purge_after_campaign_end`	It enables the automatic purging of campaign data after the campaign's end date is reached, helping to manage data storage effectively.
`sn_ca.purging.purge_on_user_removed`	This property enables or disables the purging of campaign data for users who have been removed from a campaign, affecting data management practices.
`sn_ca.state_management.max_records_update`	This property limits the number of records updated per job run to enhance processing efficiency and prevent system overload.
`sn_ca.state_management.max_run_time`	This property defines the maximum run time for scheduled jobs related to content state management, influencing how quickly campaigns can transition between states.
`sn_ca.task.max_records_create`	This property limits the number of records created by the Content Experiences scheduled job, impacting how efficiently large batches are processed.
`sn_ca.task.max_run_time`	This property limits the execution time of scheduled jobs, allowing them to finish current tasks without picking up new work once the time limit is reached.
`sn_ca.user_deactivation.max_run_time`	This property defines the maximum duration for the Content Experiences scheduled job that deactivates users, defaulting to 300 seconds.
`sn_ca.user_deactivation.max_users_per_job`	This property limits the number of users deactivated per job run to optimize performance during scheduled deactivation tasks.