Example Use case:
1. Set Default logic for some parameter of report or process (i.e. CO for DocStatus of Shipment Details)
2. Login as Garden World, open this process/report and try to set Value Preference for same parameter with different value
3. Close and reopen process/report window
Result: Value Preference is overridden by Defult Logic. This should be inverted, because user is not possible to set his own Value Preference for fields with default logic.
Thanks , the test you described is ok.
Today we faced problem when SQL default logic was not applied to process parameters. We needed to add sys config ZK_SEQ_DEFAULT_VALUE_PANEL for to value "623" to support old behaviour. I suggest to change this value also in code on line 582. "62" is not enough as default behaviour.
Hi , now it can configuration, so let implement decide it.
default value of system for process parameter and infoWindow parameter follow old logic of parameter in infoWindow, it don't use type and database default value.
i think it's acceptable.
I mean default logic from process parameter like @SQL=SELECT.... is not considering now which breaks old logic.. Also I understand that it's possible to set sys config, but we should never break old logic of system
Thanks , testing "Initial Client Setup", the fields country and currency were not filled properly (as they were in 2.1 via a @SQL default).
Fixed with http://bitbucket.org/idempiere/idempiere/commits/5ac23bf
Now I see a different issue about the list of regions not refreshing when the country changes.