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
Add YAML config key to indicate whether the Indicator query definition is supposed to return a single value or an array of values
The periodically running job to execute the indicator generating function should run between 15min - 24 hour intervals
The indicator generating functionality should be refactored to:
Execute indicator queries that would potentially return multiple values from multiple columns and store the data in a multidimensional array.
The multidimensional array would be serialized into a String which would be persisted in the database
To get the indicator counts the serializer introduced would convert the persisted Strings into multidimensional arrays for use when rendering indicator chartsjunit.framework.junit.framework.
When generating indicator tallies, for each indicator the newly newly generated counts should replace the existing record for that indicator as long as the record was saved within the same day (24 hours). Upon expiration of 24 hours, the new counts should be saved as new records.
Refactor the showing of indicator visualizations on the dashboard:
Introduce a table view to show counts in rows and columns
Refactor the existing visualizations i.e. the numeric count display and Pie chart to use the infrastructure described above
The text was updated successfully, but these errors were encountered:
Add YAML config key to indicate whether the Indicator query definition is supposed to return a single value or an array of values
The periodically running job to execute the indicator generating function should run between 15min - 24 hour intervals
The indicator generating functionality should be refactored to:
Execute indicator queries that would potentially return multiple values from multiple columns and store the data in a multidimensional array.
The multidimensional array would be serialized into a String which would be persisted in the database
To get the indicator counts the serializer introduced would convert the persisted Strings into multidimensional arrays for use when rendering indicator chartsjunit.framework.junit.framework.
When generating indicator tallies, for each indicator the newly newly generated counts should replace the existing record for that indicator as long as the record was saved within the same day (24 hours). Upon expiration of 24 hours, the new counts should be saved as new records.
Refactor the showing of indicator visualizations on the dashboard:
Introduce a table view to show counts in rows and columns
Refactor the existing visualizations i.e. the numeric count display and Pie chart to use the infrastructure described above
The text was updated successfully, but these errors were encountered: