- 28 Dec, 2017 3 commits
-
-
Yusei Tahara authored
[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.
-
Yusei Tahara authored
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.
-
Yusei Tahara authored
[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.
-
- 27 Dec, 2017 5 commits
-
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Tomáš Peterka authored
/reviewed-on nexedi/erp5!538
-
Yusei Tahara authored
-
- 26 Dec, 2017 13 commits
-
-
Cédric Le Ninivin authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Cédric Le Ninivin authored
This reverts commit 6687e7e0.
-
Cédric Le Ninivin authored
-
Tomáš Peterka authored
Test for bugfix /#/bug_module/20171208-5E8D43 /reviewed-on nexedi/erp5!529
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Yusei Tahara authored
[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
-
Yusei Tahara authored
[erp5_base] Fix Delivery_getLedgerItemList to make it work with non-Delivery Type portal type documents.
-
Yusei Tahara authored
-
Yusei Tahara authored
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
-
- 25 Dec, 2017 1 commit
-
-
Yusei Tahara authored
[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.
-
- 22 Dec, 2017 5 commits
-
-
Romain Courteaud authored
This reverts commit 82c5ae6f. Add a test to check that hidden rows action update the listbox head
-
Tomáš Peterka authored
/reviewed-on !536
-
Yusei Tahara authored
[erp5_core] Allow developers to choose a larger value for the preference of number of lines displayed in listboxes.
-
Yusei Tahara authored
-
Yusei Tahara authored
[erp5_pdm] Display validation state title of Quantity Unit Conversion Group and Quantity Unit Conversion Definition.
-
- 21 Dec, 2017 4 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
A lot was found with pylint.
-
Julien Muchembled authored
-
Nicolas Wavrant authored
-
- 20 Dec, 2017 2 commits
-
-
Roque authored
-
Georgios Dagkakis authored
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
-
- 19 Dec, 2017 3 commits
-
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Tristan Cavelier authored
-
- 18 Dec, 2017 2 commits
-
-
Romain Courteaud authored
ERP5 doesn't provide any information about the timezone used internally. As test doesn't know the selenium browser locale, full text can't be checked.
-
Yusei Tahara authored
[erp5_core, erp5_property_sheets, erp5_pdm] Add time_quantity_unit and order_quantity_unit categories and add max/min order quantity to supply. Also cleaning up proxy fields for supply view forms.
-
- 15 Dec, 2017 2 commits
-
-
Tristan Cavelier authored
-
Ayush Tiwari authored
After migration of catalog to ERP5-ified document, its better to migrate all the catalog methods (`ZSQL Method, Python Script`) to new format. This will save the time during migration for developers and will reduce the chance for error during *import_in_old_format >> export_in_new_format* process. Some important changes during re-export: - Classes for new catalog methods are now defined via `portal_type` - Filter is now defined via properties, so no need to save their properties in `.catalog_keys.xml` file. /reviewed-on nexedi/erp5!518
-