*Fixed wrong field names in erp5_dms.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18397 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Fixed wrong field names around search dialog.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18396 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18394 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18390 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18384 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18383 20353a03-c40f-0410-a6d1-a30d3c3de9de

We still use workflow scripts for "transiant validation" : for example, validating that at the time we validate this transaction an accounting period is open, other parties are not invalidated.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18382 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18381 20353a03-c40f-0410-a6d1-a30d3c3de9de

When testing that validation is refused with something else that a Currency as a resource, at least use a Resource type
Don't check_consistency when creating invalid transactions



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18380 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18379 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18378 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18375 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Acquire skins and tools from a portal, whenever possible.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18374 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18373 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18372 20353a03-c40f-0410-a6d1-a30d3c3de9de

Also change the behaviour a bit, don't raise an Exception directly, constraints
should *not* raise exceptions, simply use _generateError. What we should do is
add support for different severity in Constraints framework.



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18369 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18368 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18367 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18366 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18365 20353a03-c40f-0410-a6d1-a30d3c3de9de

each constraint class are predefined on the class and constraint users can
override the message in the propertysheet.
The motivation is to be able to provide user friendly context dependant
messages, eg. "Please Enter the Shipping Date" instead of technical messages
like "Property start_date is not defined".
See test_OverrideMessage for an example use, and the interface for more info.

(Also add a new CategoryAcquiredExistence constraint)



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18364 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18363 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18362 20353a03-c40f-0410-a6d1-a30d3c3de9de

Move all code relative to dict_length_ids in a code which access is controled by "store" value. This prevents portal_ids' persistent object modifications when "store" is false.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18361 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18359 20353a03-c40f-0410-a6d1-a30d3c3de9de

another timezone than UTC.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18358 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18357 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18356 20353a03-c40f-0410-a6d1-a30d3c3de9de

- remove duplicate empty entries in frequency lists
- add '0' entries in hour and minute lists
- replace map(lambda) by list comprehensions

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18355 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18354 20353a03-c40f-0410-a6d1-a30d3c3de9de

well update an modify it


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18353 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18352 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18351 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18350 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18349 20353a03-c40f-0410-a6d1-a30d3c3de9de

- add a "Model Inheritance" column in PaySheetModelModule_viewPaySheetModelList listbox

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18348 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18347 20353a03-c40f-0410-a6d1-a30d3c3de9de

sub objects of a model are already added, the model will not be present in the
final dict.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18346 20353a03-c40f-0410-a6d1-a30d3c3de9de

wich use a Breadth First Search instead of Depth First Search witch is very more appropiate in this case.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18345 20353a03-c40f-0410-a6d1-a30d3c3de9de

- remove commented code
- modify getInheritanceModelReferenceDict  method to use a Breadth First Search
  instead of Depth First Search witch is very more appropiate in this case.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18344 20353a03-c40f-0410-a6d1-a30d3c3de9de