Bundling Conditions

The application uses these conditions to determine the activities which activities can be bundled together:

• activities must be in the Pending status

• activities must have the same bundling key (for Immediate Routing)

• activities must have the same bundling key or the same address (for Bulk Routing)

• activities must be within the defined interval of dates (for Immediate Routing, see below)

• non-scheduled activities must have an empty SLA start value or a SLA start value within the defined interval of dates (for Immediate Routing, see below)

When the application finds the acceptable destination route, it checks these assignment constraints for all activities in the bundle:

• work zones—the resource's work zone must match that of the activity

• work skills—the resource's work skills must match the work skills required by the activity

• Resource preference—the activity may be assigned only to required or preferred resources, if specified

• Service window—the activity service window should be observed

• Access hours – the activity access hours should be observed

• SLA start—the SLA start of the activity should be observed

• SLA end—the SLA end of the activity should be observed

• Maximum duration if a single bundle— 8 hours