Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: stonysmithManditory comes into play when you are producing a BRX or LXA for running a graph automatically.
One use case is if you are using a Bypass node, it's possible at times that you might have both sides of the bypass disabled, such that the downstream nodes would never produce any output.
By setting Manditory on a node, you will receive a notification (error message) while producing the BRX/LXA that the node can never be executed because it will never have any input data.
===
I also use the Manditory flag in the opposite manner: I have a graph or two that have diagnostic nodes that I would "never" want to run the in a nightly process, but I also don't want to remove them from the graph. By placing a filter in the composite with the diagnostic nodes, and by not connecting it's input to any data stream, the Manditory flag on that node allows me to remind myself not to publish the graph with the diagnostic nodes enabled. Disabling the entire composite disables the manditory filter, and thereby allows the graph to be published without the diagnostic nodes active.