NPE while trying to add a step (flow) to a stage
I'm trying to add an existing flow to a step of one of my stages. When I click away (triggering a save) or click the save button I get an NPE error on the screen. I'm blocked from doing any development in this area because I can't add new flow or existing flows.
After tracing the issue I can see that the CaseTypeStages.pyStage().pyProcesses().pyFlowName is blank. This property is used on step 1 of pzSetStepTempProperties to call Obj-open. The obj-open fails because the flow name is blank. pyFlowName has a value for things that I configure previously (weeks/months ago) but for anything new it is missing.
Accepted Solution
Pegasystems Inc.
IN
Hello,
On review the corresponding SR, we see that this has been resolved by providing HFix-27367. Please create an SR with Request Type as Existing HotFix Request to obtain this HFix.
Thank you,
Pegasystems Inc.
US
This looks like a product issue. Can you please open an SR via My Support Portal to address this issue?
When you do, I would recommend attaching the same document you supplied here, as well as the saved tracer output that is referenced in your reproduction steps.
Pegasystems Inc.
IN
H John,
Please let us know the SR number once you raise it with Pega Support. That way we can track it and follow-up this discussion with the resolution.
Regards,
Lochan | Community Moderator | Pegasystems Inc.
Virtusa IT Consulting
AE
Is it happening on 7.2.2? If yes, I have faced the similar behaviour on 7.2.2 and raised a bug sometime back. Here is the reference id BUG-270217 which can help you in investigating this behaviour through the SR.
Pega
US
This is happening on 7.1.9. I raised SR-B16886 the same day that I started this thread but have not received a response expect for being asked to provide the tracer output which I did.
Pega
US
What was the outcome of BUG-270217? Did you get a hfix or work around?
So far I haven't found any details about this bug on the PDN and without access to Pega's internal PMF system I can't look it up.
Pegasystems Inc.
IN
Hi John,
You're right, the bug details can only be accessed by Pega employees. Since you have an SR open, please add this request on the SR. I will also add in a Pulse post on the SR so that the engineer can connect these 2 threads. In case you feel that this should be addressed with an increased priority, we suggest that you contact your Pega Account Executive.
Thanks,
Lochan | Community Moderator | Pegasystems Inc.
Accepted Solution
Pegasystems Inc.
IN
Hello,
On review the corresponding SR, we see that this has been resolved by providing HFix-27367. Please create an SR with Request Type as Existing HotFix Request to obtain this HFix.
Thank you,