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
A user would like to know anything that happened between/until/after certain dates.
A usage log entity can achieve this goal.
The usage log entity should persist:
account id
tenant
field id (refer to the plan field)
created at (date)
usage: number
additional info (string, optional)
The usage log should be set asynchronously on every increment action.
The usage property should be equal to the incementAmount given to the method (even if the field kind is boolean or string).
We should have an optional property to the increment method to support the additional info property, that will be stored in the usage log.
The user would like to add additional information about the increment action to add some context to the usage).
The text was updated successfully, but these errors were encountered:
A user would like to know anything that happened between/until/after certain dates.
A usage log entity can achieve this goal.
The usage log entity should persist:
The usage log should be set asynchronously on every increment action.
The usage property should be equal to the incementAmount given to the method (even if the field kind is boolean or string).
We should have an optional property to the increment method to support the additional info property, that will be stored in the usage log.
The user would like to add additional information about the increment action to add some context to the usage).
The text was updated successfully, but these errors were encountered: