This question might be answered by Product Support.  Here you can research your issue and perhaps find a solution.  If there is no solution there links to additional help available on the right hand panel.

Hope this helps,

Sean

Pega Academy Support Team

Yes, our work objects - we call them 'cases' - have internal flows on them.  The job of pzInternalCaseFlow is to provide a context for case-wide flow actions, even when no other flow is present on the case.  I'll do some research on how you could be getting this error and get back to you.

Deepesh, when you see "By performing this assignment, you are disabling stage SLA and stage/case-wide local actions for the current stage of your work object.", you are viewing the flow action for the internal assignment itself.  This is consistent with the fact that you stated " while opening WO,  assignment key passed as ASSIGN-INTERNAL <WO pzinskey>!PZINTERNALCASEFLOW".  So, we need to figure out how you are getting that assignment handle.  Can you please go into more detail about how you open the case?

Nadeem, I don't understand what you wrote.  What does "one of the children cases in pzInternalCaseFlow" mean?  What is showing in System Lock details?  Can you be more clear?

Thanks Deepesh for your time ..

FYI, as a resolution for this issue,  Added a new condition to skip this default flow by checking at pxAssignClass=="Assign-Internal".