Edit #143
ProjectCBTS - Dev - obsoleted
Opened by Steven Loh
On2017-02-26
StatusReady for Testing
Labels
Task

Priority 
Assigned ToHorWT
External ID
Open in release
Fixed/Target in release



[Billing - Customer Billing - CN/DN]: Add / Edit CN/DN

Created 26 Feb 2017, by Steven Loh

Objective

Allow finance users to create a CN/DN to alter or modify the contents of an existing invoice which have been issued.

A CN is to create a price decrease to the targeted invoice amount, while DN is to create a price increase to the targeted invoice amount.

Tasks

  1. Implement the add CN/DN pop-up for customer invoice. Note that this pop-up will be reused for internal invoice and miscellaneous invoice.
  2. Create the following to allow user to bring up the add CN/DN pop-up:
    • A link in customer invoice listing table action panel to "Add CN".
    • A link in customer invoice listing table action panel to "Add DN".
    • Add an "Add CN" button in customer invoice detail pop-up.
    • Add an "Add DN" button in customer invoice detail pop-up.
  3. This add CN/DN pop-up must be able to support edit (update) CN/DN.

Entity relationships

  1. One customer CN or DN to at least one to many customer invoice.
  2. Similar to customer invoice, one CN or DN contains at least one to many service charges.
  3. Each service charge of a CN or DN relates to only one booking.

Constraints

  1. A new CN/DN can be issued when the invoice status is between confirmed (inclusive) and cancelled (exclusive).
  2. To issue a CN/DN for a customer invoice, the CN/DN must be associated to only one customer invoice.
  3. The constraints of updating an existing CN/DN shall follow invoice constraints, i.e. at the moment of writing - as long as it's not cancelled and within the accounting period.
  4. All service charges created in a CN/DN must be associated to only one booking.

Data visibility and access rights

  1. A user can only create CN/DN for an invoice that he/she has visibility to.

UI mock-up

Implement this task using the mock-up attached as reference.

Assumptions

None

Task estimation

Development: 24 hours (12 hrs mock, 12 hrs BO integration)
Review: 2 hours
Testing: 6 hours

Comments
Commits

HorWT was assigned by HorWT
Thursday March 09, 2017 - 02:18:59

HorWT change status to Fixed/Done
Friday April 07, 2017 - 10:10:53

Steven Loh was assigned by HorWT
Friday April 07, 2017 - 10:10:53

HorWT was assigned by HorWT
Friday April 07, 2017 - 10:10:56

Anupama
Monday April 10, 2017 - 08:43:43
Pending verification in the task:The constraints of updating an existing CN/DN shall follow invoice constraints, i.e. at the moment of writing - as long as it's not cancelled and within the accounting period.
Display Comment and Event



uBugtrack - Built with ♥ by a passionate small team located in Nice, France.
Plans & pricing - News & Changelog - uBugtrack API - Simple Agile Methodology - Privacy - Status
Follow on twitter