Orphaned widgets in BPMs

Other than being “sloppy”, is there any down side to having orphaned widgets in a BPM workflow? And by “orphaned” I mean not connected to any other widgets.

Like If 'm doing development and put a couple of Show Message widgets in for debugging.


But then when I go to roll it out I just remover the path arrows, but leave the widgets.


Are unreachable widgets just ignored?

And yes… the better thing to do would be to put condition blocks in to determine when to shows those (user= , date <= , etc …) But I’m often just probing for info, but don’t want to rebuild a Show Msg widget (with possibly a half dozen field queries in it) ever time

if you do a “verify” on the BPM, you will get a warning message… that said, I have not found any negative effects for doing what you have done. In fact, while developing changes, I often will copy a set of widgets and paste them, and then modify the “active” widgets.
ALSO I now almost always create one additional disconnected C# Widget with a comment block that holds change history.

1 Like