[7.0] split invoicing into parts #10
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 6 commits
July 30, 2015 12:56
Conflicts: contract_isp_invoice/contract.py contract_isp_invoice/invoice.py
|
@veloutin Will this change impact the invoice workflow? |
|
@joaoalf I have tried to make no impact. The top-level "create_invoice" and "proforma_voucher" functions do the same thing. They both:
The difference I can see right now is that in proforma_voucher() now respects the company "send_email_contract_invoice" field instead of always sending. |
|
👍 |
1 similar comment
|
👍 |
max3903
approved these changes
Oct 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are doing invoicing through xmlrpc calls of invoice batches. With this PR, the invoicing process can be tackled in parallel batches by splitting the invoice numbering bottleneck into its own operation.