Support Article
Self-looping FlowAction not saving on AssignmentService shape
SA-16900
Summary
A previous PRPC version a configuration's “Assignment Service” shape is the first shape after the “Start” shape and also a self-looping connector is added to the “Assignment Service”.

After having migrated to Pega 7.1.8, the same flow is generating a Java exception:

Error Messages
Java generation failed; see log for details
Steps to Reproduce
- Create a Flow on Pega 7.1.8
- Add “Start” shape
- Add “Assignment Service” shape
- Add self-looping “Connector” shape
- Save the rule, error generated
Root Cause
A defect in Pegasystems’ code or rules The log is providing the following details:
2015-11-03 15:29:53,092 [] [TABTHREAD5] [] ( internal.mgmt.Executable) ERROR - FirstUseAssemblerException
com.pega.pegarules.pub.generator.FirstUseAssemblerException: FUACache-FailAssembly [this:is:not:a:classname] produced no java source
From: (H51E571C5FBCB5AD8DF6D5FB0A2F9598B)
at com.pega.pegarules.generation.internal.cache.AssemblerFunctions.assembleRule(AssemblerFunctions.java:179)
at com.pega.pegarules.generation.internal.vtable.asm.VirtualTableAssemblyHandler$1.call(VirtualTableAssemblyHandler.java:464)
at com.pega.pegarules.generation.internal.vtable.asm.VirtualTableAssemblyHandler$1.call(VirtualTableAssemblyHandler.java:394)
This issue is coming from the code on Rule-Utility-Function called “pzGetDisplayableIncomingShapeIDs”
Resolution
Apply HFIX-24894
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.