Re: Fwd: [PROPOSAL] Enable entity timestamp fields

2019-04-27 Thread Pawan Verma
Hello All,

I have attached a patch for this improvement on the task.

Added include-internal attribute in auto-fields-entity with default value
false. And in FindGeneric.groovy, for list records set it to true.

Please let me know in case of any concern.
-- 
Kind Regards,
*Pawan Verma* | Technical Consultant
HotWax Systems 
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P. 452010
Linkedin: *Pawan Verma *


On Fri, Apr 26, 2019 at 12:31 PM Pawan Verma 
wrote:

> Thank You, everyone, for the inputs. I have logged Jira for this
> https://issues.apache.org/jira/browse/OFBIZ-10959.
> --
> Kind Regards,
> *Pawan Verma* | Technical Consultant
> HotWax Systems 
> Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> Indore, M.P. 452010
> Linkedin: *Pawan Verma *
>
>
> On Wed, Apr 24, 2019 at 7:06 PM Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
>> Thanks Guys,
>>
>> Makes sense to me
>>
>> Jacques
>>
>> Le 24/04/2019 à 08:36, Deepak Dixit a écrit :
>> > On Wed, Apr 24, 2019 at 11:58 AM Nicolas Malin <
>> nicolas.ma...@nereide.fr>
>> > wrote:
>> >
>> >> Hello,
>> >>
>> >> On 24/04/2019 08:01, Deepak Dixit wrote:
>> >>> I think it's removed while converting find generic ftl to form widget
>> >>> at OFBIZ-9217
>> >> Yes it's me :)
>> > Was it intentional? If yes what was the reason?
>> >> Yes and not, when I converted it to widget screen I did a choice slim
>> >> code, increase functionality but lose timestamp field on result list.
>> >>> I think it's not intentional, form widget auto-fields-entity exclude
>> the
>> >>> stamp filed, that's why it's not rendering on webtools find generic
>> page.
>> >> If you want to enable it, I suggest to improve auto-fields-entity
>> system
>> >> to support internal fields by parameters
>> >>
>> >
>> > Agree, we can extend auto-fields-entity and add an option to include
>> > internal default value will be false.
>> >
>> > @Pawan, Could you please open a Jira ticket for the same?
>> >
>> > Thanks & Regads
>> > --
>> > Deepak Dixit
>> >
>> >
>> >> Nicolas
>> >>
>> >>> Kind Regards,
>> >>> Deepak Dixit
>> >>>
>> >>>
>> >>> On Fri, Apr 19, 2019 at 10:57 PM Jacques Le Roux <
>> >>> jacques.le.r...@les7arts.com> wrote:
>> >>>
>>  Hi Pawan,
>> 
>>  Seems to make sense, do you know when (by which commit) it has been
>>  removed. Was it intentional? If yes what was the reason?
>> 
>>  Thanks
>> 
>>  Jacques
>> 
>>  Le 19/04/2019 à 18:03, Pawan Verma a écrit :
>> > Hello  Devs,
>> >
>> > While working on a Production environment, I have found that for
>> some
>> > reason entity timestamp fields are disabled at Search Results
>> screen in
>> > Trunk and the previous release branch. It is available at View Value
>> > screen. It was enabled in Release 16.11.
>> >
>> > These fields are helpful for developers to get the idea about when
>> the
>>  row
>> > in the entity is created/updated. Extremely helpful while working on
>> >> the
>> > Production environment.
>> >
>> > I propose to reenable these fields. Views/suggestions are most
>> welcome.
>> >
>>
>


Re: Fwd: [PROPOSAL] Enable entity timestamp fields

2019-04-26 Thread Pawan Verma
Thank You, everyone, for the inputs. I have logged Jira for this
https://issues.apache.org/jira/browse/OFBIZ-10959.
-- 
Kind Regards,
*Pawan Verma* | Technical Consultant
HotWax Systems 
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P. 452010
Linkedin: *Pawan Verma *


On Wed, Apr 24, 2019 at 7:06 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Thanks Guys,
>
> Makes sense to me
>
> Jacques
>
> Le 24/04/2019 à 08:36, Deepak Dixit a écrit :
> > On Wed, Apr 24, 2019 at 11:58 AM Nicolas Malin  >
> > wrote:
> >
> >> Hello,
> >>
> >> On 24/04/2019 08:01, Deepak Dixit wrote:
> >>> I think it's removed while converting find generic ftl to form widget
> >>> at OFBIZ-9217
> >> Yes it's me :)
> > Was it intentional? If yes what was the reason?
> >> Yes and not, when I converted it to widget screen I did a choice slim
> >> code, increase functionality but lose timestamp field on result list.
> >>> I think it's not intentional, form widget auto-fields-entity exclude
> the
> >>> stamp filed, that's why it's not rendering on webtools find generic
> page.
> >> If you want to enable it, I suggest to improve auto-fields-entity system
> >> to support internal fields by parameters
> >>
> >
> > Agree, we can extend auto-fields-entity and add an option to include
> > internal default value will be false.
> >
> > @Pawan, Could you please open a Jira ticket for the same?
> >
> > Thanks & Regads
> > --
> > Deepak Dixit
> >
> >
> >> Nicolas
> >>
> >>> Kind Regards,
> >>> Deepak Dixit
> >>>
> >>>
> >>> On Fri, Apr 19, 2019 at 10:57 PM Jacques Le Roux <
> >>> jacques.le.r...@les7arts.com> wrote:
> >>>
>  Hi Pawan,
> 
>  Seems to make sense, do you know when (by which commit) it has been
>  removed. Was it intentional? If yes what was the reason?
> 
>  Thanks
> 
>  Jacques
> 
>  Le 19/04/2019 à 18:03, Pawan Verma a écrit :
> > Hello  Devs,
> >
> > While working on a Production environment, I have found that for some
> > reason entity timestamp fields are disabled at Search Results screen
> in
> > Trunk and the previous release branch. It is available at View Value
> > screen. It was enabled in Release 16.11.
> >
> > These fields are helpful for developers to get the idea about when
> the
>  row
> > in the entity is created/updated. Extremely helpful while working on
> >> the
> > Production environment.
> >
> > I propose to reenable these fields. Views/suggestions are most
> welcome.
> >
>


Re: Fwd: [PROPOSAL] Enable entity timestamp fields

2019-04-24 Thread Jacques Le Roux

Thanks Guys,

Makes sense to me

Jacques

Le 24/04/2019 à 08:36, Deepak Dixit a écrit :

On Wed, Apr 24, 2019 at 11:58 AM Nicolas Malin 
wrote:


Hello,

On 24/04/2019 08:01, Deepak Dixit wrote:

I think it's removed while converting find generic ftl to form widget
at OFBIZ-9217

Yes it's me :)

Was it intentional? If yes what was the reason?

Yes and not, when I converted it to widget screen I did a choice slim
code, increase functionality but lose timestamp field on result list.

I think it's not intentional, form widget auto-fields-entity exclude the
stamp filed, that's why it's not rendering on webtools find generic page.

If you want to enable it, I suggest to improve auto-fields-entity system
to support internal fields by parameters



Agree, we can extend auto-fields-entity and add an option to include
internal default value will be false.

@Pawan, Could you please open a Jira ticket for the same?

Thanks & Regads
--
Deepak Dixit



Nicolas


Kind Regards,
Deepak Dixit


On Fri, Apr 19, 2019 at 10:57 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Hi Pawan,

Seems to make sense, do you know when (by which commit) it has been
removed. Was it intentional? If yes what was the reason?

Thanks

Jacques

Le 19/04/2019 à 18:03, Pawan Verma a écrit :

Hello  Devs,

While working on a Production environment, I have found that for some
reason entity timestamp fields are disabled at Search Results screen in
Trunk and the previous release branch. It is available at View Value
screen. It was enabled in Release 16.11.

These fields are helpful for developers to get the idea about when the

row

in the entity is created/updated. Extremely helpful while working on

the

Production environment.

I propose to reenable these fields. Views/suggestions are most welcome.



Re: Fwd: [PROPOSAL] Enable entity timestamp fields

2019-04-24 Thread Deepak Dixit
On Wed, Apr 24, 2019 at 11:58 AM Nicolas Malin 
wrote:

> Hello,
>
> On 24/04/2019 08:01, Deepak Dixit wrote:
> > I think it's removed while converting find generic ftl to form widget
> > at OFBIZ-9217
> Yes it's me :)
> >>> Was it intentional? If yes what was the reason?
> Yes and not, when I converted it to widget screen I did a choice slim
> code, increase functionality but lose timestamp field on result list.
> > I think it's not intentional, form widget auto-fields-entity exclude the
> > stamp filed, that's why it's not rendering on webtools find generic page.
>
> If you want to enable it, I suggest to improve auto-fields-entity system
> to support internal fields by parameters
>


Agree, we can extend auto-fields-entity and add an option to include
internal default value will be false.

@Pawan, Could you please open a Jira ticket for the same?

Thanks & Regads
--
Deepak Dixit


>
> Nicolas
>
> >
> > Kind Regards,
> > Deepak Dixit
> >
> >
> > On Fri, Apr 19, 2019 at 10:57 PM Jacques Le Roux <
> > jacques.le.r...@les7arts.com> wrote:
> >
> >> Hi Pawan,
> >>
> >> Seems to make sense, do you know when (by which commit) it has been
> >> removed. Was it intentional? If yes what was the reason?
> >>
> >> Thanks
> >>
> >> Jacques
> >>
> >> Le 19/04/2019 à 18:03, Pawan Verma a écrit :
> >>> Hello  Devs,
> >>>
> >>> While working on a Production environment, I have found that for some
> >>> reason entity timestamp fields are disabled at Search Results screen in
> >>> Trunk and the previous release branch. It is available at View Value
> >>> screen. It was enabled in Release 16.11.
> >>>
> >>> These fields are helpful for developers to get the idea about when the
> >> row
> >>> in the entity is created/updated. Extremely helpful while working on
> the
> >>> Production environment.
> >>>
> >>> I propose to reenable these fields. Views/suggestions are most welcome.
> >>>
>


Re: Fwd: [PROPOSAL] Enable entity timestamp fields

2019-04-24 Thread Nicolas Malin

Hello,

On 24/04/2019 08:01, Deepak Dixit wrote:

I think it's removed while converting find generic ftl to form widget
at OFBIZ-9217

Yes it's me :)

Was it intentional? If yes what was the reason?
Yes and not, when I converted it to widget screen I did a choice slim 
code, increase functionality but lose timestamp field on result list.

I think it's not intentional, form widget auto-fields-entity exclude the
stamp filed, that's why it's not rendering on webtools find generic page.


If you want to enable it, I suggest to improve auto-fields-entity system 
to support internal fields by parameters


Nicolas



Kind Regards,
Deepak Dixit


On Fri, Apr 19, 2019 at 10:57 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Hi Pawan,

Seems to make sense, do you know when (by which commit) it has been
removed. Was it intentional? If yes what was the reason?

Thanks

Jacques

Le 19/04/2019 à 18:03, Pawan Verma a écrit :

Hello  Devs,

While working on a Production environment, I have found that for some
reason entity timestamp fields are disabled at Search Results screen in
Trunk and the previous release branch. It is available at View Value
screen. It was enabled in Release 16.11.

These fields are helpful for developers to get the idea about when the

row

in the entity is created/updated. Extremely helpful while working on the
Production environment.

I propose to reenable these fields. Views/suggestions are most welcome.



Fwd: [PROPOSAL] Enable entity timestamp fields

2019-04-24 Thread Deepak Dixit
I think it's removed while converting find generic ftl to form widget
at OFBIZ-9217

>>Was it intentional? If yes what was the reason?

I think it's not intentional, form widget auto-fields-entity exclude the
stamp filed, that's why it's not rendering on webtools find generic page.

Kind Regards,
Deepak Dixit


On Fri, Apr 19, 2019 at 10:57 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi Pawan,
>
> Seems to make sense, do you know when (by which commit) it has been
> removed. Was it intentional? If yes what was the reason?
>
> Thanks
>
> Jacques
>
> Le 19/04/2019 à 18:03, Pawan Verma a écrit :
> > Hello  Devs,
> >
> > While working on a Production environment, I have found that for some
> > reason entity timestamp fields are disabled at Search Results screen in
> > Trunk and the previous release branch. It is available at View Value
> > screen. It was enabled in Release 16.11.
> >
> > These fields are helpful for developers to get the idea about when the
> row
> > in the entity is created/updated. Extremely helpful while working on the
> > Production environment.
> >
> > I propose to reenable these fields. Views/suggestions are most welcome.
> >
>