Question
BA Continuum India Private Ltd
IN
Last activity: 30 Jul 2018 0:54 EDT
Function Not found if restricted to lower version
Team,
There is a function 'ispagelocked' saved as into our application library from PEGA library for development purpose in version say 01-20-01 and it is then been withdrawn in higher version say 01-20-08.
When we restrict the application to version 01-16-99, rule not found exception is happening as it is trying to search for this function in our application library, which doesn't have this rule in that version. Please suggest to resolve this issue.
Thanks,
G.Manikandan
Pegasystems Inc.
IT
Can you post the stack trace of the exception showing this problem?
We should determine what rule (in which version) is calling the function and how it is trying to resolve the function.
BA Continuum India Private Ltd
IN
Runtime error occurs in PEGA OOTB activity "Work-.JumpToTask", when it tries to invoke this function in a when condition. Stack trace is attached.
Pegasystems Inc.
IT
Thanks for providing the stacktrace. Can you please use the "Reassemble Candidates" option in the Virtual Table Cache Management facility in SMA (SMA > Advanced > Virtual Rule Table Cache Management) to invalidate the Caller and verify whether this addresses the issue?
Please enter "Rule-Obj-Activity" for pxObjClass field and "!JUMPTOTASK" for the pxInsId field then click on the "Lookup Virtual Table Cache Details" button.
You should get a list of entries (mine is reported below). Then click on ""Reassemble Candidates" button.
pzInsKey Object Class Name Availability Instance Class Names RuleSet Name
RULE-OBJ-ACTIVITY @BASECLASS JUMPTOTASK #20130919T002146.258 GMT @baseclass Final Rule-Obj-Activity Pega-ProCom
RULE-OBJ-ACTIVITY WORK- JUMPTOTASK #20130919T002525.627 GMT Work- Final Rule-Obj-Activity Pega-ProCom
RULE-OBJ-ACTIVITY WORK- JUMPTOTASK #20160930T122121.887 GMT Work- Final Rule-Obj-Activity Pega-ProcessEngine
Please apply the steps above and kindly let me know about the outcome.
Pegasystems Inc.
IT
Hi Ganapathy,
In order to proceed in investigating the issue we need to reproduce the issue in-house.
To do so more details are required.
Considering that such data could contains sensitive information I would suggest you to raise a support request on My Support Portal (https://collaborate.pega.com/question/how-raise-sr-my-support-portal-how-question) providing the following elements:
A clear description of the issue (Context, Application Ruleset versions, ...)
Environment Details (Operating System, Application Server, JVM ans DB details)
Logs for the failing node.
Note: Please mention this Community Question while raising the request.
Thank you,
Domenico
Pegasystems Inc.
IN
Hi @ManikandanG,
Please let us know the SR# back here once created so that we may continue to track it and update this post for the resolution.
Thanks!