This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Can you pass data/variables between alert conditions?

Let's say the Primary Section Alert Condition for the Alert trigger is what I initially care about in terms of identifying nodes I want to alert on.

Then let's say I enable complex conditions and in the Secondary Section I want to look at those identified nodes from the Primary Section, and maybe use them in a custom SWQL Alert... 

Can you pass data/variables between alert conditions?

Parents
  • Anyone know if this is possible to pass data/variables between conditions whether they be alert conditions or trigger conditions? That would be useful if you needed to formulate something and massage some data then use it in the next condition/step...

  • You can use a subquery in the custom SWQL bit to do what you describe, can be a bit fiddily to work with.

    Your use case sounds like you're trying to get alerting levels into the product, i think, I've not seen anyone do this without getting another tool involved. Seems possible, though will make your alert fairly hard to understand for a newbie, recommend adding a lot of comments.

    I think in practice you'd want to select from the layer you eventually care about (nodes here), then specifically right or left join a subquery to white/blacklist the stuff you do/dont care about

Reply
  • You can use a subquery in the custom SWQL bit to do what you describe, can be a bit fiddily to work with.

    Your use case sounds like you're trying to get alerting levels into the product, i think, I've not seen anyone do this without getting another tool involved. Seems possible, though will make your alert fairly hard to understand for a newbie, recommend adding a lot of comments.

    I think in practice you'd want to select from the layer you eventually care about (nodes here), then specifically right or left join a subquery to white/blacklist the stuff you do/dont care about

Children
No Data