Tracer does not show flow shapes executed within a subprocess
While tracing the flow execution, it does show the flow shapes that are executed like Utility, Connector, Sub-Process etc. But when a sub-process is executed Tracer does not show flow shapes that are being executed within this sub-process. Is this a known limitation?
I am using Pega 7.1.7
Another usability issue observed is flow shapes are shown with IDs like Utility8, SubProcess11 (I think these values are from pyMOId). Instead if short description (pyMOName) of these shapes are shown it will be easy to identify the exact shape being executed in the flow.
I have selected Flow option in Tracer settings. Let me know if I need to select any other settings in Tracer to get details of shapes being executed in sub-process.
As sub-process is again a flow rule, I am expecting Tracer to show shapes being executed within sub-process as well once Flow is selected in Tracer settings. Is there any other work-around to trace sub-processes?
I find it hard to believe that the tracer won't show the flow events in the subflow. I did a bit of experimentation and it seems to show in mine.
Please check the following:
1) Turn OFF draft mode and make sure your flow saves without error. To prove it is saving, after draft mode is off, make a visible CHANGE, and click SAVE, and then click "actions - > refresh" (I'm referring to making changes directly in the flow ruleform here, not a proxy flow change via case type rule) and make sure the change sticks.
2) Do number 1 for both the parent and subflow.
3) Make sure ALL rulesets are turned on in your tracer, particularly the ones your parent and subflow are in.
4) If you're still not seeing your subflow shapes showing up in tracer but you are seeing your parent flow shapes, put a utility flow in your subflow that calls an activity, and try "actions - > trace" on the activity ruleform to trace ONLY the activity. NOTE: For that experiment, make sure you turn on activity and activity step tracer events (you may have had only flow events on for previous numbered steps here) ! Make sure you see your activity being performed. If not, then it may be that your subflow isn't even being called and that's why you don't see it in the tracer.