Dispatch Console vs PSO InActive Resources 23R2

What is the reason for inactivating resources? Is this only a temporary deactivation? 

Hello Alexander,

Thank you for responding

It can be temporary deactivation or full deactivation when resource leaves.

1.Resource is not using IFS system and using other WFM system.When deactivated in IFS it should not be visible in console and assigned tasks unassigned and reallocated to other.In future resource can be reactivated.

2.Resource leaving company and fully deactivated. Assigned tasks get reallocated after the deactivation.

Thank you

I have confirmed this behavior in 24.1E.0 and created a ticket for it.

Thank you Alexander, Shall we consider it as Gap and will be addressed in future release or how we interpret this behaviour. Thank you

Hi all, we have the same observation from our side and would like to understand if indeed this is considered as a product gap and if it will be addressed in future releases. Thank you

When I receive an update of my ticket from R&D, I will share here.

We just upgraded to 2025R1 and it still appears to be broken, has anyone heard of a fix aside from removing the resource detail record ? 

Blocked or hidden resources are still shown in Dispatch Console, Resource Shift Gantt etc. to visualize any previous planning information. It is however not possible to create new allocations or shifts etc. when a resource is blocked.

To remove a resource from DC, clear the resource’s Scheduling Dataset or move it to a dummy one.

After that, Generate Schedules and Capacity and activate the toggle Remove Scheduling Dataset Deviations. This creates shifts without association to the Scheduling Dataset and ultimately removes the resource from DC.