This content has been marked as final. Show 2 replies
Hi Leandro, as I told you earlier, the only way I can think of is the SQL based rule.
It appears to be fully supported, though not necessarily encouraged.
Right now we'll try to use a workaround that doesn't go through low level customization.
The point is that we can do this because our rule is associated to a Jeopardy event. Basically, we'll let the Jeopardy be always triggered and leave the complexity of checking the extensible attributes to the jeopardy's automation.
Unfortunately, this solution only works for rules associated to events triggering any automation. In other cases, your solution should be considered, even if it's not configurable from the design studio.