System-wide configuration options
System-wide options, such as licensed languages, password policy, and general settings for Scorecards Product that assists agents, supervisors and all contact center employees to focus on critical aspects of their performance and identify opportunities for improvement. and Workforce Management affect all components within the system.
The options that are available depend on product licenses applied.
User Defined Fields
To include information unique to your environment, you can define up to 10 custom fields. You do not have to define 10, but you must define the fields consecutively. These fields are displayed in the employee profiles in User Management Module that an administrator uses to create a profile for each employee in their organization., My Profile modules and in Forecasting and Scheduling.
System configuration
|
Parameter |
Description |
|---|---|
|
Application Context Path |
The context path that the current application is using. The application uses this path to embed links within a URL to allow a user to select the link and sign back in. This field is automatically populated. If you are using a firewall or load balancer, verify that this setting is correct. |
|
Sign-in Screen Message |
Optional: Any message entered here appears when users sign in to the system. |
|
Return Server Hostname instead of IP to Client |
When selected, the system returns a host name instead of an IP address to Forecasting and Scheduling for load balancing. This flexibility has been added for use with the Single Sign-On (SSO) feature. |
|
JavaScript Load Error Detection |
Enables a diagnostic tool to run to detect JavaScript loading errors (typically caused by network congestion). Only turn on this setting when requested by Technical Support. |
|
Is System Configured to Support SSO (Trusted Login) |
The Single Sign-On (SSO) feature enables user authentication using Windows sign-in credentials. To use SSO, a user must have a system user account with the same user name as the Windows user name. When this setting is selected, the sign-in page has a Trusted Login check box. When the Trusted Login box is selected, the user name and password fields are not available. When users select Sign In, they are authenticated automatically using Windows credentials. If a user clears Trusted Login, the user name and password fields are enabled. The user can then enter any valid user name and password to sign in to the application. |
|
Is in Non-Primary Mode |
Primary Mode is the default for editing user information, such as user name, password, and account status, on the Users page and the My Profile section. In non-primary mode, another server, which is now the primary server, maintains user information. The user information is synchronized to the non-primary server. When non-primary mode is enabled, user information, employee names, email addresses, end dates, and switch IDs cannot be edited. In addition, Import, Create, Terminate, and Delete buttons, and the [Register] and [Reset Password] buttons on the sign-in page are also unavailable. |
|
Is External Authentication Token Supported |
Specifies whether external tokens are supported. |
|
External Token Authentication Server URL |
Specifies the URL of the external authentication server used to authenticate an external token. |
Password policy
Password policies include settings to protect user accounts and dictate what is permitted when users create passwords. These settings apply also to the System Account.
|
Setting |
Description |
|---|---|
|
Activate Password Policy |
If your security realm is modifiable, such as DBRealm, enabling this setting enforces the password policy as customized using the remaining parameters in this section. Default: Not enabled |
|
Validate Policy On Login |
When enabled, the active password policy is enforced the first time that users sign in after the Activate Password Policy is enabled. When not enabled, users who have passwords that do not adhere to the active password policy can continue to use the invalid password until it is changed. Default: Not enabled |
|
Password Minimum Length |
The minimum number of characters required for a user password. Accepted values are from 8 to 30 characters. The default is 8 characters. |
|
Password Maximum Length |
The maximum number of characters allowed for a user password. Accepted values are from 8 to 40 characters. The default is 30 characters. |
|
Password Maximum Age (days) |
The number of days that a user password is valid. After the specified number of days, the password expires and the user is prompted to reset it. The expiration count resets each time a user changes the password. A value of zero keeps passwords alive forever. Accepted values are 0–180 days. Default: 30 days |
|
Password History (number) |
The number of previous passwords stored in the system for a user account. When a user tries to reset the password, the user is forced not to use any of the stored passwords. A value of zero for this field disables the password history requirement. Accepted values are 0–30. Default: 5 |
|
Password Pattern |
The format to which all user passwords must conform. The options available include No Pattern, Complex Pattern, and Custom Pattern. When you specify any of the three Password Pattern options, all other policy rules that were specified, such as Password Minimum Length and Password Maximum Length, also apply to the passwords. Regardless of the password pattern chosen, a user password cannot include the user's username or birth date. No Pattern - Select this option to turn off password pattern validation. This option is the default selection. The format of the password is at the discretion of the user. Users can create passwords containing any combination of uppercase English characters, lower case English characters, numbers, or special characters (~!@#$%^&*_-+=`|\(){}[]:;"'<>,.?/). The password can also be made of all uppercase or lowercase, numerical or even special characters. Complex Pattern - Select this option to require passwords to include any three of the four following items:
For example, one user can create a password that includes one uppercase English character, one special character, and one number. Another user can create a password that includes one uppercase English character, one lowercase English character, and one number. Both passwords are valid because each password contains three of the four items. If a user creates a password that does not include three of the four items, a message displays to the user indicating that the password must contain three of the four items. Custom Pattern - Select this option to require passwords to include the items you select from the Custom Pattern list. The selectable items in the Custom Pattern list include:
For example, if you select one uppercase English character and one number, all passwords must include those two items. If a user creates a password that does not include the specified items, a message displays to the user indicating that the password must contain the specified items. |
Account locking policy
Administrators can define settings for locking user accounts after authentication fails.
|
Setting |
Description |
|---|---|
|
Activate Account Locking Policy |
When enabled, a user account status can be automatically switched to locked based on the other settings listed in this section. If a user account is locked, clearing this setting does not necessarily unlock the account. The User Management policy also affects the account. Users with locked accounts cannot access the system unless both this policy and the User Management policy are unlocked. Default: Not enabled |
|
Enable Account Locking for System Account |
When enabled, the Account Locking Policy is applied to the System account when the policy is activated. If the Account Locking Policy is activated, but this option is not selected, the lockout threshold, inactivity, or other locking parameters do not affect the System account. Default: Not enabled |
|
Lockout Threshold |
This parameter only applies to failed sign-in attempts. The number supplied specifies the number of consecutive failed attempts can occur before a user account is locked. The counter resets when the sign-in is successful. Once the account is locked, a system administrator can unlock it or it is automatically unlocked after the time specified by the Lockout Duration (minutes) parameter. A value of zero prevents locking of accounts from failed password attempts and gives users infinite chances to enter a password. Accepted: 0–30 Default: 3 |
|
Lockout Duration (minutes) |
This parameter only applies once the user account has been locked. The number supplied specifies the number of minutes a locked-out account (because of multiple failed sign-in attempts) remains locked before being automatically unlocked. A value of zero prevents automatic unlocking of locked accounts and requires an administrator to unlock the user account. Accepted: 0–30 Default: 30 |
|
Lockout Inactive User Period (days) |
Specifies the number of days of user inactivity allowed to pass before a user account is automatically locked. After the inactive user account is locked, it cannot be automatically unlocked. Only an administrator must unlock it. A value of zero prevents automatic locking of inactive user accounts. Accepted: 0–180 Default: 60 |
System proxy settings (OpenID)
If the IDP communication server is not on the premises, a proxy server is needed to control access for token validation.
|
Setting |
Description |
|---|---|
|
Host Name |
Host name or IP address of proxy server. Alphanumeric characters only. |
|
Port Number |
5-digit port number of proxy host. |
Integration Server mapping
The following settings control the display of unmapped activities and reason codes Representation of an external data source event in WFM, which consists of an Event Mode and Event Reason..
|
Setting |
Description |
|---|---|
|
Show Unmapped Activities for Time Collection Mapping |
Display activities and reason codes that are not mapped to one another. |
|
Show Mapped Data Source Group for Queue Mapping |
Displays the data source groups Groups that represent an external identifier of work in WFM. Data source groups are linked to queues. that are mapped to other queues, when mapping a queue Entity that represents demand in WFM. Queues help predict workload by multiplying the volume of customer interactions by their expected handling time. to data source Third-party systems that provide data to the system, including employee and device states, and data change events. Typical data sources are phone switches, PBXs, or LANs. groups. |
Integration Server configuration
The following settings affect the Integration Server cache. The Integration Server must be rebooted before changes to these parameters take place.
|
Setting |
Description |
|---|---|
|
Cache Refresh Sleep Time |
Rate at which the cache is refreshed. A low value means that the cache is in sync frequently but also consumes CPU cycles. A high value loads the system to a lesser extent with a proportional risk of de-synchronization. Default: 300,000 milliseconds. |
|
Cache Retry Count |
When the system determines that the cache must be reloaded, it waits to see if the database is still being changed. It does not reload the cache until the changes have stopped. This parameter sets the number of times it checks for the system to stabilize before it gives up and reloads the cache. |
|
Cache Retry Interval |
The maximum amount of time to wait before checking to see if the cache needs to be refreshed. The system actually checks for cache changes more frequently but slows down over time until it checks at the rate specified by this parameter. |
Reports
In this area, set the parameters for the SSRS server. The application server must be rebooted before changes to these parameters take place.
|
Setting |
Description |
|---|---|
|
Enable Report Trimmer |
When selected, the Report Trimmer job is scheduled to run. When cleared, the report does not run, no matter what other Report Trimmer settings are. Default: Not enabled |
|
Report Trimmer Frequency (hours) |
The frequency at which the Workforce Management application requests the Report Trimmer job to remove expired or excessive report instances from the system. The value 0 means that Report Trimmer does not run, even if the parameter Enable Report Trimmer has been checked. The default value for this parameter is 24. Changes to this parameter take effect the next time the application server is rebooted.
|
|
Trim Expired Instances (older than N days) |
Report Trimmer uses the value for this property to remove expired instances. The value 0 means that expired instances are not trimmed. The default value is 31. Changes to this parameter take effect the next time the application server is rebooted. |
|
Keep Maximum Number of Unmanaged Instances per report |
Report Trimmer uses this value to remove excessive unmanaged ("run now") instances for each report for each user. The value 0 means that unmanaged instances are not trimmed. Changes to this setting take effect immediately. The changes are applied for each user on each report the next time that user enters the Reports page and creates an unmanaged instance for that report. Default: 5 |
|
Keep Maximum Number of Scheduled Instances per Schedule |
Report Trimmer uses the value for this property to trim excessive managed (scheduled) instances for each report schedule.
|
|
Trim Adhoc Orphan Reports |
Ensures that ad hoc reports that were created by an employee who is no longer with the company are removed from the store on the SSRS server. |
|
Enable custom reports deployed by service provider user to tenant user |
To make custom reports deployed by the SPA (Service Provider Administrator) available for all tenants, select this option . When this feature is enabled, custom reports deployed by the SPA appear on the Reports - Setup - Access Rights screen. The privileges to view those reports can be granted to a tenant user role Entity assigned to users to define their access permissions to applications.. This feature is available in releases 15.2 HFR7 718 and higher. |
|
Max Data-refresh Lookback (days) |
The maximum number of days in the past for which a report dump refreshes data. |
|
Dump Chunk Size |
During report dump, this parameter determines the number of employees in a single report dump chunk. You do not usually need to modify this parameter. However, if users get time-out errors during a report dump, reduce the default value of 100 to eliminate the time-out. |
|
Dump Thread Number |
The number of threads to use with Report Dump. Default: 1 |
|
Dump Max Retry |
When many users are running real-time reports at the same time (which triggers a report dump), database collisions sometimes occur. This setting is the number of retries that can be attempted if report generation failed. Usually, you do not need to change this value. Default: 10 |
|
Request Timeout (minutes) |
How long the system waits before timing out a report request. The default setting is 30. When running reports from the WFO application, reports containing large data sets can time out. In this case, ask your system administrator to increase the setting of this parameter. Some experimentation with this setting can be required to determine the proper setting for a particular report. If you change this setting to a value greater than 30, you must also change the report time out setting on the SSRS report server. The default report time out setting for the SSRS server is 1800 seconds/30 minutes. Change the setting on the SSRS server to match the value for this setting to prevent the SSRS server from timing out. |
|
Status Polling Frequency (seconds) |
The frequency at which the current report data is requested. |
|
Use Live Data For Adherence Reports |
Reports are typically run against data that is prepared at regular intervals, typically once a day. However, if this option is checked, adherence Measure used in Workforce Management (WFM) to determine how well an employee’s scheduled activities match their actual, real-time activities. reports also process data that has been entered in the system since then. These reports are referred to as real-time reports. |
My Time integration
Enables a special Client-Side integration with Kana.
Only change these settings at the request of Technical Support.
Time records
These settings affect the behavior of the Tracking module. The web server must be rebooted before changes to these parameters take place.
|
Setting |
Description |
|---|---|
|
Automatically Close If Last Event Is Longer Than (minutes) |
The duration in minutes of the last event in a time record before Workforce Management automatically closes it. |
|
Automatically Merge Time Records |
Workforce Management merges adjacent time records. |
|
Automatically Merge Time Records If The Time Interval Between Them Is Less Than (minutes) |
Workforce Management merges time records that have less than this time between them. |
|
Lookback Interval (minutes) |
To improve performance, you can limit how far back in time Workforce Management looks for time records. Set the look back interval to the longest-anticipated event for this system. Default: 480 Example: There is an organization where:
If an agent has activity Core component of both schedules and time records in Workforce Management (WFM). When an employee performs any kind of work, activities specify the scheduled work and capture employee adherence to their schedule. past the time limit, the Time Record Auto Close adapter is triggered when the time limit is reached. In this case, the earliest that the Time Record Auto Close adapter can run is 4:00 AM EST. The calculation is based on the length of the longest event (five hours) after the latest shift end time (11:00 PM). The length of time that the Time Record Auto Close adapter then needs to look back is: ((<Hours from midnight when the Time Record Auto Close adapter runs>) + (<time from the earliest shift end to midnight>))*60 = (four hours + nine hours) or 13 hours*60 = 780 minutes. |
|
Eliminate Zero Duration Entries |
When enabled, events with zero duration are deleted. |
Quick view
|
Setting |
Description |
|---|---|
|
Show Organization Column |
When selected, a column showing the agent organization is shown on the Quick View page. |
Scorecards
The configuration settings affect the way that Scorecards processes data.
|
Settings |
Description |
|---|---|
|
%Met - Count Only People With Scores |
If checked, only those employees with scores are used in the % Met calculation. In addition, the list of under-performing employees only contains employees with scores. |
|
Convert Null Values to Zeros. |
When the value of a KPI formula is calculated, some source measures can have null values. This situation typically occurs when there is no data in the source. This setting causes the calculation engine to treat null values in the source measure as zero. Example: A KPI uses the formula bm1+bm2, where bm1 is null. If the check box is selected, the calculation engine returns bm2. If the check box is not selected, the calculation engine returns a value of null, the equivalent of no score. When there is no score, the value associated with bm2 is not shown. |
|
Audit Source Measures |
Turns on or off the auditing of any insertions or updates of source measures entering Scorecards. The audit is stored in the table AUFACTBASEMEASURE in the database BPWAREHOUSEDB. |
|
Enable Period to Date Scorecards |
Turns on or off score calculations before the end of the period. Users expect to be able to access Weekly and Monthly scores before the completion of the period. Period-to-Date scores are calculated by running the Scorecards – Calc Engine adapter for a period before all days in that period have been populated. Enabling this feature can adversely affect performance of the Workforce Optimization solution. KPIs that use source measures that are loaded on a weekly or monthly basis (and not daily) do not work with the period-to-date feature. |
|
Enable Calculation Engine Performance Diagnostics |
Turns on or off writing calculation engine performance diagnostics to the log table WHPERFORMANCELOG in the database BPWAREHOUSEDB. |
|
Maximum number of days to recalculate (per each calc engine run) |
The maximum number of days to recalculate (per each calculating engine run). Default: 5 |
|
Maximum recalculation time (in minutes) |
The maximum recalculation time (in minutes). Default: 60 |
|
Maximum numbers of periods |
The maximum number of periods users can see in Scorecards KPI Trends view For the last drop-down. Also, the maximum number or periods users can see in the Scorecards History view on the Show list. Default: 30 Accepted: 4–30 |
|
Show “Filter Out Of Sync” warnings |
Turns on or off the notification displayed when a Scorecards filter becomes invalid or inconsistent: "The current Scorecard filter has become inconsistent because of Administrator changes to the Configuration. Edit and save the current filter." Deleted KPIs, changes to access rights, and other changes can trigger this message. Editing and saving the filter creates a filter that is valid at its time of creation. |
|
Enable Supervisor Rollup |
Turns on or off aggregation of employee source measure and KPI values to the supervisor level during KPI calculation. |
|
Maximum number of interactions to retrieve for the KPI Drill to Interactions feature. Default: 20 Maximum: 50 |
|
|
Custom Drill to Interactions <URL #> and Data Source <#> |
Settings required to configure the KPI Drill to Interactions feature to work with an external system. A maximum of five custom URLs and associated data sources can be configured for the KPI Drill to Interactions feature.
|
|
Intraday Interval Length (Minutes) |
Number of minutes between each calculation of values for Intraday KPIs. Default: 60 |
Map service
After you activate your subscription to your third-party mapping service, Mapbox, you can map KPIs by location in a portlet Visual building block in an application that is interchangeable, depending on system or user configurations (also known as a widget)..
To use the Performance Map feature, Map box must be enabled for users. If it is not set up correctly or not set up, an error message directs users to their administrator. For assistance with setup, contact The entire communication experience for a customer, from beginning to end. your services representative.
Application server cache
Enables the cache parameters.
It is possible to set each cache to refresh at small intervals. However, refreshing large caches at small intervals can cause serious system performance issues.
Default: 0 (for no refresh)
Quality Monitoring
Set the default timeout for recording interactions.
|
Setting |
Description |
|---|---|
|
Interaction Recording Timeout (minutes) |
Time out duration for recordings in minutes. A background process runs every 5 minutes and stops all recordings that have exceeded this setting. Default: 10 |
Activity display names for desktop monitoring
If you are licensed for Desktop Monitoring, you can set the names of the Actual and Desktop activity lines for the Adherence page.
|
Setting |
Description |
|---|---|
|
Primary Activity Display Name |
The display name of the actual line on the Adherence page. |
|
Secondary Activity Display Name |
This item is only displayed for Desktop Monitoring licenses. Specifies the display name of the desktop activity line on the Adherence page. |
EM alarm collection
You set parameters for the collection Group of back-office Contributions from one or more employees connected to a single customer or account captured by DPA. Collections are used for analyzing and improving back-office efficiency and quality. of alarm data from each Recorder Manager installation in the system. Alarm data can be collected from each Recorder Manager on a recurring basis, such as every 60 seconds and updates sent to the Enterprise Manager.
|
Setting |
Description |
|---|---|
|
Maximum Number of Threads |
Maximum number of threads available to send Recorder Manager (RM) requests. Because each request to an RM is made on a separate thread, this value is also the maximum number of concurrent RM requests. Default: 10 |
|
Minimum Number of Threads |
Minimum number of threads available to send RM requests. Default: 1 |
|
Thread Execution Delay (milliseconds) |
The delay time (in milliseconds) between a thread completing the execution of a task and starting the execution of a new task. Accepted: 0, 50, 150, 200, 250, or 300 Default: 150 |
|
Polling Enabled |
Turns on or off the polling of each RM for its alarm status. Default: Selected (on) |
|
Polling Interval (milliseconds) |
The time, in milliseconds, between the polling of each RM server for its alarm status. Accepted: 30000, 60000, 90000, or 120000 Default: 30000 |
|
Disable Sending EMail on Failure |
Turns on or off email notification of alarm failure. When selected, this setting turns notification off. Default: Not selected |
EM reliable messaging
If you are licensed for Enterprise Manager, you can set parameters for sending messages to installations in the enterprise such as Recorders, Viewers, and Analyzers.
|
Setting |
Description |
|---|---|
|
Maximum Number of Threads |
Maximum number of threads available to send Recorder Manager (RM) requests. Because each request to an RM is made on a separate thread, this value is also the maximum number of concurrent RM requests. Default: 10 |
|
Minimum Number of Threads |
Minimum number of threads available to send RM requests. Default: 1 |
|
Thread Execution Delay (milliseconds) |
The delay time (in milliseconds) between a thread completing the execution of a task and starting the execution of a new task. Accepted: 0, 50, 150, 200, 250, or 300 Default: 150 |
|
Message Data use the Cut command Interval (days) |
The time to wait between checks for message data that is to be deleted (in days). Default: 1 |
|
Message Job Purge Interval (days) |
The time to wait between checks for message jobs that are to be deleted (in days). Default: 1 |
|
Message Job Age (days) |
The age of a message job (in days) before it can be deleted. Any completed message job older than the number of days is purged from the database. Default: 1 |
|
Scheduled Job Timer Interval (milliseconds) |
Amount of time (in milliseconds) to wait between checks for scheduled jobs that are ready to be sent. Default: 60000 |
|
Viewer Web Server Timeout (milliseconds) |
Amount of time in milliseconds that the adapter waits for a Viewer to process a message. Once this amount of time has passed, the adapter considers the message failed and reattempts on the next interval. Default: 300000. |
|
Client Timeout (milliseconds) |
Amount of time in milliseconds that the adapter waits before timing out a client request from Enterprise Manager. Use this setting to prevent unresponsiveness while the adapter is processing large configuration messages. Once a time-out occurs, the Configuration Status page displays the status of the message. Default: 15000 |
EM SQL Server Express job schedules
If you are licensed for Enterprise Manager and you use a SQL Server Express database, you can specify the schedules for database jobs. These settings are ignored if any other edition of SQL Server is running.
|
Setting |
Description |
|---|---|
|
Schedule for DB Cleanup Job |
Default: The job is scheduled to run every day at midnight. |
|
Schedule for DB Growth Job |
Default: The job is scheduled to run at 12:30 AM on the last Sunday of every month. |
|
Schedule for DB Optimize Statistics Job |
Default: The job is scheduled to run every day at 06:00 AM. |
|
Schedule for DB Optimize Indexes Job |
Default: The job is scheduled to run at 01:30 AM on the last Sunday of every month. |
Values to set schedules
To set the schedules, use specific values and characters with special meanings.
|
Field Name |
Allowed Values |
Allowed Special Characters |
|---|---|---|
|
Seconds |
0–59 |
, - * / |
|
Minutes |
0–59 |
, - * / |
|
Hours |
0–23 |
, - * / |
|
Day-of-month |
1–31 |
, - * ? / L W C |
|
Month |
1–12 or JAN-DEC |
, - * / |
|
Day-of-week |
1–7 or SUN-SAT |
, - * ? / L C # |
Special characters
|
Special |
Usage |
|---|---|
|
* |
Used to specify all values. For example, * in the Minutes field means every minute. |
|
? |
Is allowed for the day-of-month and day-of-week fields to indicate no specific value. This character is useful when you need to specify something in one of the two fields, but not the other. |
|
- |
Is used to specify ranges. For example, 10–12 in the Hours field means the hours 10, 11, and 12. |
|
, |
Is used to specify more values. For example, MON,WED,FRI in the Day-of-week field means the days Monday, Wednesday, and Friday. |
|
/ |
Is used to specify increments. For example:
You can also specify / after the * character; in this case, * is equivalent to having 0 before the /. |
|
L |
Is allowed for the Day-of-month and Day-of-week fields. This character is short-hand for last, but it has a different meaning in each of the two fields. Example: The value L in the Day-of-month field means the last day of the month. That is, day 31 for January, day 28 for February on non-leap years, and so on. If used in the Day-of-week field by itself, it means 7 or SAT. But if used in the Day-of-week field after another value, it means the last xxx day of the month. For example, 6L means the last Friday of the month. When using the L option, it is important not to specify lists, or ranges of values, because you can get confusing results. |
|
W |
Is allowed for the Day-of-month field. This character is used to specify the weekday (Monday-Friday) nearest the specified day. Example: If you specify 15W as the value for the day-of-month field, the meaning is the nearest weekday to the 15th of the month. So, if the 15th is a Saturday, the trigger fires on Friday the 14th. If the 15th is a Sunday, the trigger fires on Monday the 16th. When the 15th is a Tuesday, then the trigger fires on Tuesday the 15th. However if you specify 1W as the value for Day-of-month, and the 1st is a Saturday, the trigger fires on Monday the 3rd. The trigger does not jump over the boundary of a month. The W character can only be specified when the Day-of-month field specifies a single day, not a range, or list of days. |
|
# |
Is allowed for the Day-of-week field. This character is used to specify the nth XXX day of the month. Example: The value of 6#3 in the Day-of-week field means the third Friday of the month (day 6 = Friday and #3 = the third one in the month). Other examples:
|
|
C |
Is allowed for the Day-of-month and Day-of-week fields. This character is short-hand for calendar. Values are calculated against the associated calendar, if any. If no calendar is associated, then C is equivalent to having an all-inclusive calendar. A value of 5C in the Day-of-month field means the first day included by the calendar on or after the 5th. A value of 1C in the Day-of-week field means the first day included by the calendar on or after Sunday. |
Examples of schedule expressions
|
Expression |
Meaning |
|---|---|
|
0 0 12 * * ? |
Run at 12 p.m. (noon) every day. |
|
0 15 10 ? * * |
Run at 10:15 a.m. every day. |
|
0 15 10 * * ? |
Run at 10:15 a.m. every day. |
|
0 15 10 * * ? * |
Run at 10:15 a.m. every day. |
|
0 15 10 * * ? 2005 |
Run at 10:15 a.m. every day during the year 2005. |
|
0 * 14 * * ? |
Run every minute, starting at 2 p.m. and ending at 2:59 p.m., every day. |
|
0 0/5 14 * * ? |
Run every five minutes, starting at 2 p.m. and ending at 2:55 p.m., every day. |
|
0 0/5 14,18 * * ? |
Run every five minutes, starting at 2 p.m. and ending at 2:55 p.m., AND fire every five minutes, starting at 6 p.m. and ending at 6:55 p.m., every day. |
|
0 0-5 14 * * ? |
Run every minute starting at 2 p.m. and ending at 2:05 p.m., every day. |
|
0 10,44 14 ? 3 WED |
Run at 2:10 p.m. and at 2:44 p.m. every Wednesday in the month of March. |
|
0 15 10 ? * MON-FRI |
Run at 10:15 a.m. every Monday, Tuesday, Wednesday, Thursday, and Friday. |
|
0 15 10 15 * ? |
Run at 10:15 a.m. on the 15th day of every month. |
|
0 15 10 L * ? |
Run at 10:15 a.m. on the last day of every month. |
|
0 15 10 ? * 6L |
Run at 10:15 a.m. on the last Friday of every month. |
|
0 15 10 ? * 6L |
Run at 10:15 a.m. on the last Friday of every month. |
|
0 15 10 ? * 6#3 |
Run at 10:15 a.m. on the third Friday of every month. |
eLearning settings
This setting is only available when you are licensed for eLearning Product that provides hard and soft skills training, applicable for the entire employee life cycle (before, during, and after the hiring process), and includes training assessment and design tools..
|
Setting |
Description |
|---|---|
|
Assign Lessons No More Than Once Every (days) |
The frequency with which lessons are assigned. |
Scheduled alerts job configuration
|
Setting |
Description |
|---|---|
|
Times to retry before de-activating job |
The number of times that the system attempts to run the scheduled job before it removes it from the job queue. Default: 3 |
|
Time interval for reactivating job (in hours) |
The amount of time that the system waits before resuming attempts to run a job that was deactivated due to failed attempts. Default: 1 |
Google OpenID settings
If Workforce Optimization is registered with Google, and users in your organization have appropriate privileges, they can use Google credentials, rather than WFO credentials, to sign in to WFO.
|
Setting |
Description |
|---|---|
|
Enable Registration using Google OpenID |
Turns on and turns off the ability to use Google authentication to access WFO. The feature must be fully configured to be operational. |
|
Authorization URL Access-Token URL Call-back URL Client ID Client Secret Key |
The values for these settings are provided when you register WFO with Google. |