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

Rules for handling data entered for invoice amount and invoice allocations #65

Closed
lcreid opened this issue Mar 1, 2017 · 2 comments
Closed

Comments

@lcreid
Copy link
Member

lcreid commented Mar 1, 2017

No description provided.

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

lcreid commented Mar 3, 2017

We want validation of all the money fields in the Invoice form:

When the user enters or changes an amount in the "Amount from this Invoice" field, Javascript will ensure that:

  1. The amount is less than than the Invoice Amount minus the other allocations for the invoice (this is the maximum allowable for this allocation per the invoice). If not, show a message and reduce the amount to the maximum allowable for this allocation.
  2. The amount is less than the the RTP Amount Requested field, minus the allocations against the RTP for other invoices (this is the maximum allowable for this allocation per the RTP. If not, show a message and reduce the amount to the maximum allowable per the RTP.
  3. Calculate the new "Amount Available".
  4. Calculate "Out of Pocket"

When the user enters or changes the invoice amount, then do the above on all the allocations.

@lcreid lcreid changed the title Review what happens when user allocates too much money from an invoice. Rules for handling data entered for invoice amount and invoice allocations Mar 3, 2017
lcreid added a commit that referenced this issue Mar 8, 2017
lcreid added a commit that referenced this issue Mar 15, 2017
@lcreid
Copy link
Member Author

lcreid commented Mar 21, 2017

Decide what to do about messages, if anything, in Issue #78.

@lcreid lcreid closed this as completed Mar 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant