port onchanges to API 8.0 to fix #22
Add a second search when no agreement is found

This restore former warning message when we can find an agreement with
not enough quantities
This allow to find and finish the framework agreement almost finished.
As it is preferable to finish agreements completely instead of
contracting new ones and be left with multiple remainings of agreements.
fix issue in cost estimate creation

populate the sourced_by field of the SO line with the PO line doing the
sourcing
fix error using self in api.multi method
fix UnboundLocalError
more details in test
fix: don't set code on PO generated from agreement

When generating a purchase order from a framework agreement, the code
should be auto-generated from the sequence, and not be equal to the code
of the logistic requisition.

This bug was already fixed on v7 by Nicolas Bessi. Then for some reason,
while porting to v8 I re-enabled a commented out line bringing that
back.

Now it is deleted for good.
update the test to fail without the fix

closes lepistone#1
remove currency from LRS: breaks creation
Add an option to set a SO as cost estimate only and create a workflow that will change the Cost Estimate only once it has been sent by mail.
Hide button Confirm Cost Estimate when Cost estimate only is active
Add a filter to see all Cost Estimates Only
Filter tree view to show Done cost estimate only in Cost Estimates
Move user_id on view and rename it Business Unit Officer
Rename project_id to Project code
Add Currency related on pricelist_id
Merge pull request #23 from yvaucher/8.0-framework-agreement-sourcing-fix-onchanges

port onchanges to API 8.0 to fix #22
compute total currency only when data is available

Fixes #33.

This is due to the fact that with the v8 API the methods that compute
function fields are called not only on save, but also as automatic
onchanges. In that situation, `self` is not a true record, but a virtual
NewId that contains only the values present in the view.

That is cool in theory, but in cases like that it can crash because the
requisition_id is empty as it is not present in the view.

This fix does the computation that relies on requisition_id only when it
is available. I do not check explicitly whether self if a NewId, so that
if we manage to fix the view so that we know the requisition_id, the
amount_total_company will be updated on the fly.
bump version
Merge pull request #29 from lepistone/fix-from-agreement-to-po-number

fix: don't set code on PO generated from agreement