Using rule!UNI_TEST_UTIL_debugBox()

is there a way to use rule!UNI_TEST_UTIL_debugBox() in an Expression Rule?

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    No, debug box won't work.  What you can do, however, is use curly braces.

    Your standard expression rule might be:

    load([or a!localVariables( ]

    local!var_1,

    local!var_2,

    ...

    local!var_n,

    expression: //code goes here

    )

    You can also do:

    load(

    local!var_1,

    ...

    local!var_n,

    {

    expression1: //code goes here ,

    expression2: //more code goes here ,

    expression3: //even more code goes here

    }

    )

    You can do all sorts of things with this, including printing out all your local variables.  Your expressions could be:

    {

    concat("This is local ! var 1: ", local!var_1),

    concat("This is local ! var 2: ", local!var_2),

    concat("This is local ! var 3: ", local!var_3)

    }

    Comment out your code, or ask for a list of all local variables before output of the existing code.  Only run some of it.  Demand the first half and after that quite separately the second half.  Ask for all local variables first, then your code, then all the local variables again.  You can do anything provided you're not on the Prod environment.

    I've been where you are.  I so rarely trust the machine for anything.  I demand that it tells me what on Earth it's thinking frequently.

Reply
  • 0
    Certified Lead Developer

    No, debug box won't work.  What you can do, however, is use curly braces.

    Your standard expression rule might be:

    load([or a!localVariables( ]

    local!var_1,

    local!var_2,

    ...

    local!var_n,

    expression: //code goes here

    )

    You can also do:

    load(

    local!var_1,

    ...

    local!var_n,

    {

    expression1: //code goes here ,

    expression2: //more code goes here ,

    expression3: //even more code goes here

    }

    )

    You can do all sorts of things with this, including printing out all your local variables.  Your expressions could be:

    {

    concat("This is local ! var 1: ", local!var_1),

    concat("This is local ! var 2: ", local!var_2),

    concat("This is local ! var 3: ", local!var_3)

    }

    Comment out your code, or ask for a list of all local variables before output of the existing code.  Only run some of it.  Demand the first half and after that quite separately the second half.  Ask for all local variables first, then your code, then all the local variables again.  You can do anything provided you're not on the Prod environment.

    I've been where you are.  I so rarely trust the machine for anything.  I demand that it tells me what on Earth it's thinking frequently.

Children