Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show unused amount of RTP in invoice allocation rows #63

Open
lcreid opened this issue Mar 1, 2017 · 3 comments
Open

Show unused amount of RTP in invoice allocation rows #63

lcreid opened this issue Mar 1, 2017 · 3 comments
Assignees
Labels
Milestone

Comments

@lcreid
Copy link
Member

lcreid commented Mar 1, 2017

Show unused amount. Possibly show total RTP request. TBD.

@lcreid lcreid added this to the V00.01.00 milestone Mar 1, 2017
@lcreid
Copy link
Member Author

lcreid commented Mar 3, 2017

Currently shows an "Amount Available" column, but the number displayed appears to be the amount requested on the RTP (for the appropriate Part A or Part B (TBC)).

Suggest:

"Amount of Request": Display the amount requested on the RTP, for Part A if the InvoiceAllocation is for ServiceProvider, or Part B if the InvoiceAllocation is for Supplier. (This will have to be reviewed when we do the form that amends a request.)

"Amount Available": Display the Amount Requested, minus the amount already allocated by this and other invoices.

@lcreid lcreid added the Task label Mar 3, 2017
@lcreid lcreid self-assigned this Mar 7, 2017
@lcreid
Copy link
Member Author

lcreid commented Mar 7, 2017

The two columns are now displayed. The Amount of Request column is showing the right stuff. The Amount Available column is calculated on the back end, and is tested superficially by an integration test.

@lcreid lcreid modified the milestones: V00.02.00, V00.01.00 Mar 20, 2017
@lcreid
Copy link
Member Author

lcreid commented Mar 20, 2017

Consider better unit or other tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant