usage of party entity status field

[hans_bakker]

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
       

[David E Jones]

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
>
>

[hans_bakker]

but the problem is performFind cannot do that.... and adding this to
performfind is a major undertaking for us...

so be it....


On Mon, 2008-09-29 at 22:38 -0600, David E Jones wrote:

> 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
> >
> >
>

--
Antwebsystems.com: Quality OFBiz services for competitive prices

[Scott Gray]

Hi Hans

You could always run the prepareFind service in a groovy script, add
your extra condition for the null and then run the executeFind
service.  It's not too much coding and you can copy most of it
straight from the performFind service.

Regards
Scott

2008/9/30 Hans Bakker <[hidden email]>:

> but the problem is performFind cannot do that.... and adding this to
> performfind is a major undertaking for us...
>
> so be it....
>
>
> On Mon, 2008-09-29 at 22:38 -0600, David E Jones wrote:
>> 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
>> >
>> >
>>
> --
> Antwebsystems.com: Quality OFBiz services for competitive prices
>
>

[hans_bakker]

Thanks Scott i will have a look into that....

however i stiil think that making the status field mandatory and filled
as in any other status field, would be much easier for many other
programs/views which now have to use this special treatment

thanks again for your suggestion...

Regards,
Hans

On Tue, 2008-09-30 at 20:37 +1300, Scott Gray wrote:

> Hi Hans
>
> You could always run the prepareFind service in a groovy script, add
> your extra condition for the null and then run the executeFind
> service.  It's not too much coding and you can copy most of it
> straight from the performFind service.
>
> Regards
> Scott
>
> 2008/9/30 Hans Bakker <[hidden email]>:
> > but the problem is performFind cannot do that.... and adding this to
> > performfind is a major undertaking for us...
> >
> > so be it....
> >
> >
> > On Mon, 2008-09-29 at 22:38 -0600, David E Jones wrote:
> >> 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
> >> >
> >> >
> >>
> > --
> > Antwebsystems.com: Quality OFBiz services for competitive prices
> >
> >

--
Antwebsystems.com: Quality OFBiz services for competitive prices

[Adrian Crum-2]

Or modify the performFind service so it accepts an optional EntityCondition parameter that contains additional permissions.

-Adrian


--- On Tue, 9/30/08, Scott Gray <[hidden email]> wrote:

> From: Scott Gray <[hidden email]>
> Subject: Re: usage of party entity status field
> To: [hidden email]
> Date: Tuesday, September 30, 2008, 12:37 AM
> Hi Hans
>
> You could always run the prepareFind service in a groovy
> script, add
> your extra condition for the null and then run the
> executeFind
> service.  It's not too much coding and you can copy
> most of it
> straight from the performFind service.
>
> Regards
> Scott
>
> 2008/9/30 Hans Bakker
> <[hidden email]>:
> > but the problem is performFind cannot do that.... and
> adding this to
> > performfind is a major undertaking for us...
> >
> > so be it....
> >
> >
> > On Mon, 2008-09-29 at 22:38 -0600, David E Jones
> wrote:
> >> 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
> >> >
> >> >
> >>
> > --
> > Antwebsystems.com: Quality OFBiz services for
> competitive prices
> >
> >