[jira] [Updated] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12664: - Description: The callback element added by the Jira OFBIZ-11812 allows to refresh a screen area without reloading the whole page. However, if you want to use this mechanism in a "tunnel" process, this parameter must be propagated manually between each form so that the final validation and closing of the modal triggers the execution of the callback. The attached patch adds a propagate-callback parameter on submitButton that will automatically propagate the callback between the forms, simplifying the writing for the developer For example: A modal allowing to create an actor on the step 1 form and then allow to attach this actor to a task in the second step. To test, apply the Example.patch on a trunk environment (with demo data) then go to the following page and click on the "Create" menu button to open the first modal: [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1] The validation of the second step should refresh the WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen was: The callback element added by the Jira OFBIZ-11812 allows to refresh a screen area without reloading the whole page. However, if you want to use this mechanism in a "tunnel" process, this parameter must be propagated manually between each form so that the final validation and closing of the modal triggers the execution of the callback. The attached patch adds a propagate-callback parameter on submitButton that will automatically propagate the callback between the forms, simplifying the writing for the developer For example: A modal allowing to create an actor on the step 1 form and then allow to attach this actor to a task in the second step. To test, apply the Example.patch on a trunk environment (with demo data) then go to the following page and click on the "Create" menu button to open the first modal: [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=9000] The validation of the second step should refresh the WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12664: - Attachment: OFBIZ-12664v2.patch > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch, > OFBIZ-12664v2.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12664: - Attachment: OFBIZ-12664v2-1.patch > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch, > OFBIZ-12664v2.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12664: - Attachment: OFBIZ-12664v2.patch > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch, > OFBIZ-12664v2.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12664: - Attachment: (was: OFBIZ-12664v2.patch) > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch, > OFBIZ-12664v2.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12664: - Attachment: (was: OFBIZ-12664v2-1.patch) > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch, > OFBIZ-12664v2.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12664: - Attachment: (was: OFBIZ-12664v2.patch) > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12664: - Attachment: OFBIZ-12664v2.patch > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch, > OFBIZ-12664v2.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-12664. Resolution: Fixed > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch, > OFBIZ-12664v2.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1|https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=1] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12702) Groovy script error when creating a communication event role
[ https://issues.apache.org/jira/browse/OFBIZ-12702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17617799#comment-17617799 ] Mekika Leila commented on OFBIZ-12702: -- Thank you Jacques for the update and for the link ! I saw your update on the fix version and I tought I have forgotten more :) > Groovy script error when creating a communication event role > > > Key: OFBIZ-12702 > URL: https://issues.apache.org/jira/browse/OFBIZ-12702 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: 22.01.01 > > > On the communication event role management screen, when trying to create a > new role the following error is returned "No such property: contactMechs for > class: CommunicationEventServices" > This comes from an error in the CommunicationEventServices groovy script > createCommunicationEventRole -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12702) Groovy script error when creating a communication event role
[ https://issues.apache.org/jira/browse/OFBIZ-12702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12702: - Fix Version/s: Upcoming Branch > Groovy script error when creating a communication event role > > > Key: OFBIZ-12702 > URL: https://issues.apache.org/jira/browse/OFBIZ-12702 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: 22.01.01, Upcoming Branch > > > On the communication event role management screen, when trying to create a > new role the following error is returned "No such property: contactMechs for > class: CommunicationEventServices" > This comes from an error in the CommunicationEventServices groovy script > createCommunicationEventRole -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12702) Groovy script error when creating a communication event role
[ https://issues.apache.org/jira/browse/OFBIZ-12702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-12702. Resolution: Fixed > Groovy script error when creating a communication event role > > > Key: OFBIZ-12702 > URL: https://issues.apache.org/jira/browse/OFBIZ-12702 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > > On the communication event role management screen, when trying to create a > new role the following error is returned "No such property: contactMechs for > class: CommunicationEventServices" > This comes from an error in the CommunicationEventServices groovy script > createCommunicationEventRole -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12702) Groovy script error when creating a communication event role
Mekika Leila created OFBIZ-12702: Summary: Groovy script error when creating a communication event role Key: OFBIZ-12702 URL: https://issues.apache.org/jira/browse/OFBIZ-12702 Project: OFBiz Issue Type: Bug Components: party Affects Versions: 22.01.01, Upcoming Branch Reporter: Mekika Leila On the communication event role management screen, when trying to create a new role the following error is returned "No such property: contactMechs for class: CommunicationEventServices" This comes from an error in the CommunicationEventServices groovy script createCommunicationEventRole -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12702) Groovy script error when creating a communication event role
[ https://issues.apache.org/jira/browse/OFBIZ-12702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12702: Assignee: Mekika Leila > Groovy script error when creating a communication event role > > > Key: OFBIZ-12702 > URL: https://issues.apache.org/jira/browse/OFBIZ-12702 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > > On the communication event role management screen, when trying to create a > new role the following error is returned "No such property: contactMechs for > class: CommunicationEventServices" > This comes from an error in the CommunicationEventServices groovy script > createCommunicationEventRole -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12679) RuntimeData and RecurrenceInfo not cleaned after job purge
[ https://issues.apache.org/jira/browse/OFBIZ-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-12679. Fix Version/s: 22.01.01 Resolution: Fixed > RuntimeData and RecurrenceInfo not cleaned after job purge > -- > > Key: OFBIZ-12679 > URL: https://issues.apache.org/jira/browse/OFBIZ-12679 > Project: OFBiz > Issue Type: Bug > Components: framework/service >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Gaetan Chaboussie >Assignee: Mekika Leila >Priority: Major > Fix For: 22.01.01 > > Attachments: Mutualisation_et_correction.patch, Test.patch > > > We noticed that the purging of jobs doesn't clean the related RuntimeData and > RecurrenceInfo > We created an integration test for development and reproduction of bug, > provided in the first patch > For the fix, we get the relevant runtimeDataId and recurrenceInfoId to pass > to the delegator in getRelatedOne method. > See the second patch > We also offer a small code rework/ mutualization of the Job related object. > Thanks to [~pgil] for his help -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12679) RuntimeData and RecurrenceInfo not cleaned after job purge
[ https://issues.apache.org/jira/browse/OFBIZ-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651207#comment-17651207 ] Mekika Leila commented on OFBIZ-12679: -- Thank you Gaëtan and Gil I tested it before and after corrective patch and it seemed alright with command : ./gradlew 'ofbiz -t component=service -t suitename=servicetests -t case=service-purge-test' For information, I will move the tests in src/main packages so it won't execute as integration test > RuntimeData and RecurrenceInfo not cleaned after job purge > -- > > Key: OFBIZ-12679 > URL: https://issues.apache.org/jira/browse/OFBIZ-12679 > Project: OFBiz > Issue Type: Bug > Components: framework/service >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Gaetan Chaboussie >Assignee: Mekika Leila >Priority: Major > Attachments: Mutualisation_et_correction.patch, Test.patch > > > We noticed that the purging of jobs doesn't clean the related RuntimeData and > RecurrenceInfo > We created an integration test for development and reproduction of bug, > provided in the first patch > For the fix, we get the relevant runtimeDataId and recurrenceInfoId to pass > to the delegator in getRelatedOne method. > See the second patch > We also offer a small code rework/ mutualization of the Job related object. > Thanks to [~pgil] for his help -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12679) RuntimeData and RecurrenceInfo not cleaned after job purge
[ https://issues.apache.org/jira/browse/OFBIZ-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12679: Assignee: Mekika Leila > RuntimeData and RecurrenceInfo not cleaned after job purge > -- > > Key: OFBIZ-12679 > URL: https://issues.apache.org/jira/browse/OFBIZ-12679 > Project: OFBiz > Issue Type: Bug > Components: framework/service >Affects Versions: 22.01.01, Upcoming Branch >Reporter: Gaetan Chaboussie >Assignee: Mekika Leila >Priority: Major > Attachments: Mutualisation_et_correction.patch, Test.patch > > > We noticed that the purging of jobs doesn't clean the related RuntimeData and > RecurrenceInfo > We created an integration test for development and reproduction of bug, > provided in the first patch > For the fix, we get the relevant runtimeDataId and recurrenceInfoId to pass > to the delegator in getRelatedOne method. > See the second patch > We also offer a small code rework/ mutualization of the Job related object. > Thanks to [~pgil] for his help -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12727) Error when calling service updateCustRequestItem
Mekika Leila created OFBIZ-12727: Summary: Error when calling service updateCustRequestItem Key: OFBIZ-12727 URL: https://issues.apache.org/jira/browse/OFBIZ-12727 Project: OFBiz Issue Type: Bug Components: order Affects Versions: 22.01.01 Reporter: Mekika Leila When we try to update a custRequest item, OFBiz returns the error "Service invocation error (Could not find SimpleMethod XML document in resource:" To reproduce, with demo datas loaded, go to the item modification form from request 9000 "https://localhost:8443/ordermgr/control/requestitems?custRequestId=9000; And try to update line 1 The error is displayed and no modification is made. The problem seems to come from the service definition which has been converted to entity-auto (OFBIZ-1166) but still points to "simple" engine. The given patch update the engine to entity-auto -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12727) Error when calling service updateCustRequestItem
[ https://issues.apache.org/jira/browse/OFBIZ-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12727: - Attachment: OFBIZ-12727_R22_01.patch > Error when calling service updateCustRequestItem > > > Key: OFBIZ-12727 > URL: https://issues.apache.org/jira/browse/OFBIZ-12727 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: 22.01.01 >Reporter: Mekika Leila >Priority: Minor > Attachments: OFBIZ-12727_R22_01.patch > > > When we try to update a custRequest item, OFBiz returns the error > "Service invocation error (Could not find SimpleMethod XML document in > resource:" > To reproduce, with demo datas loaded, go to the item modification form from > request 9000 > "https://localhost:8443/ordermgr/control/requestitems?custRequestId=9000; > And try to update line 1 > The error is displayed and no modification is made. > The problem seems to come from the service definition which has been > converted to entity-auto (OFBIZ-1166) but still points to "simple" engine. > The given patch update the engine to entity-auto > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12727) Error when calling service updateCustRequestItem
[ https://issues.apache.org/jira/browse/OFBIZ-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12727: Assignee: Mekika Leila > Error when calling service updateCustRequestItem > > > Key: OFBIZ-12727 > URL: https://issues.apache.org/jira/browse/OFBIZ-12727 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: 22.01.01 >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Attachments: OFBIZ-12727_R22_01.patch > > > When we try to update a custRequest item, OFBiz returns the error > "Service invocation error (Could not find SimpleMethod XML document in > resource:" > To reproduce, with demo datas loaded, go to the item modification form from > request 9000 > "https://localhost:8443/ordermgr/control/requestitems?custRequestId=9000; > And try to update line 1 > The error is displayed and no modification is made. > The problem seems to come from the service definition which has been > converted to entity-auto (OFBIZ-1166) but still points to "simple" engine. > The given patch update the engine to entity-auto > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12727) Error when calling service updateCustRequestItem
[ https://issues.apache.org/jira/browse/OFBIZ-12727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-12727. Fix Version/s: 22.01.01 Resolution: Fixed > Error when calling service updateCustRequestItem > > > Key: OFBIZ-12727 > URL: https://issues.apache.org/jira/browse/OFBIZ-12727 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: 22.01.01 >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: 22.01.01 > > Attachments: OFBIZ-12727_R22_01.patch > > > When we try to update a custRequest item, OFBiz returns the error > "Service invocation error (Could not find SimpleMethod XML document in > resource:" > To reproduce, with demo datas loaded, go to the item modification form from > request 9000 > "https://localhost:8443/ordermgr/control/requestitems?custRequestId=9000; > And try to update line 1 > The error is displayed and no modification is made. > The problem seems to come from the service definition which has been > converted to entity-auto (OFBIZ-1166) but still points to "simple" engine. > The given patch update the engine to entity-auto > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12664: Assignee: Mekika Leila > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=9000] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
[ https://issues.apache.org/jira/browse/OFBIZ-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12664: Assignee: (was: Mekika Leila) > Automatic callback element propagation inside a modal "tunnel" process > -- > > Key: OFBIZ-12664 > URL: https://issues.apache.org/jira/browse/OFBIZ-12664 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Trivial > Attachments: OFBIZ-12664.patch, OFBIZ-12664_Example.patch > > > The callback element added by the Jira OFBIZ-11812 allows to refresh a screen > area without reloading the whole page. > However, if you want to use this mechanism in a "tunnel" process, this > parameter must be propagated manually between each form so that the final > validation and closing of the modal triggers the execution of the callback. > > The attached patch adds a propagate-callback parameter on submitButton > that will automatically propagate the callback between the forms, simplifying > the writing for the developer > For example: > A modal allowing to create an actor on the step 1 form and then allow > to attach this actor to a task in the second step. > To test, apply the Example.patch on a trunk environment (with demo > data) then go to the following page and click on the "Create" menu button to > open the first modal: > > [https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=9000] > > The validation of the second step should refresh the > WorkEffortPartyAssign list in the ListWorkEffortPartyAssigns screen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12825) Form html validation not working correctly inside a modal
[ https://issues.apache.org/jira/browse/OFBIZ-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12825: - Description: Description: When submitting a form with required fields inside a modal, the html validation does not work and form is submitted even if the required fields are empty. To reproduce: Go to the following page on a trunk environment (with demo data) and click on the "Create workeffort" menu button to open the modal: [https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK] Submit the form without filling the required fields: the form will be submitted and an error will be returned from service validation was: Description: When submitting a form with required fields inside a modal, the html validation does not work and form is submitted even if the required fields are empty. To reproduce: Go to the following page on a trunk environment (with demo data) and click on the "Create workeffort" menu button to open the modal: https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK Submit the form without filling the required fields: the form will be submitted and an error will be returned from service validation Once the corrective patch is applied (it seems to need a restart/rebuild for common-theme cache to be updated), the form validation is blocked and you should see the html error message "This field is required" > Form html validation not working correctly inside a modal > - > > Key: OFBIZ-12825 > URL: https://issues.apache.org/jira/browse/OFBIZ-12825 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > Description: When submitting a form with required fields inside a modal, the > html validation does not work and form is submitted even if the required > fields are empty. > To reproduce: > Go to the following page on a trunk environment (with demo data) and > click on the "Create workeffort" menu button to open the modal: > > [https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK] > > Submit the form without filling the required fields: the form will be > submitted and an error will be returned from service validation > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12825) Form html validation not working correctly inside a modal
Mekika Leila created OFBIZ-12825: Summary: Form html validation not working correctly inside a modal Key: OFBIZ-12825 URL: https://issues.apache.org/jira/browse/OFBIZ-12825 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Reporter: Mekika Leila Fix For: Upcoming Branch Description: When submitting a form with required fields inside a modal, the html validation does not work and form is submitted even if the required fields are empty. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12825) Form html validation not working correctly inside a modal
[ https://issues.apache.org/jira/browse/OFBIZ-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12825: - Description: Description: When submitting a form with required fields inside a modal, the html validation does not work and form is submitted even if the required fields are empty. To reproduce: Go to the following page on a trunk environment (with demo data) and click on the "Create workeffort" menu button to open the modal: https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK Submit the form without filling the required fields: the form will be submitted and an error will be returned from service validation Once the corrective patch is applied (it seems to need a restart/rebuild for common-theme cache to be updated), the form validation is blocked and you should see the html error message "This field is required" was: Description: When submitting a form with required fields inside a modal, the html validation does not work and form is submitted even if the required fields are empty. > Form html validation not working correctly inside a modal > - > > Key: OFBIZ-12825 > URL: https://issues.apache.org/jira/browse/OFBIZ-12825 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > Description: When submitting a form with required fields inside a modal, the > html validation does not work and form is submitted even if the required > fields are empty. > To reproduce: > Go to the following page on a trunk environment (with demo data) and > click on the "Create workeffort" menu button to open the modal: > > https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK > > Submit the form without filling the required fields: the form will be > submitted and an error will be returned from service validation > > Once the corrective patch is applied (it seems to need a restart/rebuild for > common-theme cache to be updated), the form validation is blocked and you > should see the html error message "This field is required" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12825) Form html validation not working correctly inside a modal
[ https://issues.apache.org/jira/browse/OFBIZ-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12825: - Attachment: OFBIZ-12825.patch > Form html validation not working correctly inside a modal > - > > Key: OFBIZ-12825 > URL: https://issues.apache.org/jira/browse/OFBIZ-12825 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-12825.patch > > > Description: When submitting a form with required fields inside a modal, the > html validation does not work and form is submitted even if the required > fields are empty. > To reproduce: > Go to the following page on a trunk environment (with demo data) and > click on the "Create workeffort" menu button to open the modal: > > https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK > > Submit the form without filling the required fields: the form will be > submitted and an error will be returned from service validation > > Once the corrective patch is applied (it seems to need a restart/rebuild for > common-theme cache to be updated), the form validation is blocked and you > should see the html error message "This field is required" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12825) Form html validation not working correctly inside a modal
[ https://issues.apache.org/jira/browse/OFBIZ-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12825: - Attachment: (was: OFBIZ-12825.patch) > Form html validation not working correctly inside a modal > - > > Key: OFBIZ-12825 > URL: https://issues.apache.org/jira/browse/OFBIZ-12825 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > Description: When submitting a form with required fields inside a modal, the > html validation does not work and form is submitted even if the required > fields are empty. > To reproduce: > Go to the following page on a trunk environment (with demo data) and > click on the "Create workeffort" menu button to open the modal: > > [https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK] > > Submit the form without filling the required fields: the form will be > submitted and an error will be returned from service validation > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12825) Form html validation not working correctly inside a modal
[ https://issues.apache.org/jira/browse/OFBIZ-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12825: Assignee: Mekika Leila > Form html validation not working correctly inside a modal > - > > Key: OFBIZ-12825 > URL: https://issues.apache.org/jira/browse/OFBIZ-12825 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-12825.patch > > > Description: When submitting a form with required fields inside a modal, the > html validation does not work and form is submitted even if the required > fields are empty. > To reproduce: > Go to the following page on a trunk environment (with demo data) and > click on the "Create workeffort" menu button to open the modal: > > [https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK] > > Submit the form without filling the required fields: the form will be > submitted and an error will be returned from service validation > > Once the corrective patch is applied (it seems to need a restart/rebuild for > common-theme cache to be updated), the form validation is blocked and you > should see the html error message "This field is required" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12825) Form html validation not working correctly inside a modal
[ https://issues.apache.org/jira/browse/OFBIZ-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12825: - Affects Version/s: Upcoming Branch > Form html validation not working correctly inside a modal > - > > Key: OFBIZ-12825 > URL: https://issues.apache.org/jira/browse/OFBIZ-12825 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-12825.patch > > > Description: When submitting a form with required fields inside a modal, the > html validation does not work and form is submitted even if the required > fields are empty. > To reproduce: > Go to the following page on a trunk environment (with demo data) and > click on the "Create workeffort" menu button to open the modal: > > [https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK] > > Submit the form without filling the required fields: the form will be > submitted and an error will be returned from service validation > > Once the corrective patch is applied (it seems to need a restart/rebuild for > common-theme cache to be updated), the form validation is blocked and you > should see the html error message "This field is required" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12825) Form html validation not working correctly inside a modal
[ https://issues.apache.org/jira/browse/OFBIZ-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-12825. Resolution: Fixed > Form html validation not working correctly inside a modal > - > > Key: OFBIZ-12825 > URL: https://issues.apache.org/jira/browse/OFBIZ-12825 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-12825.patch > > > Description: When submitting a form with required fields inside a modal, the > html validation does not work and form is submitted even if the required > fields are empty. > To reproduce: > Go to the following page on a trunk environment (with demo data) and > click on the "Create workeffort" menu button to open the modal: > > [https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK] > > Submit the form without filling the required fields: the form will be > submitted and an error will be returned from service validation > > Once the corrective patch is applied (it seems to need a restart/rebuild for > common-theme cache to be updated), the form validation is blocked and you > should see the html error message "This field is required" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12825) Form html validation not working correctly inside a modal
[ https://issues.apache.org/jira/browse/OFBIZ-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12825: - Attachment: OFBIZ-12825.patch > Form html validation not working correctly inside a modal > - > > Key: OFBIZ-12825 > URL: https://issues.apache.org/jira/browse/OFBIZ-12825 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-12825.patch > > > Description: When submitting a form with required fields inside a modal, the > html validation does not work and form is submitted even if the required > fields are empty. > To reproduce: > Go to the following page on a trunk environment (with demo data) and > click on the "Create workeffort" menu button to open the modal: > > [https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK] > > Submit the form without filling the required fields: the form will be > submitted and an error will be returned from service validation > > Once the corrective patch is applied (it seems to need a restart/rebuild for > common-theme cache to be updated), the form validation is blocked and you > should see the html error message "This field is required" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12825) Form html validation not working correctly inside a modal
[ https://issues.apache.org/jira/browse/OFBIZ-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12825: - Description: Description: When submitting a form with required fields inside a modal, the html validation does not work and form is submitted even if the required fields are empty. To reproduce: Go to the following page on a trunk environment (with demo data) and click on the "Create workeffort" menu button to open the modal: [https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK] Submit the form without filling the required fields: the form will be submitted and an error will be returned from service validation Once the corrective patch is applied (it seems to need a restart/rebuild for common-theme cache to be updated), the form validation is blocked and you should see the html error message "This field is required" was: Description: When submitting a form with required fields inside a modal, the html validation does not work and form is submitted even if the required fields are empty. To reproduce: Go to the following page on a trunk environment (with demo data) and click on the "Create workeffort" menu button to open the modal: [https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK] Submit the form without filling the required fields: the form will be submitted and an error will be returned from service validation > Form html validation not working correctly inside a modal > - > > Key: OFBIZ-12825 > URL: https://issues.apache.org/jira/browse/OFBIZ-12825 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-12825.patch > > > Description: When submitting a form with required fields inside a modal, the > html validation does not work and form is submitted even if the required > fields are empty. > To reproduce: > Go to the following page on a trunk environment (with demo data) and > click on the "Create workeffort" menu button to open the modal: > > [https://localhost:8443/workeffort/control/EditWorkEffortNotes?workEffortId=DEFAULT_TASK] > > Submit the form without filling the required fields: the form will be > submitted and an error will be returned from service validation > > Once the corrective patch is applied (it seems to need a restart/rebuild for > common-theme cache to be updated), the form validation is blocked and you > should see the html error message "This field is required" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12875) [SECURITY: CVE-2023-50968] Use screen engine for the request getJSONuilabels
[ https://issues.apache.org/jira/browse/OFBIZ-12875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817899#comment-17817899 ] Mekika Leila commented on OFBIZ-12875: -- Hello, For information I just committed an small fix for showjGrowlMessage call (undefined object error when retrieving jGrowlLabelObject) * 22.01 : [768d0780afb2e8a70acb9017a7ded9d4e72dfa30|https://github.com/apache/ofbiz-framework/commit/768d0780afb2e8a70acb9017a7ded9d4e72dfa30] * trunk : [8813c75986|https://github.com/apache/ofbiz-framework/commit/8813c75986] > [SECURITY: CVE-2023-50968] Use screen engine for the request getJSONuilabels > > > Key: OFBIZ-12875 > URL: https://issues.apache.org/jira/browse/OFBIZ-12875 > Project: OFBiz > Issue Type: Sub-task > Components: framework/common >Affects Versions: 18.12.10, 22.01 >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Major > Fix For: 22.01.01, 18.12.11 > > > Before this improvement, you can resolve a list of labels to display with the > uiLabel resource file > like : "CommonUiLabels" : ["CommonUpload", "CommonSave", > "CommonCompleted"] > > We remove the possibility to specify a uiLabel resource file and make it > work by default with CommonUiLabels. > After that we implement the json return on extend theme screen so we can > add some uiLabel ressource by theme extension or component screen definition. > > Other enhancement, on getJSONuiLabels instead resolve the label with a > list position you can call your label with it key. > resolve : uiLabelJsonObjects.CommonUiLabels[1] >become : uiLabelJsonObjects.CommonSave -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-12875) [SECURITY: CVE-2023-50968] Use screen engine for the request getJSONuilabels
[ https://issues.apache.org/jira/browse/OFBIZ-12875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817899#comment-17817899 ] Mekika Leila edited comment on OFBIZ-12875 at 2/16/24 10:04 AM: Hello, For information I have just committed a small fix for showjGrowlMessage call (undefined object error when retrieving jGrowlLabelObject) * 22.01 : [768d0780afb2e8a70acb9017a7ded9d4e72dfa30|https://github.com/apache/ofbiz-framework/commit/768d0780afb2e8a70acb9017a7ded9d4e72dfa30] * trunk : [8813c75986|https://github.com/apache/ofbiz-framework/commit/8813c75986] was (Author: mleila): Hello, For information I just committed an small fix for showjGrowlMessage call (undefined object error when retrieving jGrowlLabelObject) * 22.01 : [768d0780afb2e8a70acb9017a7ded9d4e72dfa30|https://github.com/apache/ofbiz-framework/commit/768d0780afb2e8a70acb9017a7ded9d4e72dfa30] * trunk : [8813c75986|https://github.com/apache/ofbiz-framework/commit/8813c75986] > [SECURITY: CVE-2023-50968] Use screen engine for the request getJSONuilabels > > > Key: OFBIZ-12875 > URL: https://issues.apache.org/jira/browse/OFBIZ-12875 > Project: OFBiz > Issue Type: Sub-task > Components: framework/common >Affects Versions: 18.12.10, 22.01 >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Major > Fix For: 22.01.01, 18.12.11 > > > Before this improvement, you can resolve a list of labels to display with the > uiLabel resource file > like : "CommonUiLabels" : ["CommonUpload", "CommonSave", > "CommonCompleted"] > > We remove the possibility to specify a uiLabel resource file and make it > work by default with CommonUiLabels. > After that we implement the json return on extend theme screen so we can > add some uiLabel ressource by theme extension or component screen definition. > > Other enhancement, on getJSONuiLabels instead resolve the label with a > list position you can call your label with it key. > resolve : uiLabelJsonObjects.CommonUiLabels[1] >become : uiLabelJsonObjects.CommonSave -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12869) Improve Run Service screen with dynamic fields
[ https://issues.apache.org/jira/browse/OFBIZ-12869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12869: - Description: Currently the Run Service screen in webtools displays service parameters fields as input, regardless of the paremeter required type The goal of this Jira is to display parameters dynamically (for example with a datetime picker field for a Timestamp parameter) was: *Description:* Currently the Run Service screen in webtools displays service parameters fields as input, regardless of the paremeter required type > Improve Run Service screen with dynamic fields > -- > > Key: OFBIZ-12869 > URL: https://issues.apache.org/jira/browse/OFBIZ-12869 > Project: OFBiz > Issue Type: Improvement > Components: webtools >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Minor > > Currently the Run Service screen in webtools displays service parameters > fields as input, regardless of the paremeter required type > The goal of this Jira is to display parameters dynamically (for example with > a datetime picker field for a Timestamp parameter) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12869) Improve Run Service forms with dynamic fields
[ https://issues.apache.org/jira/browse/OFBIZ-12869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12869: - Description: Currently the Run Service screen in webtools displays service parameters fields as input, regardless of the parameter type The goal of this [PR|https://github.com/apache/ofbiz-framework/pull/675] is to display parameters dynamically (for example with a datetime picker field for a Timestamp parameter) using auto-fields-service like system was: Currently the Run Service screen in webtools displays service parameters fields as input, regardless of the paremeter required type The goal of this Jira is to display parameters dynamically (for example with a datetime picker field for a Timestamp parameter) using auto-fields-service like system > Improve Run Service forms with dynamic fields > - > > Key: OFBIZ-12869 > URL: https://issues.apache.org/jira/browse/OFBIZ-12869 > Project: OFBiz > Issue Type: Improvement > Components: webtools >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Minor > > Currently the Run Service screen in webtools displays service parameters > fields as input, regardless of the parameter type > The goal of this [PR|https://github.com/apache/ofbiz-framework/pull/675] is > to display parameters dynamically (for example with a datetime picker field > for a Timestamp parameter) using auto-fields-service like system -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12869) Improve Run Service forms with dynamic fields
[ https://issues.apache.org/jira/browse/OFBIZ-12869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12869: - Description: Currently the Run Service screen in webtools displays service parameters fields as input, regardless of the paremeter required type The goal of this Jira is to display parameters dynamically (for example with a datetime picker field for a Timestamp parameter) using auto-fields-service like system was: Currently the Run Service screen in webtools displays service parameters fields as input, regardless of the paremeter required type The goal of this Jira is to display parameters dynamically (for example with a datetime picker field for a Timestamp parameter) Summary: Improve Run Service forms with dynamic fields (was: Improve Run Service screen with dynamic fields) > Improve Run Service forms with dynamic fields > - > > Key: OFBIZ-12869 > URL: https://issues.apache.org/jira/browse/OFBIZ-12869 > Project: OFBiz > Issue Type: Improvement > Components: webtools >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Minor > > Currently the Run Service screen in webtools displays service parameters > fields as input, regardless of the paremeter required type > The goal of this Jira is to display parameters dynamically (for example with > a datetime picker field for a Timestamp parameter) using auto-fields-service > like system -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12869) Improve Run Service screen with dynamic fields
Mekika Leila created OFBIZ-12869: Summary: Improve Run Service screen with dynamic fields Key: OFBIZ-12869 URL: https://issues.apache.org/jira/browse/OFBIZ-12869 Project: OFBiz Issue Type: Improvement Components: webtools Affects Versions: Upcoming Branch Reporter: Mekika Leila *Description:* Currently the Run Service screen in webtools displays service parameters fields as input, regardless of the paremeter required type -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12859) Implement placeholder attribute on textarea form widget
[ https://issues.apache.org/jira/browse/OFBIZ-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12859: Assignee: Mekika Leila > Implement placeholder attribute on textarea form widget > --- > > Key: OFBIZ-12859 > URL: https://issues.apache.org/jira/browse/OFBIZ-12859 > Project: OFBiz > Issue Type: Improvement >Affects Versions: 22.01.01, 18.12.08 >Reporter: Florian Motteau >Assignee: Mekika Leila >Priority: Minor > Attachments: image-2023-10-11-10-12-37-688.png > > > HTML textarea element supports a "placeholder" attribute : a text which is > displayed until the user starts typing characters in the textarea. > [https://developer.mozilla.org/fr/docs/Web/HTML/Element/textarea#placeholder] > !image-2023-10-11-10-12-37-688.png|width=518,height=160! > OFBiz implements a textarea form widget, which does not support this > attribute. It would be a good thing to implement this feature in OFBiz form > model. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12859) Implement placeholder attribute on textarea form widget
[ https://issues.apache.org/jira/browse/OFBIZ-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12859: - Fix Version/s: Upcoming Branch > Implement placeholder attribute on textarea form widget > --- > > Key: OFBIZ-12859 > URL: https://issues.apache.org/jira/browse/OFBIZ-12859 > Project: OFBiz > Issue Type: Improvement >Affects Versions: 22.01.01, 18.12.08 >Reporter: Florian Motteau >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > Attachments: image-2023-10-11-10-12-37-688.png > > > HTML textarea element supports a "placeholder" attribute : a text which is > displayed until the user starts typing characters in the textarea. > [https://developer.mozilla.org/fr/docs/Web/HTML/Element/textarea#placeholder] > !image-2023-10-11-10-12-37-688.png|width=518,height=160! > OFBiz implements a textarea form widget, which does not support this > attribute. It would be a good thing to implement this feature in OFBiz form > model. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12859) Implement placeholder attribute on textarea form widget
[ https://issues.apache.org/jira/browse/OFBIZ-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12859: - Component/s: ALL COMPONENTS > Implement placeholder attribute on textarea form widget > --- > > Key: OFBIZ-12859 > URL: https://issues.apache.org/jira/browse/OFBIZ-12859 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: 22.01.01, 18.12.08 >Reporter: Florian Motteau >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > Attachments: image-2023-10-11-10-12-37-688.png > > > HTML textarea element supports a "placeholder" attribute : a text which is > displayed until the user starts typing characters in the textarea. > [https://developer.mozilla.org/fr/docs/Web/HTML/Element/textarea#placeholder] > !image-2023-10-11-10-12-37-688.png|width=518,height=160! > OFBiz implements a textarea form widget, which does not support this > attribute. It would be a good thing to implement this feature in OFBiz form > model. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12859) Implement placeholder attribute on textarea form widget
[ https://issues.apache.org/jira/browse/OFBIZ-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-12859. Resolution: Fixed Thanks Florian. Your PR has been commited in trunk > Implement placeholder attribute on textarea form widget > --- > > Key: OFBIZ-12859 > URL: https://issues.apache.org/jira/browse/OFBIZ-12859 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: 22.01.01, 18.12.08 >Reporter: Florian Motteau >Assignee: Mekika Leila >Priority: Minor > Labels: pull-request-available > Fix For: Upcoming Branch > > Attachments: image-2023-10-11-10-12-37-688.png > > > HTML textarea element supports a "placeholder" attribute : a text which is > displayed until the user starts typing characters in the textarea. > [https://developer.mozilla.org/fr/docs/Web/HTML/Element/textarea#placeholder] > !image-2023-10-11-10-12-37-688.png|width=518,height=160! > OFBiz implements a textarea form widget, which does not support this > attribute. It would be a good thing to implement this feature in OFBiz form > model. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12859) Implement placeholder attribute on textarea form widget
[ https://issues.apache.org/jira/browse/OFBIZ-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12859: - Labels: pull-request-available (was: ) > Implement placeholder attribute on textarea form widget > --- > > Key: OFBIZ-12859 > URL: https://issues.apache.org/jira/browse/OFBIZ-12859 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: 22.01.01, 18.12.08 >Reporter: Florian Motteau >Assignee: Mekika Leila >Priority: Minor > Labels: pull-request-available > Fix For: Upcoming Branch > > Attachments: image-2023-10-11-10-12-37-688.png > > > HTML textarea element supports a "placeholder" attribute : a text which is > displayed until the user starts typing characters in the textarea. > [https://developer.mozilla.org/fr/docs/Web/HTML/Element/textarea#placeholder] > !image-2023-10-11-10-12-37-688.png|width=518,height=160! > OFBiz implements a textarea form widget, which does not support this > attribute. It would be a good thing to implement this feature in OFBiz form > model. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12859) Implement placeholder attribute on textarea form widget
[ https://issues.apache.org/jira/browse/OFBIZ-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787088#comment-17787088 ] Mekika Leila commented on OFBIZ-12859: -- Hello Florian, just a quick remark: when you update the parameters sent to the macro, it has impact on every call of renderTextareaField macro. So i think you should also update renderTextareaField parameters in every "XXXFormMacroLibrary.ftl" file > Implement placeholder attribute on textarea form widget > --- > > Key: OFBIZ-12859 > URL: https://issues.apache.org/jira/browse/OFBIZ-12859 > Project: OFBiz > Issue Type: Improvement >Affects Versions: 22.01.01, 18.12.08 >Reporter: Florian Motteau >Priority: Minor > Attachments: image-2023-10-11-10-12-37-688.png > > > HTML textarea element supports a "placeholder" attribute : a text which is > displayed until the user starts typing characters in the textarea. > [https://developer.mozilla.org/fr/docs/Web/HTML/Element/textarea#placeholder] > !image-2023-10-11-10-12-37-688.png|width=518,height=160! > OFBiz implements a textarea form widget, which does not support this > attribute. It would be a good thing to implement this feature in OFBiz form > model. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12869) Improve Run Service forms with dynamic fields
[ https://issues.apache.org/jira/browse/OFBIZ-12869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-12869. Fix Version/s: Upcoming Branch Resolution: Fixed > Improve Run Service forms with dynamic fields > - > > Key: OFBIZ-12869 > URL: https://issues.apache.org/jira/browse/OFBIZ-12869 > Project: OFBiz > Issue Type: Improvement > Components: webtools >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > Currently the Run Service screen in webtools displays service parameters > fields as input, regardless of the parameter type > The goal of this [PR|https://github.com/apache/ofbiz-framework/pull/675] is > to display parameters dynamically (for example with a datetime picker field > for a Timestamp parameter) using auto-fields-service like system -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12869) Improve Run Service forms with dynamic fields
[ https://issues.apache.org/jira/browse/OFBIZ-12869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12869: Assignee: Mekika Leila > Improve Run Service forms with dynamic fields > - > > Key: OFBIZ-12869 > URL: https://issues.apache.org/jira/browse/OFBIZ-12869 > Project: OFBiz > Issue Type: Improvement > Components: webtools >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > > Currently the Run Service screen in webtools displays service parameters > fields as input, regardless of the parameter type > The goal of this [PR|https://github.com/apache/ofbiz-framework/pull/675] is > to display parameters dynamically (for example with a datetime picker field > for a Timestamp parameter) using auto-fields-service like system -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
[ https://issues.apache.org/jira/browse/OFBIZ-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12994: Assignee: Mekika Leila > Convert Invoice relation screen to dynamic Compound > --- > > Key: OFBIZ-12994 > URL: https://issues.apache.org/jira/browse/OFBIZ-12994 > Project: OFBiz > Issue Type: Improvement > Components: accounting/invoice >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > > After the work on the task OFBIZ-11808, and the migration started for > workeffort screens on OFBIZ-12292, the purpose is to migrate all screen > linked to Invoice entity with idea to reduce the code and use widget > improvement developped last years > This migration cover invoice related screens from invoiceOverview to > managment screens and forms for each invoice sub item such as: > - Applications > - Attributes > - ContactMech > - Content > - Item > - Note > - Role > - Status > - Term > - TimeEntry > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-12992) Lookup Pop ups cannot be dragged to move position
[ https://issues.apache.org/jira/browse/OFBIZ-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834163#comment-17834163 ] Mekika Leila edited comment on OFBIZ-12992 at 4/5/24 8:14 AM: -- Hello [~gavinju] , [~jleroux] , [~FloMo] Is it ok for you if I commit/close this jira and attach it to OFBIZ-12276 ? [~FloMo], to answer to your question, I don't know of any other issue. But I can help resolve the ones reported by Jacques if necessary was (Author: mleila): Hello [~jleroux] , [~FloMo] Is it ok for you if I commit/close this jira and attach it to OFBIZ-12276 ? [~FloMo], to answer to your question, I don't know of any other issue. But I can help resolve the ones reported by Jacques if necessary > Lookup Pop ups cannot be dragged to move position > - > > Key: OFBIZ-12992 > URL: https://issues.apache.org/jira/browse/OFBIZ-12992 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: 22.01.01 >Reporter: gavinju >Assignee: Mekika Leila >Priority: Major > > For example，menu path is Party->Parties， and click the icon （User Login ID）, > the popup can't drag and move。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12992) Lookup Pop ups cannot be dragged to move position
[ https://issues.apache.org/jira/browse/OFBIZ-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12992: - Affects Version/s: Upcoming Branch > Lookup Pop ups cannot be dragged to move position > - > > Key: OFBIZ-12992 > URL: https://issues.apache.org/jira/browse/OFBIZ-12992 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: 22.01.01, Upcoming Branch >Reporter: gavinju >Assignee: Mekika Leila >Priority: Major > Fix For: Upcoming Branch, 22.01 > > > For example，menu path is Party->Parties， and click the icon （User Login ID）, > the popup can't drag and move。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12992) Lookup Pop ups cannot be dragged to move position
[ https://issues.apache.org/jira/browse/OFBIZ-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12992: - Fix Version/s: Upcoming Branch 22.01 > Lookup Pop ups cannot be dragged to move position > - > > Key: OFBIZ-12992 > URL: https://issues.apache.org/jira/browse/OFBIZ-12992 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: 22.01.01 >Reporter: gavinju >Assignee: Mekika Leila >Priority: Major > Fix For: Upcoming Branch, 22.01 > > > For example，menu path is Party->Parties， and click the icon （User Login ID）, > the popup can't drag and move。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12992) Lookup Pop ups cannot be dragged to move position
[ https://issues.apache.org/jira/browse/OFBIZ-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834163#comment-17834163 ] Mekika Leila commented on OFBIZ-12992: -- Hello [~jleroux] , [~FloMo] Is it ok for you if I commit/close this jira and attach it to OFBIZ-12276 ? [~FloMo], to answer to your question, I don't know of any other issue. But I can help resolve the ones reported by Jacques if necessary > Lookup Pop ups cannot be dragged to move position > - > > Key: OFBIZ-12992 > URL: https://issues.apache.org/jira/browse/OFBIZ-12992 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: 22.01.01 >Reporter: gavinju >Assignee: Mekika Leila >Priority: Major > > For example，menu path is Party->Parties， and click the icon （User Login ID）, > the popup can't drag and move。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12992) Lookup Pop ups cannot be dragged to move position
[ https://issues.apache.org/jira/browse/OFBIZ-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-12992. Resolution: Fixed > Lookup Pop ups cannot be dragged to move position > - > > Key: OFBIZ-12992 > URL: https://issues.apache.org/jira/browse/OFBIZ-12992 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: 22.01.01, Upcoming Branch >Reporter: gavinju >Assignee: Mekika Leila >Priority: Major > Fix For: Upcoming Branch, 22.01 > > > For example，menu path is Party->Parties， and click the icon （User Login ID）, > the popup can't drag and move。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12963) Fix problems with Eclipse about multi module dependencies.
[ https://issues.apache.org/jira/browse/OFBIZ-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12963: Assignee: Mekika Leila > Fix problems with Eclipse about multi module dependencies. > -- > > Key: OFBIZ-12963 > URL: https://issues.apache.org/jira/browse/OFBIZ-12963 > Project: OFBiz > Issue Type: Bug >Affects Versions: Upcoming Branch >Reporter: Gil Portenseigne >Assignee: Mekika Leila >Priority: Minor > Attachments: OFBIZ-12963.patch > > > On my journey to come back using Eclipse, i got some issues when loading > trunk : > The package xxx is accessible from more than one module. > This kind of issue appear when a project bring a dependency that is already > in another module in OFBiz > The patch avoid loading 'pull-parser' and 'xpp3' dependencies that are > already present in jdk17. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12963) Fix problems with Eclipse about multi module dependencies.
[ https://issues.apache.org/jira/browse/OFBIZ-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830926#comment-17830926 ] Mekika Leila commented on OFBIZ-12963: -- Hello, Tested on trunk with openjdk version "17.0.10": only one problem remains but it is not linked to the "The package xxx is accessible from more than one module." error Thanks Gil > Fix problems with Eclipse about multi module dependencies. > -- > > Key: OFBIZ-12963 > URL: https://issues.apache.org/jira/browse/OFBIZ-12963 > Project: OFBiz > Issue Type: Bug >Affects Versions: Upcoming Branch >Reporter: Gil Portenseigne >Assignee: Mekika Leila >Priority: Minor > Attachments: OFBIZ-12963.patch > > > On my journey to come back using Eclipse, i got some issues when loading > trunk : > The package xxx is accessible from more than one module. > This kind of issue appear when a project bring a dependency that is already > in another module in OFBiz > The patch avoid loading 'pull-parser' and 'xpp3' dependencies that are > already present in jdk17. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12963) Fix problems with Eclipse about multi module dependencies.
[ https://issues.apache.org/jira/browse/OFBIZ-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-12963. Fix Version/s: Upcoming Branch Resolution: Fixed > Fix problems with Eclipse about multi module dependencies. > -- > > Key: OFBIZ-12963 > URL: https://issues.apache.org/jira/browse/OFBIZ-12963 > Project: OFBiz > Issue Type: Bug >Affects Versions: Upcoming Branch >Reporter: Gil Portenseigne >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-12963.patch > > > On my journey to come back using Eclipse, i got some issues when loading > trunk : > The package xxx is accessible from more than one module. > This kind of issue appear when a project bring a dependency that is already > in another module in OFBiz > The patch avoid loading 'pull-parser' and 'xpp3' dependencies that are > already present in jdk17. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
Mekika Leila created OFBIZ-12994: Summary: Convert Invoice relation screen to dynamic Compound Key: OFBIZ-12994 URL: https://issues.apache.org/jira/browse/OFBIZ-12994 Project: OFBiz Issue Type: Improvement Components: accounting/invoice Affects Versions: Upcoming Branch Reporter: Mekika Leila After the work on the task OFBIZ-11808, and the migration started for workeffort screens on OFBIZ-12292, the purpose is to migrate all screen linked to Invoice entity with idea to reduce the code and use widget improvement developped last years This migration cover invoice related screens from invoiceOverview to managment screens and forms for each invoice sub item such as: - Applications - Attributes - ContactMech - Content - Item - Note - Role - Status - Term - TimeEntry -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
[ https://issues.apache.org/jira/browse/OFBIZ-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834015#comment-17834015 ] Mekika Leila commented on OFBIZ-12994: -- PR: [https://github.com/apache/ofbiz-framework/pull/746|https://github.com/apache/ofbiz-framework/pull/746] > Convert Invoice relation screen to dynamic Compound > --- > > Key: OFBIZ-12994 > URL: https://issues.apache.org/jira/browse/OFBIZ-12994 > Project: OFBiz > Issue Type: Improvement > Components: accounting/invoice >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Minor > > After the work on the task OFBIZ-11808, and the migration started for > workeffort screens on OFBIZ-12292, the purpose is to migrate all screen > linked to Invoice entity with idea to reduce the code and use widget > improvement developped last years > This migration cover invoice related screens from invoiceOverview to > managment screens and forms for each invoice sub item such as: > - Applications > - Attributes > - ContactMech > - Content > - Item > - Note > - Role > - Status > - Term > - TimeEntry > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
[ https://issues.apache.org/jira/browse/OFBIZ-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12994: - Description: After the work on the task OFBIZ-11808, and the migration started for workeffort screens on OFBIZ-12292, the purpose is to migrate all screen linked to Invoice entity with idea to reduce the code and use widget improvement developped last years This migration cover invoice related screens from invoiceOverview to managment screens and forms for each invoice sub item such as: - Applications - Attributes - ContactMech - Content - Item - Note - Role - Status - Term - TimeEntry was: After the work on the task OFBIZ-11808, and the migration started for workeffort screens on OFBIZ-12292, the purpose is to migrate all screen linked to Invoice entity with idea to reduce the code and use widget improvement developped last years This migration cover invoice related screens from invoiceOverview to managment screens and forms for each invoice sub item such as: - Applications - Attributes - ContactMech - Content - Item - Note - Role - Status - Term - TimeEntry > Convert Invoice relation screen to dynamic Compound > --- > > Key: OFBIZ-12994 > URL: https://issues.apache.org/jira/browse/OFBIZ-12994 > Project: OFBiz > Issue Type: Improvement > Components: accounting/invoice >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Minor > > After the work on the task OFBIZ-11808, and the migration started for > workeffort screens on OFBIZ-12292, the purpose is to migrate all screen > linked to Invoice entity with idea to reduce the code and use widget > improvement developped last years > This migration cover invoice related screens from invoiceOverview to > managment screens and forms for each invoice sub item such as: > - Applications > - Attributes > - ContactMech > - Content > - Item > - Note > - Role > - Status > - Term > - TimeEntry > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-12992) Lookup Pop ups cannot be dragged to move position
[ https://issues.apache.org/jira/browse/OFBIZ-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-12992: Assignee: Mekika Leila > Lookup Pop ups cannot be dragged to move position > - > > Key: OFBIZ-12992 > URL: https://issues.apache.org/jira/browse/OFBIZ-12992 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: 22.01.01 >Reporter: gavinju >Assignee: Mekika Leila >Priority: Major > > For example，menu path is Party->Parties， and click the icon （User Login ID）, > the popup can't drag and move。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13017) invoiceOverview generates an error
[ https://issues.apache.org/jira/browse/OFBIZ-13017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838031#comment-17838031 ] Mekika Leila commented on OFBIZ-13017: -- Hello [~jleroux] and [~pierresmits], [~pierresmits] about your remarks, I also think that there is something that can be done with the menus but I didn't find the way to move it without impacting the AR/AP component (I didn't know then that they were to be remove) For the uri, it was my first thought to create new controller requests for 'entry point' but it would mean that we will have to keep both versions of the "same" screens and forms, so there was no more 'code reducing'. The goal was also to be transparent for the users (if you checkout the trunk at commit 'c7333c0c93940a8bfeaab78e282a447755be8ab8' you will see that the screens remained as close as possible as the previous ones. So are the controller request) If you both agree, I think the discussion can be pursued on jira OFBIZ-12994 instead of this one. For the current invoiceOverview screen error, I propose to work on a PR to resolve the conflicts between the three jiras. Tell me if you are interested > invoiceOverview generates an error > -- > > Key: OFBIZ-13017 > URL: https://issues.apache.org/jira/browse/OFBIZ-13017 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Pierre Smits >Priority: Major > > see > https://demo-trunk.ofbiz.apache.org/accounting/control/invoiceOverview?invoiceId=demo10001 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13017) invoiceOverview generates an error
[ https://issues.apache.org/jira/browse/OFBIZ-13017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838626#comment-17838626 ] Mekika Leila commented on OFBIZ-13017: -- Thanks Jacques > invoiceOverview generates an error > -- > > Key: OFBIZ-13017 > URL: https://issues.apache.org/jira/browse/OFBIZ-13017 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Pierre Smits >Priority: Major > > see > https://demo-trunk.ofbiz.apache.org/accounting/control/invoiceOverview?invoiceId=demo10001 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
[ https://issues.apache.org/jira/browse/OFBIZ-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839549#comment-17839549 ] Mekika Leila commented on OFBIZ-12994: -- PR: https://github.com/apache/ofbiz-framework/pull/780 Update fix to combine OFBIZ-12966 and OFBIZ-13011 updates with modifications brought by jira OFBIZ-12994 It brings back the changes introduced by OFBIZ-12994 and adapt it with the change of invoiceOverview screen name > Convert Invoice relation screen to dynamic Compound > --- > > Key: OFBIZ-12994 > URL: https://issues.apache.org/jira/browse/OFBIZ-12994 > Project: OFBiz > Issue Type: Improvement > Components: accounting/invoice >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > After the work on the task OFBIZ-11808, and the migration started for > workeffort screens on OFBIZ-12292, the purpose is to migrate all screen > linked to Invoice entity with idea to reduce the code and use widget > improvement developped last years > This migration cover invoice related screens from invoiceOverview to > managment screens and forms for each invoice sub item such as: > - Applications > - Attributes > - ContactMech > - Content > - Item > - Note > - Role > - Status > - Term > - TimeEntry > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13017) invoiceOverview generates an error
[ https://issues.apache.org/jira/browse/OFBIZ-13017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837558#comment-17837558 ] Mekika Leila commented on OFBIZ-13017: -- Thank you for the alert: I check to fix the issue > invoiceOverview generates an error > -- > > Key: OFBIZ-13017 > URL: https://issues.apache.org/jira/browse/OFBIZ-13017 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Pierre Smits >Priority: Major > > see > https://demo-trunk.ofbiz.apache.org/accounting/control/invoiceOverview?invoiceId=demo10001 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
[ https://issues.apache.org/jira/browse/OFBIZ-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837598#comment-17837598 ] Mekika Leila commented on OFBIZ-12994: -- Hello [~jleroux] and [~pierresmits] After a double check, it seems that the two commits for (OFBIZ-12966) and (OFBIZ-13011) reverted changes from OFBIZ-12994. That's why the invoiceOverview is now broken. > Convert Invoice relation screen to dynamic Compound > --- > > Key: OFBIZ-12994 > URL: https://issues.apache.org/jira/browse/OFBIZ-12994 > Project: OFBiz > Issue Type: Improvement > Components: accounting/invoice >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > After the work on the task OFBIZ-11808, and the migration started for > workeffort screens on OFBIZ-12292, the purpose is to migrate all screen > linked to Invoice entity with idea to reduce the code and use widget > improvement developped last years > This migration cover invoice related screens from invoiceOverview to > managment screens and forms for each invoice sub item such as: > - Applications > - Attributes > - ContactMech > - Content > - Item > - Note > - Role > - Status > - Term > - TimeEntry > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13072) Issue when caching a query with a selectField
Mekika Leila created OFBIZ-13072: Summary: Issue when caching a query with a selectField Key: OFBIZ-13072 URL: https://issues.apache.org/jira/browse/OFBIZ-13072 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Upcoming Branch Reporter: Mekika Leila When a query with a field selection and a cache() option is done, the result is put in cache with the incomplete genericValue (I mean without all the fields). Then when an other query with the same condition and cache option is done, even whitout the field selection, the result returned is the incomplete version of the GenericValue that has been stored in cache. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13072) Issue when caching a query with a selectField
[ https://issues.apache.org/jira/browse/OFBIZ-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-13072: - Description: When a query with a field selection and a cache() option is done, the result is put in cache with the incomplete genericValue (I mean without all the fields). Then when an other query with the same condition and cache option is done, even whitout the field selection, the result returned is the incomplete version of the GenericValue that has been stored in cache. The code in the PR prevent from adding in cache an incomplete genericValue and filter the cached value when necessary *To test:* testCache has been added to entity-query-tests test case. It can be launched with ./gradlew 'ofbiz -t component=entity' or ./gradlew 'ofbiz -t component=entity -t suitename=entitytests -t case=entity-query-tests' was: When a query with a field selection and a cache() option is done, the result is put in cache with the incomplete genericValue (I mean without all the fields). Then when an other query with the same condition and cache option is done, even whitout the field selection, the result returned is the incomplete version of the GenericValue that has been stored in cache. > Issue when caching a query with a selectField > - > > Key: OFBIZ-13072 > URL: https://issues.apache.org/jira/browse/OFBIZ-13072 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Minor > > When a query with a field selection and a cache() option is done, the result > is put in cache with the incomplete genericValue (I mean without all the > fields). > Then when an other query with the same condition and cache option is done, > even whitout the field selection, the result returned is the incomplete > version of the GenericValue that has been stored in cache. > The code in the PR prevent from adding in cache an incomplete genericValue > and filter the cached value when necessary > *To test:* > testCache has been added to entity-query-tests test case. It can be launched > with > ./gradlew 'ofbiz -t component=entity' > or > ./gradlew 'ofbiz -t component=entity -t suitename=entitytests -t > case=entity-query-tests' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13072) Issue when caching a query with a selectField
[ https://issues.apache.org/jira/browse/OFBIZ-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-13072: - Description: When a query with a field selection and a cache() option is done, the result is put in cache with the incomplete genericValue (I mean without all the fields). Then when an other query with the same condition and cache option is done, even whitout the field selection, the result returned is the incomplete version of the GenericValue that has been stored in cache. was: When a query with a field selection and a cache() option is done, the result is put in cache with the incomplete genericValue (I mean without all the fields). Then when an other query with the same condition and cache option is done, even whitout the field selection, the result returned is the incomplete version of the GenericValue that has been stored in cache. > Issue when caching a query with a selectField > - > > Key: OFBIZ-13072 > URL: https://issues.apache.org/jira/browse/OFBIZ-13072 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Minor > > When a query with a field selection and a cache() option is done, the result > is put in cache with the incomplete genericValue (I mean without all the > fields). > Then when an other query with the same condition and cache option is done, > even whitout the field selection, the result returned is the incomplete > version of the GenericValue that has been stored in cache. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
[ https://issues.apache.org/jira/browse/OFBIZ-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840690#comment-17840690 ] Mekika Leila commented on OFBIZ-12994: -- To pursue discussion started on JIRA-1307, a quick link to the thread: https://issues.apache.org/jira/browse/OFBIZ-13017#comment-17837631 https://issues.apache.org/jira/browse/OFBIZ-13017#comment-17838031 > Convert Invoice relation screen to dynamic Compound > --- > > Key: OFBIZ-12994 > URL: https://issues.apache.org/jira/browse/OFBIZ-12994 > Project: OFBiz > Issue Type: Improvement > Components: accounting/invoice >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > After the work on the task OFBIZ-11808, and the migration started for > workeffort screens on OFBIZ-12292, the purpose is to migrate all screen > linked to Invoice entity with idea to reduce the code and use widget > improvement developped last years > This migration cover invoice related screens from invoiceOverview to > managment screens and forms for each invoice sub item such as: > - Applications > - Attributes > - ContactMech > - Content > - Item > - Note > - Role > - Status > - Term > - TimeEntry > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12992) Lookup Pop ups cannot be dragged to move position
[ https://issues.apache.org/jira/browse/OFBIZ-12992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-12992: - Parent: OFBIZ-12276 Issue Type: Sub-task (was: Bug) > Lookup Pop ups cannot be dragged to move position > - > > Key: OFBIZ-12992 > URL: https://issues.apache.org/jira/browse/OFBIZ-12992 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: 22.01.01, Upcoming Branch >Reporter: gavinju >Assignee: Mekika Leila >Priority: Major > Fix For: Upcoming Branch, 22.01 > > > For example，menu path is Party->Parties， and click the icon （User Login ID）, > the popup can't drag and move。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12918) Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836105#comment-17836105 ] Mekika Leila commented on OFBIZ-12918: -- Hello Pierre, Jacques, I just saw that the declaration of mainMenuLocation in AR/AP web/xml seems to be missing (you can see it on the trunk demo: https://demo-trunk.ofbiz.apache.org/ar/control/invoiceOverview?invoiceId=demo1200 ) > Move from hard-code menu location to parameterized > -- > > Key: OFBIZ-12918 > URL: https://issues.apache.org/jira/browse/OFBIZ-12918 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
[ https://issues.apache.org/jira/browse/OFBIZ-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-12994. Fix Version/s: Upcoming Branch Resolution: Implemented > Convert Invoice relation screen to dynamic Compound > --- > > Key: OFBIZ-12994 > URL: https://issues.apache.org/jira/browse/OFBIZ-12994 > Project: OFBiz > Issue Type: Improvement > Components: accounting/invoice >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > After the work on the task OFBIZ-11808, and the migration started for > workeffort screens on OFBIZ-12292, the purpose is to migrate all screen > linked to Invoice entity with idea to reduce the code and use widget > improvement developped last years > This migration cover invoice related screens from invoiceOverview to > managment screens and forms for each invoice sub item such as: > - Applications > - Attributes > - ContactMech > - Content > - Item > - Note > - Role > - Status > - Term > - TimeEntry > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12918) Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836144#comment-17836144 ] Mekika Leila commented on OFBIZ-12918: -- Thank you Pierre for the explanation: Indeed, I was not aware of the discussion nor the jira [OFBIZ-10552|https://issues.apache.org/jira/browse/OFBIZ-10552] I was warning you because I notice the broken screen when doing tests for my last Jira. I propose to add it just to repair the screen during the time that Jiras [OFBIZ-10552|https://issues.apache.org/jira/browse/OFBIZ-10552] and [OFBIZ-12966|https://issues.apache.org/jira/browse/OFBIZ-12966] are managed. Is it ok for you ? > Move from hard-code menu location to parameterized > -- > > Key: OFBIZ-12918 > URL: https://issues.apache.org/jira/browse/OFBIZ-12918 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13017) invoiceOverview generates an error
[ https://issues.apache.org/jira/browse/OFBIZ-13017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838514#comment-17838514 ] Mekika Leila commented on OFBIZ-13017: -- Hello [~jleroux], Sorry, I was talking about pursuing the discussion about the suggestions made by Pierre on OFBIZ-12994. I think corrections about the revert and broken invoiceOverview can still be made in this jira. Do you agree ? > invoiceOverview generates an error > -- > > Key: OFBIZ-13017 > URL: https://issues.apache.org/jira/browse/OFBIZ-13017 > Project: OFBiz > Issue Type: Bug > Components: accounting >Reporter: Pierre Smits >Priority: Major > > see > https://demo-trunk.ofbiz.apache.org/accounting/control/invoiceOverview?invoiceId=demo10001 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13072) Issue when caching a query with a selectField
[ https://issues.apache.org/jira/browse/OFBIZ-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-13072: - Fix Version/s: Upcoming Branch > Issue when caching a query with a selectField > - > > Key: OFBIZ-13072 > URL: https://issues.apache.org/jira/browse/OFBIZ-13072 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > When a query with a field selection and a cache() option is done, the result > is put in cache with the incomplete genericValue (I mean without all the > fields). > Then when an other query with the same condition and cache option is done, > even whitout the field selection, the result returned is the incomplete > version of the GenericValue that has been stored in cache. > The code in the PR prevent from adding in cache an incomplete genericValue > and filter the cached value when necessary > *To test:* > testCache has been added to entity-query-tests test case. It can be launched > with > ./gradlew 'ofbiz -t component=entity' > or > ./gradlew 'ofbiz -t component=entity -t suitename=entitytests -t > case=entity-query-tests' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-13072) Issue when caching a query with a selectField
[ https://issues.apache.org/jira/browse/OFBIZ-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-13072. Resolution: Fixed > Issue when caching a query with a selectField > - > > Key: OFBIZ-13072 > URL: https://issues.apache.org/jira/browse/OFBIZ-13072 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > > When a query with a field selection and a cache() option is done, the result > is put in cache with the incomplete genericValue (I mean without all the > fields). > Then when an other query with the same condition and cache option is done, > even whitout the field selection, the result returned is the incomplete > version of the GenericValue that has been stored in cache. > The code in the PR prevent from adding in cache an incomplete genericValue > and filter the cached value when necessary > *To test:* > testCache has been added to entity-query-tests test case. It can be launched > with > ./gradlew 'ofbiz -t component=entity' > or > ./gradlew 'ofbiz -t component=entity -t suitename=entitytests -t > case=entity-query-tests' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-13072) Issue when caching a query with a selectField
[ https://issues.apache.org/jira/browse/OFBIZ-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-13072: Assignee: Mekika Leila > Issue when caching a query with a selectField > - > > Key: OFBIZ-13072 > URL: https://issues.apache.org/jira/browse/OFBIZ-13072 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > > When a query with a field selection and a cache() option is done, the result > is put in cache with the incomplete genericValue (I mean without all the > fields). > Then when an other query with the same condition and cache option is done, > even whitout the field selection, the result returned is the incomplete > version of the GenericValue that has been stored in cache. > The code in the PR prevent from adding in cache an incomplete genericValue > and filter the cached value when necessary > *To test:* > testCache has been added to entity-query-tests test case. It can be launched > with > ./gradlew 'ofbiz -t component=entity' > or > ./gradlew 'ofbiz -t component=entity -t suitename=entitytests -t > case=entity-query-tests' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13072) Issue when caching a query with a selectField
[ https://issues.apache.org/jira/browse/OFBIZ-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842857#comment-17842857 ] Mekika Leila commented on OFBIZ-13072: -- Thanks for the review Jacques ! > Issue when caching a query with a selectField > - > > Key: OFBIZ-13072 > URL: https://issues.apache.org/jira/browse/OFBIZ-13072 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Minor > > When a query with a field selection and a cache() option is done, the result > is put in cache with the incomplete genericValue (I mean without all the > fields). > Then when an other query with the same condition and cache option is done, > even whitout the field selection, the result returned is the incomplete > version of the GenericValue that has been stored in cache. > The code in the PR prevent from adding in cache an incomplete genericValue > and filter the cached value when necessary > *To test:* > testCache has been added to entity-query-tests test case. It can be launched > with > ./gradlew 'ofbiz -t component=entity' > or > ./gradlew 'ofbiz -t component=entity -t suitename=entitytests -t > case=entity-query-tests' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13077) Error when calling EntityQuery.from() with a dynamicView via groovy DSL
Mekika Leila created OFBIZ-13077: Summary: Error when calling EntityQuery.from() with a dynamicView via groovy DSL Key: OFBIZ-13077 URL: https://issues.apache.org/jira/browse/OFBIZ-13077 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: Upcoming Branch Reporter: Mekika Leila There is a "No signature of method " error when executing the script FindInventoryItemsByLabels.groovy which use Groovy DSL syntax to call method EntityQuery.from(DynamicViewEntity dve) This is due to the fact that the from() DSL is currently only defined for calling the method with an entityName String. The purpose of this Jira is to add the Groovy DSL for EntityQuery.from(DynamicViewEntity dve) so the FindInventoryItemsByLabels will not fail and the dsl will be extended for other scripts *To reproduce* In a trunk ofbiz with demo data loaded, load file attached and go to [SearchInventoryItemsByLabels page|[https://localhost:8443/facility/control/SearchInventoryItemsByLabels?facilityId=WebStoreWarehouse]]. Then select 'Label test' and submit the search form -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13077) Error when calling EntityQuery.from() with a dynamicView via groovy DSL
[ https://issues.apache.org/jira/browse/OFBIZ-13077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-13077: - Attachment: DemoDataOFBIZ-13077.xml > Error when calling EntityQuery.from() with a dynamicView via groovy DSL > --- > > Key: OFBIZ-13077 > URL: https://issues.apache.org/jira/browse/OFBIZ-13077 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Priority: Minor > Attachments: DemoDataOFBIZ-13077.xml > > > There is a "No signature of method " error when executing the script > FindInventoryItemsByLabels.groovy which use Groovy DSL syntax to call method > EntityQuery.from(DynamicViewEntity dve) > This is due to the fact that the from() DSL is currently only defined for > calling the method with an entityName String. > The purpose of this Jira is to add the Groovy DSL for > EntityQuery.from(DynamicViewEntity dve) so the FindInventoryItemsByLabels > will not fail and the dsl will be extended for other scripts > *To reproduce* > In a trunk ofbiz with demo data loaded, load file attached and go to > [SearchInventoryItemsByLabels > page|[https://localhost:8443/facility/control/SearchInventoryItemsByLabels?facilityId=WebStoreWarehouse]]. > > Then select 'Label test' and submit the search form -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
[ https://issues.apache.org/jira/browse/OFBIZ-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844175#comment-17844175 ] Mekika Leila commented on OFBIZ-12994: -- Hello [~jleroux] , For me there is no longer any issues also. For Pierre points, I agree with 1 and 3. For the three others it was on volontary so I am not sure. > Convert Invoice relation screen to dynamic Compound > --- > > Key: OFBIZ-12994 > URL: https://issues.apache.org/jira/browse/OFBIZ-12994 > Project: OFBiz > Issue Type: Improvement > Components: accounting/invoice >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > After the work on the task OFBIZ-11808, and the migration started for > workeffort screens on OFBIZ-12292, the purpose is to migrate all screen > linked to Invoice entity with idea to reduce the code and use widget > improvement developped last years > This migration cover invoice related screens from invoiceOverview to > managment screens and forms for each invoice sub item such as: > - Applications > - Attributes > - ContactMech > - Content > - Item > - Note > - Role > - Status > - Term > - TimeEntry > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
[ https://issues.apache.org/jira/browse/OFBIZ-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844175#comment-17844175 ] Mekika Leila edited comment on OFBIZ-12994 at 5/7/24 7:48 AM: -- Hello [~jleroux] , For me there is no longer any issues also. For Pierre points, I agree with 1 and 3. For the three others it was on purpose so I am not sure. was (Author: mleila): Hello [~jleroux] , For me there is no longer any issues also. For Pierre points, I agree with 1 and 3. For the three others it was on volontary so I am not sure. > Convert Invoice relation screen to dynamic Compound > --- > > Key: OFBIZ-12994 > URL: https://issues.apache.org/jira/browse/OFBIZ-12994 > Project: OFBiz > Issue Type: Improvement > Components: accounting/invoice >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > After the work on the task OFBIZ-11808, and the migration started for > workeffort screens on OFBIZ-12292, the purpose is to migrate all screen > linked to Invoice entity with idea to reduce the code and use widget > improvement developped last years > This migration cover invoice related screens from invoiceOverview to > managment screens and forms for each invoice sub item such as: > - Applications > - Attributes > - ContactMech > - Content > - Item > - Note > - Role > - Status > - Term > - TimeEntry > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
[ https://issues.apache.org/jira/browse/OFBIZ-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-12994. Resolution: Fixed > Convert Invoice relation screen to dynamic Compound > --- > > Key: OFBIZ-12994 > URL: https://issues.apache.org/jira/browse/OFBIZ-12994 > Project: OFBiz > Issue Type: Improvement > Components: accounting/invoice >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > After the work on the task OFBIZ-11808, and the migration started for > workeffort screens on OFBIZ-12292, the purpose is to migrate all screen > linked to Invoice entity with idea to reduce the code and use widget > improvement developped last years > This migration cover invoice related screens from invoiceOverview to > managment screens and forms for each invoice sub item such as: > - Applications > - Attributes > - ContactMech > - Content > - Item > - Note > - Role > - Status > - Term > - TimeEntry > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-13077) Error when calling EntityQuery.from() with a dynamicView via groovy DSL
[ https://issues.apache.org/jira/browse/OFBIZ-13077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila reassigned OFBIZ-13077: Assignee: Mekika Leila > Error when calling EntityQuery.from() with a dynamicView via groovy DSL > --- > > Key: OFBIZ-13077 > URL: https://issues.apache.org/jira/browse/OFBIZ-13077 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Attachments: DemoDataOFBIZ-13077.xml > > > There is a "No signature of method " error when executing the script > FindInventoryItemsByLabels.groovy which use Groovy DSL syntax to call method > EntityQuery.from(DynamicViewEntity dve) > This is due to the fact that the from() DSL is currently only defined for > calling the method with an entityName String. > The purpose of this Jira is to add the Groovy DSL for > EntityQuery.from(DynamicViewEntity dve) so the FindInventoryItemsByLabels > will not fail and the dsl will be extended for other scripts > *To reproduce* > In a trunk ofbiz with demo data loaded, load file attached and go to > [SearchInventoryItemsByLabels > page|[https://localhost:8443/facility/control/SearchInventoryItemsByLabels?facilityId=WebStoreWarehouse]]. > > Then select 'Label test' and submit the search form -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12994) Convert Invoice relation screen to dynamic Compound
[ https://issues.apache.org/jira/browse/OFBIZ-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845997#comment-17845997 ] Mekika Leila commented on OFBIZ-12994: -- Ok, Thank you Jacques. I close the jira > Convert Invoice relation screen to dynamic Compound > --- > > Key: OFBIZ-12994 > URL: https://issues.apache.org/jira/browse/OFBIZ-12994 > Project: OFBiz > Issue Type: Improvement > Components: accounting/invoice >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > > After the work on the task OFBIZ-11808, and the migration started for > workeffort screens on OFBIZ-12292, the purpose is to migrate all screen > linked to Invoice entity with idea to reduce the code and use widget > improvement developped last years > This migration cover invoice related screens from invoiceOverview to > managment screens and forms for each invoice sub item such as: > - Applications > - Attributes > - ContactMech > - Content > - Item > - Note > - Role > - Status > - Term > - TimeEntry > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13077) Error when calling EntityQuery.from() with a dynamicView via groovy DSL
[ https://issues.apache.org/jira/browse/OFBIZ-13077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila updated OFBIZ-13077: - Fix Version/s: Upcoming Branch > Error when calling EntityQuery.from() with a dynamicView via groovy DSL > --- > > Key: OFBIZ-13077 > URL: https://issues.apache.org/jira/browse/OFBIZ-13077 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > Attachments: DemoDataOFBIZ-13077.xml > > > There is a "No signature of method " error when executing the script > FindInventoryItemsByLabels.groovy which use Groovy DSL syntax to call method > EntityQuery.from(DynamicViewEntity dve) > This is due to the fact that the from() DSL is currently only defined for > calling the method with an entityName String. > The purpose of this Jira is to add the Groovy DSL for > EntityQuery.from(DynamicViewEntity dve) so the FindInventoryItemsByLabels > will not fail and the dsl will be extended for other scripts > *To reproduce* > In a trunk ofbiz with demo data loaded, load file attached and go to > [SearchInventoryItemsByLabels > page|[https://localhost:8443/facility/control/SearchInventoryItemsByLabels?facilityId=WebStoreWarehouse]]. > > Then select 'Label test' and submit the search form -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-13077) Error when calling EntityQuery.from() with a dynamicView via groovy DSL
[ https://issues.apache.org/jira/browse/OFBIZ-13077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mekika Leila closed OFBIZ-13077. Resolution: Fixed > Error when calling EntityQuery.from() with a dynamicView via groovy DSL > --- > > Key: OFBIZ-13077 > URL: https://issues.apache.org/jira/browse/OFBIZ-13077 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Mekika Leila >Assignee: Mekika Leila >Priority: Minor > Fix For: Upcoming Branch > > Attachments: DemoDataOFBIZ-13077.xml > > > There is a "No signature of method " error when executing the script > FindInventoryItemsByLabels.groovy which use Groovy DSL syntax to call method > EntityQuery.from(DynamicViewEntity dve) > This is due to the fact that the from() DSL is currently only defined for > calling the method with an entityName String. > The purpose of this Jira is to add the Groovy DSL for > EntityQuery.from(DynamicViewEntity dve) so the FindInventoryItemsByLabels > will not fail and the dsl will be extended for other scripts > *To reproduce* > In a trunk ofbiz with demo data loaded, load file attached and go to > [SearchInventoryItemsByLabels > page|[https://localhost:8443/facility/control/SearchInventoryItemsByLabels?facilityId=WebStoreWarehouse]]. > > Then select 'Label test' and submit the search form -- This message was sent by Atlassian Jira (v8.20.10#820010)
