The more common approach is to design the search or other
functionality to be more flexible, because at the end of the day there
is no way to guarantee a value for many fields, and really to keep
things easy to use and customize in OFBiz we don't want to require too
many fields. Instead the functionality related to those fields should
silently do nothing if the data is not available.
In general just treat null/empty like the default value. In this case
that's probably PARTY_ENABLED.
-David
On Sep 29, 2008, at 10:06 PM, Hans Bakker wrote:
The problem:
currently the status field in party is not checked in the performFind
service, so all popups for party show disabled parties.
The performfind service can only check on 'and-ed' fields,
so to add the status="PARTY_ENABLED" condition could be a solution.
However that means that the party status field cannot be empty.
In order to solve this the following is proposed:
1. change all demo data to include the party status field
2. make sure that by default the create party service sets this
field to
"PARTY_ENABLED"
3. provide a conversion service where existing data can be modified to
fill the empty status field with "PARTY_ENABLED".
any comments or suggestions?
--
Antwebsystems.com: Quality OFBiz services for competitive prices
