You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem / use case? Please describe.
Have calculated attributes using JEXL, having as value the expression evaluation result.
Describe the solution you'd like
When an attribute type is Calculated the value returned when queriying (and also, when notifiying) should be the expression result.
What happens when using that attribute within a notification condition?
Probably, a new URL param should be included to request entities without rendering calculated values (to check if the expression works or not). Another alternative is to change the type.
The text was updated successfully, but these errors were encountered:
Probably, a new URL param should be included to request entities without rendering calculated values (to check if the expression works or not). Another alternative is to change the type.
Noted by @mrutid : Those attributes need to be manually provisioned one by one in each entity (since data provider is not going to create those attributes). No existing clases or patterns that apply to all the entities, like the case of subscriptions, that is a group provision.
Is your feature request related to a problem / use case? Please describe.
Have calculated attributes using JEXL, having as value the expression evaluation result.
Describe the solution you'd like
When an attribute type is
Calculated
the value returned when queriying (and also, when notifiying) should be the expression result.Provision
Describe alternatives you've considered
#4579
Describe why you need this feature
Additional information
The text was updated successfully, but these errors were encountered: