Filter Data by Custom User Properties
in progress
T
Travis Gosselin
Today you can add additional filters via JSON to any table, chart, etc using some of the intrinsic functions like: "getUserTeams()". With the ability to customize the user data-model (like a profile), it would be beneficial to access other user data properties to filter on that we added custom. Perhaps a new function like: getUserProperty("myCustomProp") to use in rules:
{
"property": "github_user_id"
"operator": "=",
"value": "getUserProperty('my_github_user_id')",
}
Gur Shafriri
Merged in a post:
Support injection of JQ functions
E
Evan SketchE
Currently, JQ functions such as getUserEmail() or getUserTeams() are only supported at specific parts of the product.
By incorporating those directly to the Search API, it will allow further customization for different components of the system that use this API (for example actions conditions).
Gur Shafriri
in progress
Currently available in closed beta, contact us if you would like to test it out. See docs here
D
Dan DEVAUCOUP
Hi Gur Shafriri, does this beta feature be used in day-2 and delete entity selection condition ?
D
Daniel H. Huaman
This is very useful for enriching the execution conditions of a self-service. Not having this limits our ability to continue creating more self-services.
I've already tried:
.trigger.by.user.email, and
the getUserEmail() function
but it doesn't work. �
C
Calum Dee
Another possibility is if the
.user.
notation that works in actions and dynamic permissions when using team and user as blueprints was extended to be available in additional filters