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 28: Line 28:
* 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. User who defines instance in Report Scheduler should set appropriate visibility rules (such as Client Company = XYZ)
 +
 +
=== 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
== SOW 2 ==
== SOW 2 ==
== SOW 3 ==
== SOW 3 ==

Revision as of 17:46, 28 January 2013


Contents

Info

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

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, Shipper, Planner user roles
  • "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)
  • "back end":
    • 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. User who defines instance in Report Scheduler should set appropriate visibility rules (such as Client Company = XYZ)

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

SOW 2

SOW 3

Personal tools