Starter Flow Issue
We made 2 flows ( Flow1, Flow2 ) with "Creates a new work object" checked. So pyCanCreateWorkObject is true.
Both the flows is being listed under Create Menu. By mistake or over sight it moved to prod. Now we saved Flow 2 in next ruleset version and unchecked "Creates a new work object" and made it unavailable too. But the datapage, D_StartingFlows, still pulls Flows under Menu. Deeper analysis shows that the process pulls all flows with pyCanCreateWorkObject true irrespective of the ruleset version. Which I see is not right. If the latest version of the flow is false, it should not be pulled by the datapage.
We are in Version 8.5.1. Is this a known bug?
Updated: 13 Jan 2022 5:41 EST
BNYMellon Technology
IN
@BhanuPrakash_G Thanks for Responding. Yes Did that too but it doesnt take that into consideration to list. But if we click the flow under create it will throw error. But Rule availability is not considered by the list function that pulls the list. Its done by the activity "pzGetStartingFlowsFromApp" in step 5 where it calls pega_processarchitect_pzprocessarchitect.pzGetStartingFlows(strClassName,false,strPageName);
The function takes class and pyCanCreateWorkObject as parameter. I feel its a bug.