@Tharun K T  End users can schedule their unavailability and transfer cases through the Operator ID settings in the Dev Studio. They can define their unavailability period and substitute operator under the 'Work' tab of their Operator ID. However, please note that the unavailability settings only affect routing activities and do not prevent the user from logging in, entering work items, or completing assignments already on their worklist. It also does not prevent another operator or manager from transferring assignments to the worklist. If more substantial abilities are required, you would need to extend any existing rules that are traversed during the execution path to provide those abilities. You can use the Pega tracer to find out what extension rules are actually traversed.

To schedule unavailability and transfer cases, an end user can follow these steps:

1. In the Case Manager portal, select the Operator icon in the top right to open their profile.

2. In the profile, select Actions > Edit Availability.

3. Set the unavailability period by specifying the start and end dates.

4. Ensure that a substitute operator is mentioned for the unavailability period.

Additionally, in the process, a when condition can be written to check if the current date falls between the unavailability period. If it does, the case can be transferred to the substitute operator using the `work-.pxTransferAssignment` activity or by using routing options in the assignment shape

⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

Operator Unavailability is not working

Defining operator availability

Operator Unavailable option is not working

Pull assignment from operator's worklist when he/she is absent

S > Staff Availability

and

How should i trasnfer the case to B operator when A operator is not available