Dashboard framework

From UG

Revision as of 21:20, 16 September 2011 (edit) Alex (Talk | contribs) (→Settings) ← Older edit		Current revision as of 22:39, 25 March 2012 (edit) (undo) Andrei (Talk | contribs) (→Solution)
(24 intermediate revisions not shown)
Line 1:		Line 1:
-		+	[[Category:DRs and KPIs]]
-	[[Category:OpsCore]]	+
	== Info ==		== Info ==
Line 60:		Line 59:
	[[File:Db config non jag user User side 2.JPG]]		[[File:Db config non jag user User side 2.JPG]]
-	== Solution version 2 ==	+	== SOW 2 ==
-	In this version we attempt to set standards for how/where to configure dashboard panels. It also suggests another approach to adding additional dashboards to the system.	+	'''Mantis:''' '''[http://ct.jaguarfreight.com/mantis/view.php?id=3067 3067]: [* DR/KPI] (Dashboard) Create Dashboard framework'''
-	=== Multiple dashboards ===	+	=== Core requirements ===
-	[[File:Multiple dashbords based on tabs.JPG]]	+	In this version we attempt to set standards for how/where to configure dashboard panels.<br>It also suggests another approach to adding additional dashboards to the system.<br><br>''Approved by Marc --[[User:Alex|Alex]] 14:33, 4 October 2011 (EDT)''
-	=== Persistence ===	+	=== Solution ===
-	System must remember last state (location, state [open/closed], settings) of Dashboard for individual user to reproduce it  at the next login.	+	==== Summary ====
-	=== Settings (configurations) ===	+	===== Dashboard hierarchy =====
-	Levels of dashboard panel management:	+	* Dashboard framework provides displaying of specific widgets on '''Dashboard area''' (Dashboard) of CT2 Home Page only.
		+	** Dashboard area contains specific '''dashboard tabs''' ([[#Multiple dashboards]]) with sets of dashboard panels.
		+	*** Each '''dashboard panel''' reflects specific widget with valuable information.
-	* ''CT2 Admin level settings''	+	[[File:Multiple dashbords based on tabs.JPG]]
-	** settings for each dashboard panel (manage defaults, etc).	+
-	** Location: Home > Admin > Dashboard	+
-	* ''Admin level user settings''	+	Widgets in CT2 can be divided on following groups:
-	** Location: Home > Admin > Users and Offices	+	* '''Informers'''. Actual information from external sources. ''Examples: RSS News Feed, World Financial Markets etc.''
-	**("User profile" managed by superuser)	+	* '''Dashboard Reports'''. Summarized information calculated from CT2 DB. ''Examples: Truck Dom Stats, Scheduled reports, Estimated GM etc.''
-	* ''User level user settings.''	+	===== Configuration =====
-	** Location: Home > User profile	+
-	**("User profile" managed by user)	+
-	==== User level User settings ====	+	* Each CT2 user should have ability to:
		+	** Add any number of additional tabs onto Dashboard and name them arbitrary.
		+	** Assign any available panel to any specific dashboard tab.
		+	*** ''One report can be assigned to one tab only ('''need to clarify!''').''
-	[[File:Client User profile Dash Tab v2.JPG]]	+	==== Details ====
-	==== Admin level user settings ====	+	===== Multiple dashboards =====
-	These could be same list as the above (in this case it would define defaults or could be used to change settings at the Admin level at some point). Or they could include additional settings. Some parameters could be managed at admin level only. In this case they would appear as read only in ''User level User settings''.	+	It is suggested to use scrollable tabs to group and display dashboard panels.
-	==== Company level settings ====	+	[[File:Dashboard-Area.GIF]]
-	In the future it would be also use convenient to have dashboard settings at the company level. In this case if company X purchased widget Y then all users associated with that company will inherit it (with default settings defined at the Company level).	+	* tabs should be named by user (default: one tab named "Main")
		+	* users should be able to assign panels to specific dashboard tabs (default: all panels on "Main" tab)
-	Currently there is no clear link between user and company. User is associated with 2 companies: one through address and another through visibility. Possibly in next version this would be re-considered. See also [[Users]]. That is why this should be part of this version only if "user to company link" functionality is implemented before.	+	===== Settings (configurations) =====
-	==== Manager level settings ====	+	Levels of dashboard panel management:
-	Requirement [[DR_framework#Personalization]] seems to lead to another type of user that has access to certain dashboard parameters for some users. This type of user is a manager who configures DRs for his team.	+	* ''System level''.
		+	** Where: need a new separate section in Admin.
		+	** What: managing of all panels.
		+	*** To keep list of all existing panels (internal and client).
		+	*** To be able to activate panel in System.
		+	*** To set default parameters of panel.
-	There is pros and cons for adding this level. I suggest not to add this functionality in this version.	+	* ''Admin level''.
		+	** Where: User Profile - Dashboard Configuration.
		+	** What: managing of activated panels.
		+	*** To show list of all activated panels (internal and client).
		+	*** To be able to activate panel for certain User (or User role).
-	==== CT2 Admin level settings ====	+	* ''User level''.
		+	** Where: User's "My Profile" section (need to add for Internal App).
		+	** What: managing of dashboard tabs and available panels.
		+	*** To add and name new tab (also edit and remove).
		+	*** To activate panel from list of available panels to display it on Dashboard and assign selected panel to specific tab of Dashboard where it should be displayed.
		+	*** To set custom parameters of panel.
-	Similarly to [[#Company level settings]] these settings regulate defaults in this case on a highest level. Also there could be some other global settings associated with specific panel/widget/DR.	+	[[File:Client User profile Dash Tab v2.JPG]]
-	At this level we could also define what user roles would see what widgets/panels.	+	==== Additionals ====
-	==== Exceptions ====	+	===== Log =====
		+	Actions on System level and Admin level should be recorded in System Log.
		+
		+	===== Exceptions =====
		+	It is possible that it would be hard to fully consolidate all settings for specific widget or DR in one place. For example for Action Required DRs (see [[DR for 9 existing Action Required internal reports]]) certain parameters are defined at the ''Reports Scheduler'' level. ''(In this case, please display in read only format these settings for user)''.
		+
		+	===== Persistence =====
		+	System must remember last state (location, state [open/closed], settings) of Dashboard for individual user to reproduce it  at the next login.
-	It is possible that it would be hard to fully consolidate all settings for specific widget or DR in one place. For example for Action required DRs (see [[DR for 9 existing Action Required internal reports]]) certain parameters are defined at the ''Reports Scheduler'' level.	+	===== Client Visibility Rules =====
		+	* ''Client Visibility Rules'' affect displaying of DR results in Client Application.
	== History ==		== History ==
	=== 0003067: [* DR/KPI] (Dashboard) Create Dashboard framework  ===		=== 0003067: [* DR/KPI] (Dashboard) Create Dashboard framework  ===

---

Current revision as of 22:39, 25 March 2012

Contents 1 Info 2 Business Requirements 3 Glossary 4 Solution version 1 4.1 Dashboard for Internal App 4.2 Dashboard for Client App 5 SOW 2 5.1 Core requirements 5.2 Solution 5.2.1 Summary 5.2.1.1 Dashboard hierarchy 5.2.1.2 Configuration 5.2.2 Details 5.2.2.1 Multiple dashboards 5.2.2.2 Settings (configurations) 5.2.3 Additionals 5.2.3.1 Log 5.2.3.2 Exceptions 5.2.3.3 Persistence 5.2.3.4 Client Visibility Rules 6 History 6.1 0003067: [* DR/KPI] (Dashboard) Create Dashboard framework

[edit] Info

• parent: 0003127: (Dashboard) ......

[edit] Business Requirements

• Need special page with various panels such as Weather, News, etc
• Need separate area on Dashboard for Dashboard Reports (DRs)
• above should be available on both Client and Internal Apps
• need flexible admin to manage above on the system, manager, user levels
• persistence (system must remember last state of dashboard for individual user to reproduce at the next login)

[edit] Glossary

Dashboard - it is a space between Header/Main Menu and Footer on a CT2 Home Page. It contains various Panels ("Widgets") with valuable information such as "Weather", "RSS News feeds" or "Truck Dom Stats Dashboard Report".

One important type of Dashboard widget is Dashboard Report (DR). Sometime we call them KPI. For more info see DR framework wiki.

Fig below explains layout.

[edit] Solution version 1

This is a current version !

Since we have 2 apps currently (Client and Internal) implementation for each slightly differs.

[edit] Dashboard for Internal App

Example:

Example of related config:

[edit] Dashboard for Client App

Client example (Main Dashboard):

KPIs Dashboard (additional dashboard):

Related config (superuser level):

Related config (user level):

[edit] SOW 2

Mantis: 3067: [* DR/KPI] (Dashboard) Create Dashboard framework

[edit] Core requirements

In this version we attempt to set standards for how/where to configure dashboard panels.
It also suggests another approach to adding additional dashboards to the system.

Approved by Marc --Alex 14:33, 4 October 2011 (EDT)

[edit] Solution

[edit] Summary

[edit] Dashboard hierarchy

• Dashboard framework provides displaying of specific widgets on Dashboard area (Dashboard) of CT2 Home Page only.
  • Dashboard area contains specific dashboard tabs (#Multiple dashboards) with sets of dashboard panels.
    • Each dashboard panel reflects specific widget with valuable information.

Widgets in CT2 can be divided on following groups:

• Informers. Actual information from external sources. Examples: RSS News Feed, World Financial Markets etc.
• Dashboard Reports. Summarized information calculated from CT2 DB. Examples: Truck Dom Stats, Scheduled reports, Estimated GM etc.

[edit] Configuration

• Each CT2 user should have ability to:
  • Add any number of additional tabs onto Dashboard and name them arbitrary.
  • Assign any available panel to any specific dashboard tab.
    • One report can be assigned to one tab only (need to clarify!).

[edit] Details

[edit] Multiple dashboards

It is suggested to use scrollable tabs to group and display dashboard panels.

• tabs should be named by user (default: one tab named "Main")
• users should be able to assign panels to specific dashboard tabs (default: all panels on "Main" tab)

[edit] Settings (configurations)

Levels of dashboard panel management:

• System level.
  • Where: need a new separate section in Admin.
  • What: managing of all panels.
    • To keep list of all existing panels (internal and client).
    • To be able to activate panel in System.
    • To set default parameters of panel.

• Admin level.
  • Where: User Profile - Dashboard Configuration.
  • What: managing of activated panels.
    • To show list of all activated panels (internal and client).
    • To be able to activate panel for certain User (or User role).

• User level.
  • Where: User's "My Profile" section (need to add for Internal App).
  • What: managing of dashboard tabs and available panels.
    • To add and name new tab (also edit and remove).
    • To activate panel from list of available panels to display it on Dashboard and assign selected panel to specific tab of Dashboard where it should be displayed.
    • To set custom parameters of panel.

[edit] Additionals

[edit] Log

Actions on System level and Admin level should be recorded in System Log.

[edit] Exceptions

It is possible that it would be hard to fully consolidate all settings for specific widget or DR in one place. For example for Action Required DRs (see DR for 9 existing Action Required internal reports) certain parameters are defined at the Reports Scheduler level. (In this case, please display in read only format these settings for user).

[edit] Persistence

System must remember last state (location, state [open/closed], settings) of Dashboard for individual user to reproduce it at the next login.

[edit] Client Visibility Rules

• Client Visibility Rules affect displaying of DR results in Client Application.

[edit] History

[edit] 0003067: [* DR/KPI] (Dashboard) Create Dashboard framework