LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Mandatory

    Employee
    Posted 03-18-2016 03:41

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Pedro Pablo

    I don't understand how mandatory works
    Documentation says "The Mandatory parameters determine whether or not a node should generate an error if it is on a bypass, and will be bypassed"
    but i do that and i don't get any error.
    Attachments:
    example.brg


  • 2.  RE: Mandatory

    Employee
    Posted 03-21-2016 05:37

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: lnason

    Hi Pablo - I've been using the software for a while and I've never had to use the "Mandatory" parameters for anything. Frankly, I don't understand what it does and would be interested to hear what any of my colleagues have to say on this

    Having said that, is there a specific "real world" use case that you are trying to handle here or are you just curious about the parameter itself? If there is a specific use case you have in mind, then we might be able to suggest another way to meet your requirements if you send along some more info.

    Luke


  • 3.  RE: Mandatory

    Employee
    Posted 03-21-2016 06:22

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: stonysmith

    Manditory 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.