Change Request Management feature settings

Request Management feature settings control where request validations alerts are shown for managers and employees, the maximum number of requests shown on the Employee Requests page for managers, and how request processing is performed. Except for the Maximum requests per page setting, all settings affect performance.

When a system is initially configured, do not change the performance settings. Only consider making changes to these settings when specific, serious issues with system performance and request processing occur. These issues can occur when an extremely high volume of requests is submitted in a short time.

These settings are not available in a multi-tenant environment.

Available options to address issues

Settings related to viewing request validation alerts include the following:

Determine whether the Alerts checkbox is selected and alerts are displayed on the Request List page by default upon login. When navigating to this page, you can select or unselect the Alerts checkbox to view alerts. To improve system performance, it is highly recommended to select the following option for this setting: Alerts not selected and no alerts are displayed by default upon login.
For managers, you can limit net staffing validations and keep the other validations visible on both the request list and request details.
For managers, lowering the maximum number of requests that can be viewed on their request list, the Employee Requests page. This option applies when the default number of 30 was already changed to a much higher number.
Configure the maximum number of employee requests returned by the V2 Get My Requests API. By default, the Maximum requests returned by the V2 Get My Requests API setting is zero (0), which represents an unlimited number of requests. To limit the number of requests, select any value from 1-2000 for this setting.
To limit the date range used on the Employee Requests page, configure a specific number of months for the setting, Maximum date range (in months) when filtering employee requests. By default, the Maximum date range (in months) when filtering employee requests setting is zero (0), which represents an unlimited number of months. To limit the date range, select any value (other than zero) for this setting.
Using queues for auto processing in any or all request types. Processing requests in a queue Entity that represents demand in WFM. Queues help predict workload by multiplying the volume of customer interactions by their expected handling time. frees up resources for other processes in WFO. Example: Use this option for shift bidding Feature in WFM that allows employees to submit requests (bids) for selected shift assignments. when you expect an extremely high volume of shift Work period in WFM that has a definite length. bid request to be submitted in a short time.
Using sequential processing for time off pools. The default option provides faster processing. However, the sequential processing option improves staffing accuracy when a high volume of requests are submitted in a short time for the same time off pool Group of employees in WFM to which time off is allocated..

Procedure

Go to System Management Module that allows performing suite-wide system management activities from a single, Web-based application, the Enterprise Manager.. Under General Settings, select Feature Settings.
Select the Request Management tab.
Change the defaults that are needed to address your issues.

Before making any changes, contact Technical Support.
Select the Save icon .