We do have several screenflows having more than 15 shapes sometimes more than 30 or even reaching to 40-45 shapes.
One reason for keeping so many shapes is because we want to see them all in breadcrumbs when using embedded layout. If we break them up into subprocess we are going to loose the shapes in subprocess appear in breadcrumb. I know we can use TREE but we'r'e having several problems with that and not using htat.
also, nother importnant points was to understnad ....Is there any performance issues if we keep more than 15 shapes?
Please can you throw some light behind making this guardrail - is it just readibility issues or performance issue as well.
Yes, it is more of maintainability and readability concern. However could you explain what you meant by embedded layout for screen-flows here. Just want to understand the actual reason behind using more than 30 shapes within single screenflow.