-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement user activity properties / events #949
Comments
* Implemented ORDER action and event * 'ORDER FROM' and 'ON ORDER TO' properties * FILTER action and event * Short 'compare' JSON values * READ ORDER/FILTER actions * READ ORDER -> ORDERS; READ FILTER -> FILTERS * user activity info storage type fix * Added 'orders', 'filters' forms * Removing auto-added leading and trailing "%" for "contains" filters * ClientFilterAction: keep filter controls visibility state; single remote apply call * compile fix * api version 257 --------- Co-authored-by: pavel-miniutka <[email protected]>
2 types of activities are implemented for the moment: ORDER and FILTER Examples of actions:
For access to default properties module UserEvents should be added into required modules list. Form events block:
JSON structure: For ORDER:
For FILTER:
"desc", "compare", "negation", "value" and "or" are optional keys Also forms for quick import and modification of user activity info were added:
|
For now, there should 3 types of such activities:
FILTER - changing filter
ORDER - changing order
FOCUS - changing focus
All this activities should be scoped to group objects for now (later it maybe also possible to scope such action / events to properties).
So syntax should be:
Event block:
ON [FILTER | ORDER | FOCUS] go [TO propertyNoParams]
Action:
[FILTER | ORDER | FOCUS] go [FROM propertyNoParams]
Property should store JSON (or CSV) string which should contain the data about the filter / order / focus.
For example (for order):
propA;true
propB;false
PS: Property action / event syntax could be the same, but property should contain more "granular data" (for example, for order, REPLACE, ADD, REMOVE, DIRECTION)/
The text was updated successfully, but these errors were encountered: