CSFS - 7.22.1 ---- > Error when trying to save as pycaseactionarea
Team took a backup Pega RAP taken from Pega 7.2.2 and CSFS 7.21. Then this product was installed in a newly setup environment with Pega 7.2.2 and CSFS 7.22.1 version of the framework. In the new environment when opening the created intent tasks, the pycaseactionarea section could not be resolved and ended up giving null pointer exception whereas OOTB intent tasks were opening properly. Team observed that the class of “pyCaseActionArea” which is launching for OOTB intent tasks is different from the “pyCaseActionArea” launching for their intent tasks. Team tried to open the “pyCaseActionArea” which is getting launched for OOTB intents (PegaFS-SCM-Work. pyCaseActionArea), but were not able to open the section itself - resulting in some exception like "There has been an issue, please consult with system administrator". As team reverted the version instantly, not able to share logs/tracer lines at this point until latest version is imported again.
In CSFS 7.21 version of the framework, no such issues are observed. Meanwhile wanted to check if anybody has faced similar issues with CSFS upgrade to 7.22.1.
ING, Netherlands
NL
Hi All,
Is someone having any update on this post?
Also , can you confirm if Pega Customer Service for Financial Services(version 7.22.1) is Compatible with Pega 7.3.
Regards,
Arpita
Accenture
IN
As per the Install Guide it states - "Install Pega 7 Platform 7.2.2 or higher". By which I suppose it means that CSFS 7.22.1 would be compatible with Pega7.3.
Pegasystems Inc.
IN
Possibly the reason of this issue is, there would be multiple copies of pyCaseActionArea rule in same ruleset version 07-22-01. As shown below:
pyCaseActionArea --- 7-22-01 – circumstanced(prop==”val1”) --- Available
pyCaseActionArea --- 7-22-01 --- circumstanced(prop==”val1”))--- Withdrawn
It is happening during upgrade and skimming.
For 7.22.1 ,we will release the hotfix .
ING, Netherlands
NL
Hello tyagn,
Thank you for your reply, we will check that once, could you also confirm that whether this issue persists in 7.22 version(one version lower to CSFS 7.22.1) of the framework as well, and if yes is there already any hotfix in place for CSFS 7.22?
Regards,
Arpita