Home Paris HR Service Delivery HR Service Delivery Employee Service Center Employee Service Center configuration Campaigns for HR Service Delivery Properties installed with content automation

Properties installed with content automation

The Content Automation [com.sn_content_automation] plugin adds properties that determine how a campaign runs related to scheduled jobs and performance.

Scheduled Jobs

The following scheduled jobs work with properties to fine-tune and configure the behavior of Content Automation:

Content Automation Profile
Content Automation: Add Non-Portal Campaign Content
Content Automation: Calculate Campaign Engagements
Content Automation: Create To-dos
Content Automation: Deactivate Campaign Users
Content Automation: Evaluate Campaign Success Goals
Content Automation: Manage Content States
Content Automation: Process SNC analytics
Content Automation: Purge Campaign Data
Content Automation: Send Email Notifications
Content Automation: Send SMS Notifications
Content Automation: Update Campaign Audience

See Components installed with Content Automation.

Properties

To access Content Automation properties, navigate to Content Automation > Configurations > Properties.

Content Automation properties determine how the scheduled jobs run and help to ensure that there is limited impact on the performance of your instance.

Table 1. Approvals
Property	Usage
sn_ca.all_must_approve	Indicates that all approvers must approve any scheduled content prior to publishing it. If you check No, only one approver is required to publish a campaign.

Table 2. Add Users
Property	Usage
sn_ca.add_users.max_run_time	The maximum amount of time (in seconds) the Content Automation: Add users to Campaigns scheduled job runs. Limits the length of the scheduled job, but completes any work in progress and does not pick up any new work. Default value: 600
sn_ca.add_users.event_stagger.campaign	The amount of time between campaign events when a scheduled job runs. Staggering provides time for the events to be processed during the staggered time. Default value: 300 seconds
sn_ca.add_users.event_stagger.users	The amount of time between campaign events to add users when a scheduled job runs. Staggering provides time for the events to be processed during the staggered time. Default value: 900 seconds
sn_ca.add_users.max_events	The maximum number of events that users can be added for a campaign. Default value: 100
sn_ca.add_users.max_users_per_event	The maximum number of users you can add in a single event. Default value: 1000

Table 3. Non-Portal Content
Property	Usage
sn_ca.campaign.max_run_time	The maximum amount of time (in seconds) the Content Automation: Add Non-Portal Campaign Content scheduled job runs. Limits the length of the Content Automation: Send Email Notifications scheduled job, but completes any work in progress and does not pick up any new work. The default is 300 seconds.
sn_ca.campaign.max_records_process	The maximum number of people a campaign can target per scheduled job run. The default is 15,000.
sn_ca.campaign.max_records_create	The maximum number of records to create per job run.
sn_ca.campaign.pending.event_stagger	The number of seconds between each time the Content Automation: Add Non-Portal Campaign Content scheduled job runs to try to send non-portal content.
Note: These properties determine limits on non-portal content (emails and SMS). The Content Automation: Send Email Notifications scheduled job runs every hour by default and attempts to send non-portal content not sent in the first pass. Customers with a large database should consider increasing this property after testing the impact it could have on performance.

Table 4. To-do Content
Property	Usage
sn_ca.task.max_run_time	The maximum amount of time (in seconds) the Content Automation: Create To-dos scheduled job runs. Limits the length of the scheduled job, but completes any work in progress and does not pick up any new work. The default is 300 seconds.
sn_ca.task.max_records_create	The maximum number of records to create per scheduled job run. The default is 25,000.

Table 5. Notifications
Property	Usage
sn_ca.sms_notification.max_users_per_event	The maximum number of users to add per event for an SMS notification.
sn_ca.notification.max_run_time	The maximum amount of time (in seconds) the Content Automation: Send Notifications scheduled job runs.
sn_ca.notification.event_stagger	The amount of time between events when a scheduled job runs. Staggering provides time for the events to be processed during the staggered time. The default is 60 seconds.
sn_ca.notification.max_events	The maximum number of events to queue per job run.
sn_ca.notification.max_events	The maximum number of events to queue per job run for email notifications.
sn_ca.notification.max_users_per_event	The maximum number of users to add per event for email notifications.

Table 6. State Management
Property	Usage
sn_ca.state_management.max_run_time	The maximum amount of time (in seconds) the Content Automation: Manage Content States scheduled job runs.
sn_ca.state_management.max_records_update	The maximum number of records to update per job run.

Table 7. User Deactivation
Property	Usage
sn_ca.user_deactivation.max_run_time	The maximum amount of time (in seconds) the Content Automation: Deactivate Campaign Users scheduled job runs. The scheduled job deactivates flagged users. The default value is 300 seconds.
sn_ca.user_deactivation.max_users_per_job	The maximum number of users to deactivate per job run. The Content Automation: Deactivate Campaign Users scheduled job runs every six hours by default. The default is 25,000 users.
Note: These properties determine limits on the Content Automation: Deactivate Campaign Users scheduled job for optimal performance. Customers with a large database should consider increasing this property after testing the impact it could have on performance.

Table 8. Purging
Property	Usage
sn_ca.purging.max_run_time	The maximum amount of time (in seconds) the Content Automation: Purge Campaign Data scheduled job runs.
sn_ca.purging.max_users_per_job	The maximum number of users to purge per job run.
sn_ca.purging.purge_after_campaign_end	Purge all campaigns when the end date is reached.
sn_ca.purging.days_after_campaign_end	The number of days after the campaign end date when campaigns are purged.
sn_ca.purging.purge_on_user_removed	Indicates if campaign information for a user should be purged after the user is removed from the campaign.
sn_ca.purging.days_after_user_removed	The number of days after a user is removed from a campaign to remove the campaign information.

Campaign Re-evaluation


Property	Usage
sn_ca.campaign.reevaluation_frequency	The default number of days to re-evaluate a campaign audience. The default is seven days. You can override this default from the Re-evaluate campaign and Re-evaluate frequency fields on the Campaign form. For more information, see Create a campaign.

Previous topic

Next topic

Release version

Properties installed with content automation

The Content Automation [com.sn_content_automation] plugin adds properties that determine how a campaign runs related to scheduled jobs and performance.

Scheduled Jobs

The following scheduled jobs work with properties to fine-tune and configure the behavior of Content Automation:

Content Automation Profile
Content Automation: Add Non-Portal Campaign Content
Content Automation: Calculate Campaign Engagements
Content Automation: Create To-dos
Content Automation: Deactivate Campaign Users
Content Automation: Evaluate Campaign Success Goals
Content Automation: Manage Content States
Content Automation: Process SNC analytics
Content Automation: Purge Campaign Data
Content Automation: Send Email Notifications
Content Automation: Send SMS Notifications
Content Automation: Update Campaign Audience

See Components installed with Content Automation.

Properties

To access Content Automation properties, navigate to Content Automation > Configurations > Properties.

Content Automation properties determine how the scheduled jobs run and help to ensure that there is limited impact on the performance of your instance.

Table 1. Approvals
Property	Usage
sn_ca.all_must_approve	Indicates that all approvers must approve any scheduled content prior to publishing it. If you check No, only one approver is required to publish a campaign.

Table 2. Add Users
Property	Usage
sn_ca.add_users.max_run_time	The maximum amount of time (in seconds) the Content Automation: Add users to Campaigns scheduled job runs. Limits the length of the scheduled job, but completes any work in progress and does not pick up any new work. Default value: 600
sn_ca.add_users.event_stagger.campaign	The amount of time between campaign events when a scheduled job runs. Staggering provides time for the events to be processed during the staggered time. Default value: 300 seconds
sn_ca.add_users.event_stagger.users	The amount of time between campaign events to add users when a scheduled job runs. Staggering provides time for the events to be processed during the staggered time. Default value: 900 seconds
sn_ca.add_users.max_events	The maximum number of events that users can be added for a campaign. Default value: 100
sn_ca.add_users.max_users_per_event	The maximum number of users you can add in a single event. Default value: 1000

Table 3. Non-Portal Content
Property	Usage
sn_ca.campaign.max_run_time	The maximum amount of time (in seconds) the Content Automation: Add Non-Portal Campaign Content scheduled job runs. Limits the length of the Content Automation: Send Email Notifications scheduled job, but completes any work in progress and does not pick up any new work. The default is 300 seconds.
sn_ca.campaign.max_records_process	The maximum number of people a campaign can target per scheduled job run. The default is 15,000.
sn_ca.campaign.max_records_create	The maximum number of records to create per job run.
sn_ca.campaign.pending.event_stagger	The number of seconds between each time the Content Automation: Add Non-Portal Campaign Content scheduled job runs to try to send non-portal content.
Note: These properties determine limits on non-portal content (emails and SMS). The Content Automation: Send Email Notifications scheduled job runs every hour by default and attempts to send non-portal content not sent in the first pass. Customers with a large database should consider increasing this property after testing the impact it could have on performance.

Table 4. To-do Content
Property	Usage
sn_ca.task.max_run_time	The maximum amount of time (in seconds) the Content Automation: Create To-dos scheduled job runs. Limits the length of the scheduled job, but completes any work in progress and does not pick up any new work. The default is 300 seconds.
sn_ca.task.max_records_create	The maximum number of records to create per scheduled job run. The default is 25,000.

Table 5. Notifications
Property	Usage
sn_ca.sms_notification.max_users_per_event	The maximum number of users to add per event for an SMS notification.
sn_ca.notification.max_run_time	The maximum amount of time (in seconds) the Content Automation: Send Notifications scheduled job runs.
sn_ca.notification.event_stagger	The amount of time between events when a scheduled job runs. Staggering provides time for the events to be processed during the staggered time. The default is 60 seconds.
sn_ca.notification.max_events	The maximum number of events to queue per job run.
sn_ca.notification.max_events	The maximum number of events to queue per job run for email notifications.
sn_ca.notification.max_users_per_event	The maximum number of users to add per event for email notifications.

Table 6. State Management
Property	Usage
sn_ca.state_management.max_run_time	The maximum amount of time (in seconds) the Content Automation: Manage Content States scheduled job runs.
sn_ca.state_management.max_records_update	The maximum number of records to update per job run.

Table 7. User Deactivation
Property	Usage
sn_ca.user_deactivation.max_run_time	The maximum amount of time (in seconds) the Content Automation: Deactivate Campaign Users scheduled job runs. The scheduled job deactivates flagged users. The default value is 300 seconds.
sn_ca.user_deactivation.max_users_per_job	The maximum number of users to deactivate per job run. The Content Automation: Deactivate Campaign Users scheduled job runs every six hours by default. The default is 25,000 users.
Note: These properties determine limits on the Content Automation: Deactivate Campaign Users scheduled job for optimal performance. Customers with a large database should consider increasing this property after testing the impact it could have on performance.

Table 8. Purging
Property	Usage
sn_ca.purging.max_run_time	The maximum amount of time (in seconds) the Content Automation: Purge Campaign Data scheduled job runs.
sn_ca.purging.max_users_per_job	The maximum number of users to purge per job run.
sn_ca.purging.purge_after_campaign_end	Purge all campaigns when the end date is reached.
sn_ca.purging.days_after_campaign_end	The number of days after the campaign end date when campaigns are purged.
sn_ca.purging.purge_on_user_removed	Indicates if campaign information for a user should be purged after the user is removed from the campaign.
sn_ca.purging.days_after_user_removed	The number of days after a user is removed from a campaign to remove the campaign information.

Campaign Re-evaluation


Property	Usage
sn_ca.campaign.reevaluation_frequency	The default number of days to re-evaluate a campaign audience. The default is seven days. You can override this default from the Re-evaluate campaign and Re-evaluate frequency fields on the Campaign form. For more information, see Create a campaign.

How search works:

Topics are ranked in search results by how closely they match your search terms

Properties installed with content automation

Properties installed with content automation

Scheduled Jobs

Properties

Campaign Re-evaluation

On this page

Properties installed with content automation

Properties installed with content automation

Scheduled Jobs

Properties

Campaign Re-evaluation

Log in to personalize your search results and subscribe to topics