General rule parameters
The General rule parameters are related to basic information about the rule, including the name, description, allowed date and time ranges, expiration policy, allowed 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., and scheduling component.
Parameter |
Description |
---|---|
Name |
Name of the rule. The rule name must be unique for the tenant. |
Description |
Description of the rule. |
Requested days |
|
Start date / End date |
Date and time range during which requests can be submitted. Note the following:
If you do not want to limit the end date and time of the request, select No end date. |
Recurrence |
Determines whether the rule is valid during the entire defined date range, or only on specific days:
|
Expiration policy NOTE: Expired requests can no longer be withdrawn, approved, or denied. Requests can be expired, regardless of status. For example, Pending, Approved, and Denied requests can be expired, according to the expiration policy. When you withdraw a request, it becomes expired. |
|
Request will expire |
Determines when submitted requests that adhere to the rule definition expire:
|
Activity |
|
Activity |
Defines the activity associated with the event for which users are able to submit requests. For example, if this parameter is set to Break, the rule applies to requests that specify an action for the Break activity. |
Schedule as |
Defines how the activity is scheduled on the Calendar. In WFM, an activity can serve multiple purposes on the schedule. For example, an Admin activity can be scheduled as a working shift event Time period in WFM when employees are scheduled for specific activities, other than the main shift activity. Shift events can either be productive or unproductive, and can be associated with activities such as Phone, Email, Break and Lunch. or as a calendar event Scheduled event in WFM that is manually created on the schedule, can be a single instance or recurring event, and can have one or multiple attendees. Examples of calendar events are meetings or training sessions.. When a request to add a specific activity and to schedule it as a specific component is approved in Request Anything, the schedule is updated according to the selection. For example, for the Activity parameter, you select Admin. For the Schedule as parameter, you select calendar event. Therefore, the system schedules a calendar event (and not, for example, a working shift Work period in WFM that has a definite length. event) associated with the Admin activity. A request to move or delete an event is only allowed if the type defined in the rule and the type on the schedule are the same. For example, an Admin calendar event is only deleted if the rule also defines calendar event as the type. The available options are based on the activity definitions in WFM. Valid values include: Working shift event, Non-working shift event, Calendar event, Unavailability event, and Time-off event. If the employee submits a request to add or move a shift event before or after a shift (and not during the shift), and the request is approved, the system creates an overtime extension for the employee's schedule. |