This is equivalent to work done for Leave Request, at:
185285c4
(merge_request 493)

Follow a simple / non-simple approach, like for Task and its lines.

In default case, user would need only one Presence Request Period, which can be edited directly on PresenceRequest_view. So, in this case, hide the Listbox containing the Presence Request Periods and have default_presence_request_period being created / edited on background, which will acquire quantity, resource, start_date and stop_date from what is set at the view of the Parent.
In case one or more Presence Request Period are added manually, user would get listbox with sub-objects, and editing should be done directly on them, i.e. fields like my_default_presence_request_period_start_date will be disabled fromPresenceRequest_view.
Additionally, now Presence Request has it's own:
start_date: equal to the minimum start_date of all Presence Request Periods
stop_date: equal to the maximum stop_date of all Presence Request Periods
These values are set by interaction on Presence Request Period, triggered on setStartDate, _setStopDate. This helps so that presence_request_module listbox can have sortable dates.
Commit contains also test that should make it easier to understand.

[erp5_pdm, erp5_trade] Fix bad field library field id. Rename ledger field library proxy field from my_ledger to my_view_mode_ledger.

[ERP5/tests/testERP5Commerce.py] quantity_unit/unit/piece category is used but it does not exist in this test. Add quantity_unit/unit/piece in afterSetUp.

To use non-existing category may lead an unexpected result. This time, getAcquiredCategoryList did not work correctly, then category values of products were not correctly indexed and test_17_getProductListFromWebSection failed.

Revert "[ERP5/tests/testERP5Commerce.py] Add erp5_configurator_standard_categories business template to provide quantity_unit/unit/piece."

This reverts commit 93c6b048.

erp5_configurator_standard_categories depends on too many business templates. I gave up using it.

[ERP5/tests/testERP5Commerce.py] Add erp5_configurator_standard_categories business template to provide quantity_unit/unit/piece.

To use non-existing category may lead an unexpected result. This time, getAcquiredCategoryList did not work correctly, then category values of products were not correctly indexed and test_17_getProductListFromWebSection failed.

/reviewed-on nexedi/erp5!538

This reverts commit 6687e7e0.

Test for bugfix /#/bug_module/20171208-5E8D43

/reviewed-on !529

[erp5_base] Add following movement groups to Order Builder. Order Builder should be able to use the same movement groups as Delivery Builder.

First Causality Movement Group
Invoice Movement Group
Previous Causality Movement Group
Property Grouping Movement Group

[erp5_base] Fix Delivery_getLedgerItemList to make it work with non-Delivery Type portal type documents.

Internal Order
Internal Packing List
Internal Trade Condition
Purchase Invoice
Purchase Order
Purchase Packing List
Purchase Trade Condition
Returned Purchase Order
Returned Purchase Packing List
Returned Sale Order
Returned Sale Packing List
Sale Invoice
Sale Order
Sale Packing List
Sale Trade Condition

[erp5_pdm] Fix proxy fields of order_quantity_unit and time_quantity_unit. Since they are derivations from quantity_unit, "quantity_unit" is needed in the path in the path.

This reverts commit 82c5ae6f.

Add a test to check that hidden rows action update the listbox head

/reviewed-on nexedi/erp5!536

[erp5_core] Allow developers to choose a larger value for the preference of number of lines displayed in listboxes.

[erp5_pdm] Display validation state title of Quantity Unit Conversion Group and Quantity Unit Conversion Definition.

A lot was found with pylint.

Follow a simple / non-simple approach, like for Task and its lines.

In default case, user would need only one Leave Request Period, which
can be edited directly on LeaveRequest_view. So, in this case, hide the Listbox
containing the Leave Request Periods and have default_leave_request_period
being created / edited on background, which will acquire quantity, resource, start_date and stop_date
from what is set at the view of the Parent.

In case one or more Leave Request Period are added manually, user would get
listbox with sub-objects, and editing should be done directly on them, i.e. fields like
my_default_leave_request_period_start_date will be disabled from LeaveRequest_view.

Additionally, now Leave Request has it's own:
- start_date: equal to the minimum start_date of all Leave Request Periods
- stop_date: equal to the maximum stop_date of all Leave Request Periods

These values are set by interaction on Leave Request Period, triggered on
_setStartDate, _setStopDate. This helps so that leave_request_module listbox
can have sortable dates.

Commit contains also <a href="https://lab.nexedi.com/georgios.dagkakis/erp5/blob/leave_request/product/ERP5/tests/testCalendar.py#L1626">test</a> that should make it easier to understand.

Test results <a href="https://nexedi.erp5.net/test_result_module/20171113-20E90B8F">here</a>

@seb we have talked on this and @cedric.leninivin I know you dealt with Leave Requests. Who else should be notified?





/reviewed-on nexedi/erp5!493