Support Article
Parent-flow's parameter value doesn't get passed to sub-flow
SA-19984
Summary
User has a subflow with a parameter HarnessPurpose. In the main flow, user references the subflow and sets the value for the parameter as "Perform". When the subflow is accessed, an error is observed in the tracer "Failed to find instance XXX-Work-Test.Param.HarnessPurpose of type Rule-HTML-Harness".
This used to work in PRPC 6.1 SP2.
Error Messages
Failed to find instance XXX-Work-Test.Param.HarnessPurpose of type Rule-HTML-Harness
Steps to Reproduce
1. Create a sub-flow - flowA to create an assignment, and specify Param.HarnessPurpose as assignment's value of HarnessPurpose parameter.
2. Create a parent flow - flowB, which calls the flowA, and specify Perform as the value of HarnessPurpose parameter.
3. Use this flow to create a work object.
4. An error will comes out when try to perform the assignment of flowA.
Root Cause
In populateflowactions there was an enhancement which took the harnesspurpose which was added in the flow and was updating the same in the newassignpage. But if the harnesspurpose in the assignment is passed as a parameter(or dynamic), this would create an issue as the parameter page would be different. This was causing resetting of the pxFormName property in the newassignPage and was causing the issue. Checking if the parameter is dynamic or not before setting in the populateflowactions fua will fix this issue.
Resolution
Apply Hfix-20675.
Published February 26, 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.