Implement submission statistics & basic RBAC

[kyle1morel]

Description

• Create a new db function, public.get_activity_statistics()
• Adds a new tab on submissions page with a tabular data view
• Implements a basic RBAC to forbid front end navigation or api access if at least one role isn't present

Types of changes

New feature (non-breaking change which adds functionality) -->

Checklist

• I have read the CONTRIBUTING doc
• I have checked that unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

[codeclimate]

Code Climate has analyzed commit 977712a and detected 1 issue on this pull request.

Here's the issue category breakdown:

Category	Count
Bug Risk	1

View more on Code Climate.

[github-actions]

Coverage Report (Application)

Totals
Statements:	43.57% ( 61 / 140 )
Methods:	26.32% ( 5 / 19 )
Lines:	60.76% ( 48 / 79 )
Branches:	19.05% ( 8 / 42 )

[github-actions]

Coverage Report (Frontend)

Totals
Statements:	37.02% ( 214 / 578 )
Methods:	34.82% ( 39 / 112 )
Lines:	42.99% ( 138 / 321 )
Branches:	25.52% ( 37 / 145 )

[tpantella]

This is great! The table is a little wide - suggest we shrink the last two columns as wide as the column titles, first column as wide as the longest value, and squish/center it - this will buy us some blank spaces on the left and right ends outside the table to ultimately make it more readable.

if you're making it responsive we could do the above, then resizing the browser width could first keep the table the same width while reducing the blank side space, then once the table is as wide as a more narrow browser, go into the standard approach for shrinking as done elsewhere.

The last comment is numbers in tables are typically right-aligned, that might look weird until we shrink down the table but I would suggest doing that as well. Also since I couldn't test with a sample navigator, I am making the assumption that the navigator filter works.

If any of this is unclear please contact me! Just

[Subin1Doo]

Hi Kyle! I think the stats page look great! It's simple and straightforward 👍
I went through it and found some things that could be updated on top of what Tyler mentioned.

First, the drop down calendar box isn't aligned with the text (submission by range/ month/ submissions by assigned navigator). But, I realized it gets aligned only when you select something from the drop down. I can see the boxes shifting position as I select a date. It'd be great if you could fix the position, so that it's aligned from the beginning and doesn't move.

Another minor thing, it would be great if we could put some contrast between the statistics heading/ title vs. the actual state. Example: [Submissions by intake state (as it is) : Assigned (in bold letters)] or the other way around. This will increase the readability for the users and help them visually capture the necessary info faster :)

This is my first review comment, so please let me know if you need clarification on what I'm saying. Thank you!

[TimCsaky]

managed to understand it.. interesting approach

[TimCsaky]

i wonder if you need this valid check.
maybe userId will either be empty or a uuid.. both work in the query.(?)

[kyle1morel]

userId is a uuid once a user has been selected from the drop down. Up until that point it is filled with whatever the user is typing into the box. Kind of annoying how it works.

[wilwong89]

Intake status and application status need to be title case and not upper case.