...
Behavior Rules are very flexible in structure to cover most use cases that you will come across. Behavior Rules are clustered in Groups. Behavior Rules are executed sequential within each Group. As soon as one Behavior Rule succeeds, all remaining Behavior Rules in this Group will be skipped.
Anchor | ||||
---|---|---|---|---|
|
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
{ "behaviorGroups": [ { "name": "GroupName", "behaviorRules": [ { "name": "RuleName", "actions": [ "action-to-be-triggered" ], "children": [ <CONDITIONS> ] }, { "name": "DifferentRule", "actions": [ "another-action-to-be-triggered" ], "children": [ <CONDITIONS> ] }, <MORE_RULES> ] } ] } |
...
Code Block | ||||
---|---|---|---|---|
| ||||
... "children": [ { "type": "negation", "children": [ <any other conditions> ] } ] ... |
Occurrence
todo
Dependency
todo
ResultSize
...
The API endpoints :
HTTP Method | API Endpoint | Request Body | Response |
---|---|---|---|
DELETE | /behaviorstore/behaviorsets/{id} | N/A | N/A |
GET | /behaviorstore/behaviorsets/{id} | N/A | |
PUT | /behaviorstore/behaviorsets/{id} | BehaviouRule model | N/A |
GET | /behaviorstore/behaviorsets/descriptors | N/A | |
POST | /behaviorstore/behaviorsets | N/A | |
GET | /behaviorstore/behaviorsets/{id}/currentversion | N/A | |
POST | /behaviorstore/behaviorsets/{id}/currentversion | N/A |