DRs on Client App

From UG

(Difference between revisions)
Jump to: navigation, search
(SOW 1 make sure client dashboard reports work)
(SOW 1 make sure client dashboard reports work)
 
Line 22: Line 22:
** user should have same experience as on internal: level 1 (counter), level 2 (summary per parameter) (where exists), level 3 (list of records in HTML), level 4 (download to xls) (where exists)
** user should have same experience as on internal: level 1 (counter), level 2 (summary per parameter) (where exists), level 3 (list of records in HTML), level 4 (download to xls) (where exists)
-
* "back end":
+
=== Reps set by Ops users for Client ===
-
** Jag Ops lead will set up reports through Report Scheduler  
+
 
-
** steps: create instance, select appropriate list of users, select receive as a DB option
+
* Jag Ops lead will set up reports through Report Scheduler  
 +
* steps: create instance, select appropriate list of users, select receive as a DB option
* client app user visibility:
* client app user visibility:
-
** will not be taken into account by system. User who defines instance in Report Scheduler should set appropriate visibility rules (such as Client Company = XYZ)
+
** will not be taken into account by system. Ops User who defines instance in Report Scheduler should set appropriate visibility rules (such as Client Company = XYZ)
 +
 
 +
=== Reps set by Client user himself ===
 +
 
 +
* Client user will set up reports through Reports > Report Scheduler
 +
* there is a limited list of such reports
 +
* steps: create instance, select appropriate list of users, select receive as a DB option
 +
 
 +
NOTE: Filters to remove or to make read only(now they are open which is a bug):
 +
 
 +
* recipients = only current user,
 +
* cc = none,
 +
* bcc = none,
 +
* report for cient company = none,
 +
* report for trucking company = none
 +
 
 +
Client app user visibility:
 +
* will be taken into account by system.
 +
* filters from visibility should propagate and become read only in scheduler. For example:
 +
** if in visibility Client Company = ABC; Shippers = S1 and S2 then these filters in Reps Scheduler will be set and show up as read nay
 +
** these filters lists are the same except Client Company Group, in this case translate group into the List of Client companies
 +
 
 +
How to enable report sched  (implemented):
 +
 
 +
To give Client user possibility create scheduled/dashboard reports below steps should be done on internal app side:
 +
 
 +
*1) Tick check-box "Show scheduler" in "Part G. Report Scheduler" section of Client Company admin.
 +
*2) Client Company with enabled "Show scheduler" option has to be assigned for Client user in user admin.
 +
*3) "Dashboard reports" option has to enabled in Client User admin, "Dashboard configuration" tab.
 +
*4) "Enable Client's reports" option has to be enabled on "Saved/Scheduled Reports" form. (reports->Saved/Scheduled Reports)
 +
*5) "Select what role can schedule reports" option ahs to be set in Admin->Client application ->Admin, "Report scheduler" tab.
=== List of existing DB Reports ===
=== List of existing DB Reports ===

Current revision as of 20:12, 5 February 2013


Contents

[edit] Info

This is about enabling for Client App users DB Reports that are available through Report Scheduler on Client.

[edit] SOW 1 make sure client dashboard reports work

mantis: 0003959: [ASN 20 ph3] make sure client dashboard reports work

spec: see below

Preliminary Notes:

  • This functionality was implemented by sasha with out spec, see mantis 3367.
  • We need to review above now that we have spec and known bugs (such as level 3 does not work)

Requirements for this component:

  • all existing DB Reports should be enabled for Client role (on Client App)
  • "front end":
    • user should have same experience as on internal: level 1 (counter), level 2 (summary per parameter) (where exists), level 3 (list of records in HTML), level 4 (download to xls) (where exists)

[edit] Reps set by Ops users for Client

  • Jag Ops lead will set up reports through Report Scheduler
  • steps: create instance, select appropriate list of users, select receive as a DB option
  • client app user visibility:
    • will not be taken into account by system. Ops User who defines instance in Report Scheduler should set appropriate visibility rules (such as Client Company = XYZ)

[edit] Reps set by Client user himself

  • Client user will set up reports through Reports > Report Scheduler
  • there is a limited list of such reports
  • steps: create instance, select appropriate list of users, select receive as a DB option

NOTE: Filters to remove or to make read only(now they are open which is a bug):

  • recipients = only current user,
  • cc = none,
  • bcc = none,
  • report for cient company = none,
  • report for trucking company = none

Client app user visibility:

  • will be taken into account by system.
  • filters from visibility should propagate and become read only in scheduler. For example:
    • if in visibility Client Company = ABC; Shippers = S1 and S2 then these filters in Reps Scheduler will be set and show up as read nay
    • these filters lists are the same except Client Company Group, in this case translate group into the List of Client companies

How to enable report sched (implemented):

To give Client user possibility create scheduled/dashboard reports below steps should be done on internal app side:

  • 1) Tick check-box "Show scheduler" in "Part G. Report Scheduler" section of Client Company admin.
  • 2) Client Company with enabled "Show scheduler" option has to be assigned for Client user in user admin.
  • 3) "Dashboard reports" option has to enabled in Client User admin, "Dashboard configuration" tab.
  • 4) "Enable Client's reports" option has to be enabled on "Saved/Scheduled Reports" form. (reports->Saved/Scheduled Reports)
  • 5) "Select what role can schedule reports" option ahs to be set in Admin->Client application ->Admin, "Report scheduler" tab.

[edit] List of existing DB Reports

Reports that support dashboard:

  • In Transit
  • Billing Required
  • GM Split
  • Daily EA
  • Daily
  • Impending Delivery/Collection
  • Impending Arrivals/Departures
  • Incomplete
  • Past Due
  • Pre-Alert Report
  • Previous Day Collection
  • Previous Day Delivery
  • Profit/Loss for Multiple CTs

Peports from list above that support level2:

  • In Transit
  • Billing Required
  • GM Split
  • Daily EA
  • Daily
  • Impending Delivery/Collection
  • Impending Arrivals/Departures
  • Incomplete
  • Past Due
  • Previous Day Collection
  • Previous Day Delivery

[edit] SOW 2

[edit] SOW 3

Personal tools