Hi All,
This is regarding Operator Absence scheduling configuration in constellation. I would like to create this feature in the landing page and any changes done there should update in the operator ID’s schedule absences section under the work tab of the operator.
We are using a list data page in the landing page to list down all operators and on selection of “Edit” , a modal opens up with the “Edit View” that is configured on the Data-Admin-Operator-ID Data class’ UX views.
But every time we are trying to click edit and update something, we are getting errors as though it is trying to create a new operator instead of just updating the selected operator.
I have attached the videos and images showing the entire configurations for reference.
It is still possible with an OOTB Constellation UI (Landing Pages and Saveable Datapage)
I have personally done this with a new Data Object, storing the data and then in the SSO rules we append this data (e.g. Skills).
Your scenario, where you use the OOTB data object Data-Admin-Operator-ID might need a little more configuration than you have. We will need to make sure we cover that.
@Aditi Mehta has kindly offered to help you, which will help feed into our 101 article on the topic - we will share as soon as its ready!
I have a similar requirement, to schedule out of office for users from the landing page. were you able to achieve this, if so, can you please give the steps you followed to achieve it.
We upgraded to Pega 25.x infinity and we were able to get it working via OOTB ways itself using the pyEdit and Action configured in the Actions tab of the Data-Admin-Operator-ID.
Not sure, if a fix has been provided for the same in 24.2.x..
Simply create a list data view on a landing page sourced from a list data page from Data-Admin-Operator-ID Class. Configure pyEdit view for the Data Type and add the necessary fields there. Make sure the default data soruces ( lookup, editable, savable)-----> All 3 are available for the datatype. Then it should work.
Alternatively, you can also choose the “Actions” tab under the Data Type and configure your own view, custom flow action, custom pre-processing and post-processing rules if you need some more customisation/updation to happen.