GE0-806 Gcp8-System Consultant, Genesys Wfm Practice Questions

The key characteristic of deferred work is that it doesn't need to be handled the instant it arrives. This time flexibility allows workforce managers to schedule these tasks during periods of low immediate demand (e.g., between call volume peaks). This practice, known as 'workload leveling' or 'smoothing', fills agent idle time, increases overall productivity, and allows for a more stable and efficient staffing plan throughout the day.

This is the classic distinction between adherence and conformance.

• Adherence measures if the agent worked the scheduled quantity of time (e.g., scheduled for 8 hours, was logged in for 7.8 hours = high adherence).
• Conformance measures if the agent was doing the right activity at the right time (e.g., was scheduled for 'Inbound Calls' from 9-10 AM but was in 'Admin Work' state).
  A high adherence with low conformance means the agent was present but was not following the scheduled sequence of activities.

The Master/Primary architecture is designed for this type of resilience. The Primary WFM Server maintains a local cache of its site's configuration and schedule data. When the connection to the Master is lost, it enters a 'disconnected' mode and continues to serve its local clients (WFM Web, etc.) using this cached data. Core functions like adherence tracking and viewing existing schedules will continue. However, any configuration changes made centrally on the Master Server will not be synchronized to the Primary Server until the connection is restored.

The most CPU-intensive task performed by the WFM Data Aggregator is the collection, processing, and aggregation of historical data. In a large contact center, it receives a constant stream of raw agent state change events from Stat Server. It must process each event, compare it against the schedule, calculate adherence, and then summarize this data into historical records in the database. This continuous, high-volume data crunching is the primary driver of its CPU usage.

This is the primary method for WFM Server redundancy. The Backup server continuously synchronizes with the Master (or Primary) server. If the main server fails, the Backup server can be promoted to take over its role, minimizing data loss and service interruption.

Components like the Data Aggregator and Scheduler can be configured for high availability using the standard Genesys Management Framework (LCA/SCS). This allows for automatic failover to a backup instance if the primary instance becomes unresponsive.

This is the correct approach because Genesys WFM's object hierarchy (Business Unit > Site > Team) allows for inheritance. By associating global items with the top-level Business Unit, they automatically apply to all child Sites. Site-specific items can then be associated directly with the Site objects, ensuring they only affect the intended location. This method is highly scalable, reduces redundant configuration, and simplifies maintenance. Creating items for every site individually is inefficient. A single global calendar becomes unmanageable and prone to errors.

Shifts define the start and end times, paid hours, and break profiles (e.g., the 12-hour day shift and 12-hour night shift). These are the fundamental building blocks of any schedule.

A Rotating Pattern is the object used to define the sequence of shifts and days off over a cycle (e.g., Day-Day-Night-Night-Off-Off-Off-Off). It links the individual Shift objects into the desired repeating pattern.

In Genesys WFM, the availability of specific time-off types for agents is controlled by their assigned Contract. The Contract object links agents to specific rules, including which paid and unpaid time-off items they are eligible to request. If the 'Unpaid Time Off' item is not included in the Contract's configuration, it will not appear as an option for agents assigned to that contract, regardless of their security permissions.

This is the most automated and fair method. The Shift Bidding module is designed for such scenarios. By creating a custom statistic to track accumulated overtime, you can configure the bidding rules to grant bids based on this metric, ensuring agents with the lowest overtime are prioritized. This automates the fairness policy, provides transparency, and reduces manual supervisor effort.

Genesys WFM's shift trading module allows for the configuration of complex validation rules. An administrator can define a rule that triggers upon a trade request, calculates the resulting weekly hours for both agents, and compares it to a set threshold (48 hours). Based on the outcome, the workflow can be configured for automatic approval or for routing to a supervisor's approval queue, enabling the required conditional logic.