b-venter / miwallboard Goto Github PK

Currently when an API call is made to the Miccsdk and a response of 401 is received, the SPA retries immediately - with the same result. This results in 100x more entries in the IIS log files, which equals massive log files and filling of HDD

Simple change. Add a footer similar to the navbar: i.e., placed in the root component and not in each of the components from router outlet. The link should simply direct to https://github.com/b-venter/miWallboard. Maybe use the GH icon but note the rules on copyright, etc.

The current styling is very flat. Adding tasteful shadows and transitions can improve the "feel" of the app

Provide a dialog view or side-draw when clicking on an agent. The dialog/side-draw must contain all (most) agent details.

Some users would like to view abandoned and answered values as percentage and not the actual whole number.
Therefore:

• add a boolean (true/false) to set whether percentage or whole number is displayed
• update options (ngIf) to display percentage or whole number based on boolean
• add boolean(s) to settings.json so that a default can be customised.

There is already one solution for this: set in ~/assets/settings.json.

However, in case of multiple queues and different people wanting different queues on default, let's add a "id" to the home url:

• by default, /home will load the the queue in settings.json
• /home/:id will load the queue identified by ":id"

Similar to #9, but for agent view only. I.e., ~/agent/:id.

Purpose is that there is a URL that can be used to directly view only the agent's performance details. This URL must be present (1) as a clickable icon with each agent and (2) in the detailed side-bar/dialog that appears when clicking on an agent on the home component.

For easy verification of the loaded app version, and also to provide confirmation that the page has loaded the latest update and not just from cache.

The tokens from MiCCB are long lived. So the current solution is manual: if nothing is getting refreshed, the user can "Clear" tokens and then "Connect" to get a new one.

Going forward, it would be better if the system will use the token refresh options provided by MiCCB

Create a "queue" component so that ~/queue/:id will take you directly to view only the queue details. Same info as shown on /home, but without the agent info.
Note that a Route Guard will need to be in place so that this only works if a valid token is present.