Unable to Capture Updated Operator Unavailability Data in Constellation Portal

Hi Team,

We have implemented a new navigation option (My Profile) in the Pega Constellation portal. On clicking this option, it successfully loads the details of the currently logged-in user.

From the available actions (three-dot menu), when selecting Edit, we attempt to update the operator’s unavailability details. However, after entering the required information and clicking Submit, the updated values are not being captured in the request, and we are unable to see them reflected.

Could you please let us know if any additional configuration or setup is required to ensure that the updated unavailability details are properly submitted and captured?

Thanks in advance for your help.

Pega Version we are using: 24.1.1

OperatorAvailability_Constellation.docx (734.6 KB)

If you look at the network tab, the data is sent in the object content with the values selected, trace the request and verify.

@Yaswanth_G, I see you’ve followed the approach on this Constellation 101. Though I can’t verify all from your document, looks pretty much the same.

From memory, when @Maciej_Dybal was putting this together, I remember prior to 25 this was not possible. Let me follow up with some of the people who experimented with 24 and see if there are some additional steps needed to get this working.

Hi @MarcCheong, yes , I followed the same approach from Constellation 101. Kindly let me know if there is any update on additional steps for 24 version. thank you.

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.

1 Like