Question
Anamata
NL
Last activity: 22 Mar 2023 6:07 EDT
Creating Operator class WorkParty using API fails
In previous versions of Pega i was able to add an "Owner" WorkParty (class "Data-Party-Operator") by doing a PageInstructions "instruction": "ADD" API call. In order to create this workparty in the correct class, I had to include the "pxObjClass" in the content.
In newer releases of Pega I'm not allowed to include the pxObjClass anymore. If I do so Pega will respond with an HTTP 500 error. (Exception: com.pega.pegarules.pub.clipboard.UnmodifiablePropertyException: The page or property MyServicePage.updateCaseRequest.pageInstructions(1).content.pxObjClass is unmodifiable.). However, if I try and create that workparty without the pxObjClass it creates a workparty in the "Data-Party" class.
Does anyone have an idea how to fix this?
Updated: 22 Mar 2023 6:07 EDT
Pegasystems Inc.
GB
@Michel Kraaij did you manage to resolve this issue?
From past support tickets there were a number of workarounds - If the "Update Page" directive is used to set the focus on a page, then an error can results if the very first thing that is done after the Update Page is to modify the pxObjClass.
Users were asked to perform the following local-changes: there are two reasonable local changes possible:
You can change the class before the Update Page directive. You can first set the pxObjClass via a direct reference and only then update the page:
The alternative is to keep the "Update Page" as the first directive, but then, as the first "Set", modify some other non-special property on the page before changing the pxObjClass.
Check that before trying to set pxObjClass for a special java page check for its presence both as a special java property and as a normal property
The error "pxObjClass is unmodifiable" comes when you try to update the existing value of "pxObjClass" on a page since when you change the class the rest of the properties on the page may not be valid anymore.
The workaround for this is to clear the page and then set the values. If you are just moving down the hierarchy of a class and want to maintain the rest of the values, you can create a page of the sub class and then do a page copy.
@Michel Kraaij did you manage to resolve this issue?
From past support tickets there were a number of workarounds - If the "Update Page" directive is used to set the focus on a page, then an error can results if the very first thing that is done after the Update Page is to modify the pxObjClass.
Users were asked to perform the following local-changes: there are two reasonable local changes possible:
You can change the class before the Update Page directive. You can first set the pxObjClass via a direct reference and only then update the page:
The alternative is to keep the "Update Page" as the first directive, but then, as the first "Set", modify some other non-special property on the page before changing the pxObjClass.
Check that before trying to set pxObjClass for a special java page check for its presence both as a special java property and as a normal property
The error "pxObjClass is unmodifiable" comes when you try to update the existing value of "pxObjClass" on a page since when you change the class the rest of the properties on the page may not be valid anymore.
The workaround for this is to clear the page and then set the values. If you are just moving down the hierarchy of a class and want to maintain the rest of the values, you can create a page of the sub class and then do a page copy.
I wasn't able to find any change in the product between versions so am unable to provide any further input on this.