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.  Runtime selection of path

    Employee
    Posted 04-25-2014 08:08

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

    Originally posted by: feanor0

    Hi

    I'd like to be able to control which part of a graph runs given some runtime condition. For example, let's say I have a split-node with outputs True and False, and True goes to do some computation (X), and False goes to do some computation (Y). The results of X and Y are concatenated at Z.

    Computation Y is complicated enough that even if the number of records at False is zero, it takes a long while to run through. So I'd like to somehow be able to disable computation Y and pipe the 0-record output from False directly to the concatenation at Z. If not, the concatenation at Z will not complete because it will be waiting for all its inputs to be satisfied.

    I thought I could use a Meta Check node and set minimum records to 1. This works to disable computation Y when there are no outputs at False. But I can't figure out how to still connect up to the concatenation at Z.

    Please see attached graph.

    Furthermore, in general, I'd like the runtime condition to be some expression rather than just a record count. Is this doable?

    Thanks,
    Attachments:
    runtime path select.brg


  • 2.  RE: Runtime selection of path

    Employee
    Posted 05-12-2014 11:45

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

    Originally posted by: ejones

    You've tried first few options I would suggest. At this point, it seems that using the "Execute BRX" node would be the best option. One example of setting up an "Execute BRX" node is in an answer in this post, http://community.lavastorm.com/threa...=5918#post5918


  • 3.  RE: Runtime selection of path

    Employee
    Posted 01-06-2015 08:55

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

    Originally posted by: gmullin

    @feanor0 Did you ever get a solution to this? I'm having this exact problem right now.


  • 4.  RE: Runtime selection of path

    Employee
    Posted 07-23-2015 08:32

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

    Originally posted by: bpurcell

    Can't access that thread for some reason Ernest and am having the same issue ... any update ?


  • 5.  RE: Runtime selection of path

    Employee
    Posted 07-24-2015 06:45

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

    Originally posted by: lnason

    Hi Berny - I've attached the graph that was posted in the other thread. The requirements for the work being done in the other thread are a little different than what is described here though, so you might need to extrapolate a little from what was done.

    SaleForceBatch.zip

    For the graph posted at the beginning of this thread, I think you'd want to connect each output of the split node to an Execute BRX node, where one invokes a BRX that performs calculation X and the other performs calculation Y. You could then clock these Execute BRX nodes to a BRD Input node(s) that would read the output created by BRXs that were executed.

    Depending on the details of the problem you are trying to solve, another option might be the "Path Enabler" node (it's an Experimental node in the "Logistics" group). You can get an idea of how this node works by looking at the following:

    http://community.lavastorm.com/threa...ning-Session-2

    There are also some Execute BRX examples here.

    Luke


  • 6.  RE: Runtime selection of path

    Employee
    Posted 07-24-2015 08:31

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

    Originally posted by: bpurcell

    Thanks Luke