Allow "optional incoming connections" to actually be optional for batch macros

[patrick_digan]

I decided to get real fancy when building a standard macro the other day. I checked the box on my macro input that made the connection optional:

It worked really well. My macro then became more complex, so I changed it to a batch macro. To my great surpise/astonishment/shock, the optional incoming connection is no longer optional:

The standard macro is working as expected on the left, but the batch macro is producing an error because my optional connection is requiring that something be connected to it.

I've been told that the code to make it optional is not there for batch macros and that this would be a product feature/improvement.

[GarryBrittain]

Fast forward 2 years, seems to be the same for an iterative macro.

This macro works just fine with all inputs hooked up, however errors when an input is made optional without an incoming connection. 

[David-Carnes]

"To my great surpise/astonishment/shock...."

My reaction was the same, nearly three years later.  Using Designer 2020.2, FWIW.

[KylieF]

Thank you for your feedback!

Our product team has reviewed this idea and based on the technical requirements and our current road map, we have determined that we're unable to include this feature into the product at this time. Should this or the road map change however, we will be sure to update this idea back to Under Review.

[MacFresno]

If you're not able to implement the feature... DO NOT PLACE THE CHECKBOX 😉

[bnjmnsmith]

Agreed. Running into the same problem.