- 27 Dec, 2017 13 commits
-
-
Łukasz Nowak authored
Note: Generic code shall have no constraints at all. Conflicts: bt5/erp5_accounting/bt/revision
-
Łukasz Nowak authored
It will protect against storing truncated data.
-
Alain Takoudjou authored
If 2 lines have the same effective date (catalog has a 1 second precision), always return the validate and open first. Commit: 02d06501 Changes applied from history: http://git.erp5.org/gitweb/erp5.git/history/refs/heads/interaction-drop:/product/ERP5/Document/SubscriptionItem.py?js=1
-
Rafael Monnerat authored
Original commit from : Lukasz Nowak <luke@nexedi.com> 3e45ec35
-
Alain Takoudjou authored
From Lukasz Nowak: 1- Compensation is undesired. (51c8a250) Raise loudly with message. 2- Disallow any compensation. (3c74ed07) 3- Emit more informative log. (534b2e77)
-
Łukasz Nowak authored
Also minimise activity hurricane by calling expand directly. Open Orders are searched using indexation timestamp, which allows to see them in "windows", and does not repeat expand if not needed. Generate activities and allow to pass the tag. Use search and activate everywhere which will allow to walk through objects without killing the cluster even in case of really big documents. Avoid calling isDivergent which can take few minutes to finish. causality_state comes from well designed causality workflow, which informs enough about delivery state. Fetching causality_state property is extremely fast.
-
Rafael Monnerat authored
Notes: Do nothing on 'calculate' instead of disabling *_causality_interaction_workflow as these interaction workflows do not generate activities directly, and do work that can't be postponed. By contrast, 'calculate' transition of delivery_causality_workflow is modified so that no 'updateCausalityState' activity is created by default. This commit also update list of method_id which should not call calculate_causality
-
Romain Courteaud authored
Conflicts: bt5/erp5_crm/bt/revision
-
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 nexedi/erp5!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 2 commits
-
-
Romain Courteaud authored
-
Romain Courteaud authored
-