You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current cash payments API takes in an invoice_uuid and an amount for each invoice, as well as the global amount for the cash payment. Since allocation is done once on the server during the WriteCashItems procedure, I propose that we remove the amount field sent to the server with each cash item. Instead, the amount will be calculated from the global payment amount in the WriteCashItems() procedure. That way, we will not have to maintain extra client code for calculating allocations that are never used.
The text was updated successfully, but these errors were encountered:
This commit updates the cash client to follow the new server/db
procedures that were introduced in IMA-WorldHealth#678. In particular, the cash is no
longer exchanged into the enterprise currency on the client. It also
removes the allocation of the cash values from the client.
ClosesIMA-WorldHealth#683.
jniles
pushed a commit
to jniles/bhima
that referenced
this issue
Sep 6, 2016
This commit updates the cash client to follow the new server/db
procedures that were introduced in IMA-WorldHealth#678. In particular, the cash is no
longer exchanged into the enterprise currency on the client. It also
removes the allocation of the cash values from the client.
ClosesIMA-WorldHealth#683.
jniles
pushed a commit
to jniles/bhima
that referenced
this issue
Sep 7, 2016
This commit updates the cash client to follow the new server/db
procedures that were introduced in IMA-WorldHealth#678. In particular, the cash is no
longer exchanged into the enterprise currency on the client. It also
removes the allocation of the cash values from the client.
ClosesIMA-WorldHealth#683.
The current cash payments API takes in an
invoice_uuid
and anamount
for each invoice, as well as the global amount for the cash payment. Since allocation is done once on the server during theWriteCashItems
procedure, I propose that we remove theamount
field sent to the server with each cash item. Instead, theamount
will be calculated from the global payment amount in theWriteCashItems()
procedure. That way, we will not have to maintain extra client code for calculating allocations that are never used.The text was updated successfully, but these errors were encountered: