Unable to Capture Updated Operator Unavailability Data in Constellation Portal

Hi @Yaswanth_G , @MarcCheong

We also tried something similar https://forums.pega.com/t/absence-scheduling-for-operator-ids-from-landing-pages-in-end-user-portal-in-constellation-24-2/10236 in constellation 24.2.

Unfortunately, we faced the same issue. You can have a look at the above link shared which documents our approach and result. But with same configuration in 25.1 it works absolutely fine. We then later upgraded to 25.1 and did this implementation there

Note: You may also try the User Actions Tab on the Data-Admin-Operator-ID. Configure the right Default Data Sources and it should work, We are using this method currently in our 25.1 version.