Content
View differences
Updated by Tobias Dillmann 9 months ago
* The token should be considered when
* creating calculated values
* reading calculated values
* within the API
As opposed to the feature flag, were we limit the validity check to the _creation_ step, not having an enterprise token should instead also limit _using_ calculated values. This will create some edge cases where a user has already created calculated values with a valid enterprise token - but the token later expires. Using calculated values (reading, editing, etc.) should be restricted.
* creating calculated values
* reading calculated values
* within the API
As opposed to the feature flag, were we limit the validity check to the _creation_ step, not having an enterprise token should instead also limit _using_ calculated values. This will create some edge cases where a user has already created calculated values with a valid enterprise token - but the token later expires. Using calculated values (reading, editing, etc.) should be restricted.