RE: Undeclared Local Variable

andrewm231 — Wed, 09 Oct 2024 09:37:46 GMT

Thank you Mike, yes, that was the issue, it was being declared in the parent rule so when the child rule was being called, it was still within scope, though that wasn't obvious at the time. It does make sense though. But the switching from "load" to "a!localVariables" is still confusing, but not within the scope of the change I'm attempting to make.

RE: Undeclared Local Variable

Mike Schmitt — Mon, 07 Oct 2024 15:56:28 GMT

Sub-rules and interfaces inherit variables declared in the parent, presuming the variable is in scope. This used to be more standard (sadly) before practices were solidified to "require" local variables be passed via rule inputs to child items. I'm guessing that the parent of your example declares "local!TriggerQuestion" validly. I'm unsure why switching it to a!localVariables() causes the behavior to change, other than that perhaps it's more sensitive to alerting us about this sort of sloppy coding.