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
Now that a report ooi renews itself on the recipe's recurrence instead of creating separate new report ooi's per run, the report history only shows the most recent version of every report. There is now a technical problem making it difficult to show all versions of all reports chronologically in this overview. I think we need to discuss the technical solution for this use case in order to look if it still fits the design of the history tab or that a redesign is needed.
Context on the technical problem:
Asking the database for all reports is possibly being a very large call. Ooi versions unfortunately is not a variable that we can ask look up in the database as far as I understand.
A possible solution was suggested where we look at the recurrence of the recipe and count back to conclude for how far back in time we need to ask the database for the report versions. This is not optimal because if someone changes the recurrence from 'every hour' to 'every year' and asks for previous versions of a report it can still break.
The text was updated successfully, but these errors were encountered:
Now that a report ooi renews itself on the recipe's recurrence instead of creating separate new report ooi's per run, the report history only shows the most recent version of every report. There is now a technical problem making it difficult to show all versions of all reports chronologically in this overview. I think we need to discuss the technical solution for this use case in order to look if it still fits the design of the history tab or that a redesign is needed.
Context on the technical problem:
The text was updated successfully, but these errors were encountered: