Style Disconnected Activities Differently
Non planifiéeAn issue that I know a few other WF designers have bumped into (and I certainly have a few times) is believing that a given activity is connected to the flow when it is in fact not. Could we get the borders on elements without inputs to be dashed, or lighter, or have some other indicator that they are effectively commented out? Subworkflows and so on excepted of course.
"Why the heck isn't this running? How is it getting skipped?!" I ask myself. I'll check my inputs and assume caching issues etc etc while looking at a WF in Designer which appears kind of like this:

Maybe it's just me but the issue here flied completely under the radar. For those like me whose folks neglected to offer Where's Waldo in their developmental literature, here's the same image with a hint added:

I understand that I'm really asking for protection from myself here, but I've tripped over this a perhaps embarrassing number of times and the first couple of times I did it I took way too long to figure out my problem. If it's not asking too much, could we get activities lacking input connectors to display that fact in some way?
Vous devez vous connecter pour laisser un commentaire.
Commentaires
0 commentaire