Question

I am facing same issue as support artical after upgrade application to PegaPRPC 6.x to 7.1.9 "https://pdn.pega.com/support-articles/pzinternalcaseflow-error#comment-139441"

I am facing same issue as support artical after upgrade application to PegaPRPC 6.x to 7.1.9 https://pdn.pega.com/support-articles/pzinternalcaseflow-error#comment-139441

SUMMARY
After upgrade to Pega 7.1.7, pzInternalCaseFlow errors occur in many of the work objects.
ERROR MESSAGES
Unable to open instance using the given input : Assign - Internal - Work Class- Work Object # - PZINTERNALCASEFLOW

STEPS TO REPRODUCE 

  1. Create an activity that loops through pxFlow page.
  2. Do obj-open-by-handle on every assignment found in the loop.
  3. Call this activity from the post action of a flow action.

ROOT CAUSEThe pzInternalCaseFlow is a system flow which is created and used for stage based processing. The internal case flow is a virtual assignment, it has a pxFlow page, but the assignment is not actually written out to the database. Therefor, you are unable to successfully perform obj-open-by-handle.RESOLUTIONFor these types of system flows, set pxSystemFlow to true. The best practice is to avoid trying to open or manipulate assignments where pxSystemFlow is set to true.

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

Pega
April 12, 2016 - 4:31am

Hi

The support article you highlighted talks about a solution. Have you tried that at your end ? What is the outcome ?

April 12, 2016 - 10:10am
Response to Santanu

I tried same solution...it's not working

April 12, 2016 - 1:16pm
Response to Samirkumar

Hi Samir,

The support article you referenced is for a case where an activity was being used to loop through the pxFlow pages.  What is the scenario in your environment?

If you are seeing the internal assignment appear in the list of processes, then you will want to check if you have a custom version of the Work-. Flows section.  The OOTB section has code to exclude system flows.

Regards,

April 12, 2016 - 4:47pm
Response to CarissaW_GCS

Hi Carissa,

Same scenario as article. activity is looping pxFlow pages and validating if pxAssinmentKey is present then set as param. and same param value pass to Obj-Open-By-handle. same page i validated in clipboard pxsystemflow value is true. Still its failing while opening.

Regards,

Samir Gohel

<Removed Contact Information>

April 12, 2016 - 1:41pm
Response to Santanu

Hi Santanu,

Same scenario as article. activity is looping pxFlow pages and validating if pxAssinmentKey is present then set as param. and same param value pass to Obj-Open-By-handle. same page i validated in clipboard pxsystemflow value is true. Still its failing while opening.

Regards,

Samir Gohel

<Removed Contact Information>

Pega
April 12, 2016 - 2:59pm
Response to Samirkumar

Hi Samir, Good morning!

could we learn the activity name? from where it triggering? screenshots?

Thank you!

psahukaru

April 12, 2016 - 5:09pm
Response to sahup1

Hi Phani,

Please find screen shot. we can talk also if you are fine. 1) Activity UpdateExistingWO WithEmailDetails -2) Update assignmentstatus. Step 1.1 methos Obj-Open-By-Handle is failing. It is working fine in Pega PRPC 6.x. Issue with Pega PRPC.7.1.9

Issue1.png

Issue2.pngIssue3.png

Thanks,

Samir Gohel

<Removed Contact Information>

April 13, 2016 - 1:26pm
Response to Samirkumar

Hi Samir,

You should add a precondition so you only open assignments where pxSystemFlow is false.

Carissa

April 13, 2016 - 2:03pm
Response to CarissaW_GCS

Hi Carissa,

Thanks for reply.

Please clear below query.

1) In this condition pxSystemFlow value should be false/True?

2) Currently I am seeing pxSystemFlow value is true in clipboard?

Samir Gohel

April 13, 2016 - 2:42pm
Response to Samirkumar

Hi Samir,

The pxSystemFlow value will be true in this instance.  My suggestion is that you do not open and modify those assignment instances.  So if pxSystemFlow is true, skip the open step.

Carissa

April 13, 2016 - 3:37pm
Response to CarissaW_GCS

Thank you Carissa,

Do we have any other work around to update that assignment status(pyAssignmentStatus)?

Regards

Samir Gohel

April 14, 2016 - 8:26am
Response to Samirkumar

Hi Samir,

I am not aware of any other workarounds.  It is a internal assignment that would not be assigned to a user.  Is there a particular reason why you need to update these virtual assignments?

Carissa