-
Problem report
-
Resolution: Fixed
-
Major
-
4.0.3
-
None
-
Team B
-
Sprint 49 (Feb 2019), Sprint 50 (Mar 2019), Sprint 51 (Apr 2019)
-
1
Steps to reproduce:
Create simple action with API with trigger conditions for discovery event source.
{
"jsonrpc": "2.0",
"method": "action.create",
"params": {
"name": "Test",
"eventsource": 1,
"status": 0,
"esc_period": "2m",
"def_shortdata": "Test",
"def_longdata": "Test long",
"filter": {
"evaltype": 0,
"conditions": [{
"conditiontype": 3,
"operator": 0,
"value": "test"
}]
},
"operations": [{
"operationtype": 0,
"esc_period": 0,
"esc_step_from": 1,
"esc_step_to": 2,
"evaltype": 0,
"opmessage_grp": [{
"usrgrpid": "7"
}],
"opmessage": {
"default_msg": 1,
"mediatypeid": "1"
}
}]
},
"auth": "038e1d7b1735c6a5436ee9eae095879e",
"id": 1
}
Result:
See screenshot we have action in discovery source with trigger name conditions. Which is useless at all.
If we check action list for Discovery at first glance it looks great for trigger event source, which might confuse users
When we open action we don't see the conditions at all.
Expected:
Probably should be an error that this not supported condition for this type of event source and action shouldn't be created.
- part of
-
-
- Reopened
-
