[jira] [Commented] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
[ https://issues.apache.org/jira/browse/OFBIZ-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598463#comment-17598463 ] Leila Mekika commented on OFBIZ-12684: -- Ok [~jleroux] sorry I didn' see your last reply :) > Add auto-parameters-form option to on-event-update-area link in xml form > > > Key: OFBIZ-12684 > URL: https://issues.apache.org/jira/browse/OFBIZ-12684 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: Image 002.png, Image3.png, OFBIZ-12684.patch, > OFBIZ-12684_Example.patch, auto-parameters-form.png, > image-2022-08-31-15-27-40-474.png > > > As we have an auto-parameters-entity and an auto-parameters-service option in > xml forms on-event-update-area tags, it could be useful to have an > auto-parameters-form option that will propagate current form fields as > parameters to the paginate or submit action link (for instance in modal > "tunnel" processes) > > Currently, if you want to propagate the parameters of a form to a zone > that is refreshed in ajax after the submit you have to write specific > javascript code or to return all the parameters sent to the request through a > service as OUT parameters and/or redirect-parameter. > This feature will add automatically the form parameters on the generated > on-event-update-area link > To test, apply the OFBIZ_12684_Example.patch on a trunk environment (with > demo data) then go to the following page and click on the "edit" button on > line Web Store Warehouse: > https://localhost:8443/catalog/control/ProductStoreFacilities?productStoreId=9000 > The validation of the edition form should refresh correctly the list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
[ https://issues.apache.org/jira/browse/OFBIZ-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598462#comment-17598462 ] Leila Mekika commented on OFBIZ-12684: -- I also use the xml catalog feature so I don't know if this is linked... But when a make a ctrl+clic over on-event-update-area, I got a link to a xsd file in cache (/home//.lemminx/cache/http/ofbiz.apache.org/dtds/ ). When I open this file, I see the auto-parameters-form . Maybe yours is not up to date ? > Add auto-parameters-form option to on-event-update-area link in xml form > > > Key: OFBIZ-12684 > URL: https://issues.apache.org/jira/browse/OFBIZ-12684 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: Image 002.png, Image3.png, OFBIZ-12684.patch, > OFBIZ-12684_Example.patch, auto-parameters-form.png, > image-2022-08-31-15-27-40-474.png > > > As we have an auto-parameters-entity and an auto-parameters-service option in > xml forms on-event-update-area tags, it could be useful to have an > auto-parameters-form option that will propagate current form fields as > parameters to the paginate or submit action link (for instance in modal > "tunnel" processes) > > Currently, if you want to propagate the parameters of a form to a zone > that is refreshed in ajax after the submit you have to write specific > javascript code or to return all the parameters sent to the request through a > service as OUT parameters and/or redirect-parameter. > This feature will add automatically the form parameters on the generated > on-event-update-area link > To test, apply the OFBIZ_12684_Example.patch on a trunk environment (with > demo data) then go to the following page and click on the "edit" button on > line Web Store Warehouse: > https://localhost:8443/catalog/control/ProductStoreFacilities?productStoreId=9000 > The validation of the edition form should refresh correctly the list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
[ https://issues.apache.org/jira/browse/OFBIZ-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598419#comment-17598419 ] Leila Mekika edited comment on OFBIZ-12684 at 8/31/22 3:11 PM: --- Maybe your IDE doesn't point to the right file. If you make ctrl+clic over the auto-parameters-form link do you see where it leads ? was (Author: mleila): Maybe your IDE doesn't point to the right file. If you make ctrl+clic over the auto-parameters-form link wan you see wher it leads ? > Add auto-parameters-form option to on-event-update-area link in xml form > > > Key: OFBIZ-12684 > URL: https://issues.apache.org/jira/browse/OFBIZ-12684 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: Image 002.png, OFBIZ-12684.patch, > OFBIZ-12684_Example.patch, auto-parameters-form.png, > image-2022-08-31-15-27-40-474.png > > > As we have an auto-parameters-entity and an auto-parameters-service option in > xml forms on-event-update-area tags, it could be useful to have an > auto-parameters-form option that will propagate current form fields as > parameters to the paginate or submit action link (for instance in modal > "tunnel" processes) > > Currently, if you want to propagate the parameters of a form to a zone > that is refreshed in ajax after the submit you have to write specific > javascript code or to return all the parameters sent to the request through a > service as OUT parameters and/or redirect-parameter. > This feature will add automatically the form parameters on the generated > on-event-update-area link > To test, apply the OFBIZ_12684_Example.patch on a trunk environment (with > demo data) then go to the following page and click on the "edit" button on > line Web Store Warehouse: > https://localhost:8443/catalog/control/ProductStoreFacilities?productStoreId=9000 > The validation of the edition form should refresh correctly the list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
[ https://issues.apache.org/jira/browse/OFBIZ-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598419#comment-17598419 ] Leila Mekika commented on OFBIZ-12684: -- Maybe your IDE doesn't point to the right file. If you make ctrl+clic over the auto-parameters-form link wan you see wher it leads ? > Add auto-parameters-form option to on-event-update-area link in xml form > > > Key: OFBIZ-12684 > URL: https://issues.apache.org/jira/browse/OFBIZ-12684 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-12684.patch, OFBIZ-12684_Example.patch, > auto-parameters-form.png, image-2022-08-31-15-27-40-474.png > > > As we have an auto-parameters-entity and an auto-parameters-service option in > xml forms on-event-update-area tags, it could be useful to have an > auto-parameters-form option that will propagate current form fields as > parameters to the paginate or submit action link (for instance in modal > "tunnel" processes) > > Currently, if you want to propagate the parameters of a form to a zone > that is refreshed in ajax after the submit you have to write specific > javascript code or to return all the parameters sent to the request through a > service as OUT parameters and/or redirect-parameter. > This feature will add automatically the form parameters on the generated > on-event-update-area link > To test, apply the OFBIZ_12684_Example.patch on a trunk environment (with > demo data) then go to the following page and click on the "edit" button on > line Web Store Warehouse: > https://localhost:8443/catalog/control/ProductStoreFacilities?productStoreId=9000 > The validation of the edition form should refresh correctly the list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
[ https://issues.apache.org/jira/browse/OFBIZ-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12684: - Attachment: image-2022-08-31-15-27-40-474.png > Add auto-parameters-form option to on-event-update-area link in xml form > > > Key: OFBIZ-12684 > URL: https://issues.apache.org/jira/browse/OFBIZ-12684 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-12684.patch, OFBIZ-12684_Example.patch, > image-2022-08-31-15-27-40-474.png > > > As we have an auto-parameters-entity and an auto-parameters-service option in > xml forms on-event-update-area tags, it could be useful to have an > auto-parameters-form option that will propagate current form fields as > parameters to the paginate or submit action link (for instance in modal > "tunnel" processes) > > Currently, if you want to propagate the parameters of a form to a zone > that is refreshed in ajax after the submit you have to write specific > javascript code or to return all the parameters sent to the request through a > service as OUT parameters and/or redirect-parameter. > This feature will add automatically the form parameters on the generated > on-event-update-area link > To test, apply the OFBIZ_12684_Example.patch on a trunk environment (with > demo data) then go to the following page and click on the "edit" button on > line Web Store Warehouse: > https://localhost:8443/catalog/control/ProductStoreFacilities?productStoreId=9000 > The validation of the edition form should refresh correctly the list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
[ https://issues.apache.org/jira/browse/OFBIZ-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598382#comment-17598382 ] Leila Mekika commented on OFBIZ-12684: -- [~jleroux], do you know if the error also appear with an other IDE ? I use Eclipse and I don't see this alert: !image-2022-08-31-15-27-40-474.png! > Add auto-parameters-form option to on-event-update-area link in xml form > > > Key: OFBIZ-12684 > URL: https://issues.apache.org/jira/browse/OFBIZ-12684 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-12684.patch, OFBIZ-12684_Example.patch, > image-2022-08-31-15-27-40-474.png > > > As we have an auto-parameters-entity and an auto-parameters-service option in > xml forms on-event-update-area tags, it could be useful to have an > auto-parameters-form option that will propagate current form fields as > parameters to the paginate or submit action link (for instance in modal > "tunnel" processes) > > Currently, if you want to propagate the parameters of a form to a zone > that is refreshed in ajax after the submit you have to write specific > javascript code or to return all the parameters sent to the request through a > service as OUT parameters and/or redirect-parameter. > This feature will add automatically the form parameters on the generated > on-event-update-area link > To test, apply the OFBIZ_12684_Example.patch on a trunk environment (with > demo data) then go to the following page and click on the "edit" button on > line Web Store Warehouse: > https://localhost:8443/catalog/control/ProductStoreFacilities?productStoreId=9000 > The validation of the edition form should refresh correctly the list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
[ https://issues.apache.org/jira/browse/OFBIZ-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597955#comment-17597955 ] Leila Mekika commented on OFBIZ-12684: -- Hello Jacques, Yes it was an example to show that it didn't break anything. For the error, can it be because i didn't put the attribute form-name in my example patch ? Leila > Add auto-parameters-form option to on-event-update-area link in xml form > > > Key: OFBIZ-12684 > URL: https://issues.apache.org/jira/browse/OFBIZ-12684 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-12684.patch, OFBIZ-12684_Example.patch > > > As we have an auto-parameters-entity and an auto-parameters-service option in > xml forms on-event-update-area tags, it could be useful to have an > auto-parameters-form option that will propagate current form fields as > parameters to the paginate or submit action link (for instance in modal > "tunnel" processes) > > Currently, if you want to propagate the parameters of a form to a zone > that is refreshed in ajax after the submit you have to write specific > javascript code or to return all the parameters sent to the request through a > service as OUT parameters and/or redirect-parameter. > This feature will add automatically the form parameters on the generated > on-event-update-area link > To test, apply the OFBIZ_12684_Example.patch on a trunk environment (with > demo data) then go to the following page and click on the "edit" button on > line Web Store Warehouse: > https://localhost:8443/catalog/control/ProductStoreFacilities?productStoreId=9000 > The validation of the edition form should refresh correctly the list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
[ https://issues.apache.org/jira/browse/OFBIZ-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597056#comment-17597056 ] Leila Mekika commented on OFBIZ-12684: -- Thank you Jacques > Add auto-parameters-form option to on-event-update-area link in xml form > > > Key: OFBIZ-12684 > URL: https://issues.apache.org/jira/browse/OFBIZ-12684 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > Attachments: OFBIZ-12684.patch, OFBIZ-12684_Example.patch > > > As we have an auto-parameters-entity and an auto-parameters-service option in > xml forms on-event-update-area tags, it could be useful to have an > auto-parameters-form option that will propagate current form fields as > parameters to the paginate or submit action link (for instance in modal > "tunnel" processes) > > Currently, if you want to propagate the parameters of a form to a zone > that is refreshed in ajax after the submit you have to write specific > javascript code or to return all the parameters sent to the request through a > service as OUT parameters and/or redirect-parameter. > This feature will add automatically the form parameters on the generated > on-event-update-area link > To test, apply the OFBIZ_12684_Example.patch on a trunk environment (with > demo data) then go to the following page and click on the "edit" button on > line Web Store Warehouse: > https://localhost:8443/catalog/control/ProductStoreFacilities?productStoreId=9000 > The validation of the edition form should refresh correctly the list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
[ https://issues.apache.org/jira/browse/OFBIZ-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597019#comment-17597019 ] Leila Mekika commented on OFBIZ-12684: -- Hello Jacques, Yes, it does not change the behaviour, it only simplify the writing in the xml. The parameters of the form are redirected automatically to the "refreshed" area if you need to. Currently we have to redirect them through service or specific javascript to do so > Add auto-parameters-form option to on-event-update-area link in xml form > > > Key: OFBIZ-12684 > URL: https://issues.apache.org/jira/browse/OFBIZ-12684 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Priority: Trivial > Attachments: OFBIZ-12684.patch, OFBIZ-12684_Example.patch > > > As we have an auto-parameters-entity and an auto-parameters-service option in > xml forms on-event-update-area tags, it could be useful to have an > auto-parameters-form option that will propagate current form fields as > parameters to the paginate or submit action link (for instance in modal > "tunnel" processes) > > Currently, if you want to propagate the parameters of a form to a zone > that is refreshed in ajax after the submit you have to write specific > javascript code or to return all the parameters sent to the request through a > service as OUT parameters and/or redirect-parameter. > This feature will add automatically the form parameters on the generated > on-event-update-area link > To test, apply the OFBIZ_12684_Example.patch on a trunk environment (with > demo data) then go to the following page and click on the "edit" button on > line Web Store Warehouse: > https://localhost:8443/catalog/control/ProductStoreFacilities?productStoreId=9000 > The validation of the edition form should refresh correctly the list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12685) Content tag in a screen does not display correctly images
[ https://issues.apache.org/jira/browse/OFBIZ-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597010#comment-17597010 ] Leila Mekika commented on OFBIZ-12685: -- Ok, thank you Jacques > Content tag in a screen does not display correctly images > - > > Key: OFBIZ-12685 > URL: https://issues.apache.org/jira/browse/OFBIZ-12685 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: 18.12.06, 22.01.01 > > Attachments: OFBIZ-12685.patch > > > When we want to display an image content within a screen through > tag, images are not rendered correctly > > To test: > Go to admin party profile page and upload a picture file as a new > "LGOIMGURL" for instance > [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] > > When your content file is uploaded, note the contentId and got to > page ShowContent (which render content using the tag ) > > [https://localhost:8443/content/control/showContent?contentId=X] > > The image will not be rendered without the given patch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12685) Content tag in a screen does not display correctly images
[ https://issues.apache.org/jira/browse/OFBIZ-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12685: - Description: When we want to display an image content within a screen through tag, images are not rendered correctly To test: Go to admin party profile page and upload a picture file as a new "LGOIMGURL" for instance [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] When your content file is uploaded, note the contentId and got to page ShowContent (which render content using the tag ) [https://localhost:8443/content/control/showContent?contentId=X] The image will not be rendered without the given patch. was: When we want to display an image content within a screen through tag, images are not rendered correctly To test: Go to admin party profile page and upload a picture as a new "LGOIMGURL" for instance [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] When your content file is uploaded, note the contentId and got to page ShowContent (which render content using the tag ) [https://localhost:8443/content/control/showContent?contentId=X] The image will not be rendered without the given patch. > Content tag in a screen does not display correctly images > - > > Key: OFBIZ-12685 > URL: https://issues.apache.org/jira/browse/OFBIZ-12685 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Priority: Trivial > Attachments: OFBIZ-12685.patch > > > When we want to display an image content within a screen through > tag, images are not rendered correctly > > To test: > Go to admin party profile page and upload a picture file as a new > "LGOIMGURL" for instance > [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] > > When your content file is uploaded, note the contentId and got to > page ShowContent (which render content using the tag ) > > [https://localhost:8443/content/control/showContent?contentId=X] > > The image will not be rendered without the given patch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12685) Content tag in a screen does not display correctly images
[ https://issues.apache.org/jira/browse/OFBIZ-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12685: - Description: When we want to display an image content within a screen through tag, images are not rendered correctly To test: Go to admin party profile page and upload a picture as a new "LGOIMGURL" for instance [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] When your content file is uploaded, note the contentId and got to page ShowContent (which render content using the tag ) [https://localhost:8443/content/control/showContent?contentId=X] The image will not be rendered without the given patch. was: When we want to display a n image content within a screen through tag, images are not rendered correctly To test: Go to admin party profile page and upload a picture as a new "LGOIMGURL" for instance [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] When your content file is uploaded, note the contentId and got to page ShowContent (which render content using the tag ) [https://localhost:8443/content/control/showContent?contentId=X] The image will not be rendered without the given patch. > Content tag in a screen does not display correctly images > - > > Key: OFBIZ-12685 > URL: https://issues.apache.org/jira/browse/OFBIZ-12685 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Priority: Trivial > Attachments: OFBIZ-12685.patch > > > When we want to display an image content within a screen through > tag, images are not rendered correctly > > To test: > Go to admin party profile page and upload a picture as a new "LGOIMGURL" > for instance > [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] > > When your content file is uploaded, note the contentId and got to > page ShowContent (which render content using the tag ) > > [https://localhost:8443/content/control/showContent?contentId=X] > > The image will not be rendered without the given patch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12685) Content tag in a screen does not display correctly images
[ https://issues.apache.org/jira/browse/OFBIZ-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12685: - Summary: Content tag in a screen does not display correctly images (was: Content tag in a screen does not display correctly the image) > Content tag in a screen does not display correctly images > - > > Key: OFBIZ-12685 > URL: https://issues.apache.org/jira/browse/OFBIZ-12685 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Priority: Trivial > Attachments: OFBIZ-12685.patch > > > When we want to display a n image content within a screen through > tag, images are not rendered correctly > > To test: > Go to admin party profile page and upload a picture as a new "LGOIMGURL" > for instance > [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] > > When your content file is uploaded, note the contentId and got to > page ShowContent (which render content using the tag ) > > [https://localhost:8443/content/control/showContent?contentId=X] > > The image will not be rendered without the given patch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12685) Content tag in a screen does not display correctly the image
[ https://issues.apache.org/jira/browse/OFBIZ-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12685: - Priority: Trivial (was: Major) > Content tag in a screen does not display correctly the image > > > Key: OFBIZ-12685 > URL: https://issues.apache.org/jira/browse/OFBIZ-12685 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Priority: Trivial > Attachments: OFBIZ-12685.patch > > > When we want to display a n image content within a screen through > tag, images are not rendered correctly > > To test: > Go to admin party profile page and upload a picture as a new "LGOIMGURL" > for instance > [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] > > When your content file is uploaded, note the contentId and got to > page ShowContent (which render content using the tag ) > > [https://localhost:8443/content/control/showContent?contentId=X] > > The image will not be rendered without the given patch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12685) Content tag in a screen does not display correctly the image
[ https://issues.apache.org/jira/browse/OFBIZ-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12685: - Attachment: OFBIZ-12685.patch > Content tag in a screen does not display correctly the image > > > Key: OFBIZ-12685 > URL: https://issues.apache.org/jira/browse/OFBIZ-12685 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Priority: Major > Attachments: OFBIZ-12685.patch > > > When we want to display a n image content within a screen through > tag, images are not rendered correctly > > To test: > Go to admin party profile page and upload a picture as a new "LGOIMGURL" > for instance > [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] > > When your content file is uploaded, note the contentId and got to > page ShowContent (which render content using the tag ) > > [https://localhost:8443/content/control/showContent?contentId=X] > > The image will not be rendered without the given patch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12685) Content tag in a screen does not display correctly the image
[ https://issues.apache.org/jira/browse/OFBIZ-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12685: - Description: When we want to display a n image content within a screen through tag, images are not rendered correctly To test: Go to admin party profile page and upload a picture as a new "LGOIMGURL" for instance [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] When your content file is uploaded, note the contentId and got to page ShowContent (which render content using the tag ) [https://localhost:8443/content/control/showContent?contentId=X] The image will not be rendered without the given patch. was: When we want to display a n image content within a screen through tag, images are not rendered correctly To test: Go to admin party profile page and upload a picture as a new "LGOIMGURL" for instance https://localhost:8443/partymgr/control/viewprofile?partyId=admin When your content file is uploaded, note the contentId and got to page ShowContent https://localhost:8443/content/control/showContent?contentId=X The image will not be rendered without the given patch. The screen ShowContent uses the tag > Content tag in a screen does not display correctly the image > > > Key: OFBIZ-12685 > URL: https://issues.apache.org/jira/browse/OFBIZ-12685 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Priority: Major > Attachments: OFBIZ-12685.patch > > > When we want to display a n image content within a screen through > tag, images are not rendered correctly > > To test: > Go to admin party profile page and upload a picture as a new "LGOIMGURL" > for instance > [https://localhost:8443/partymgr/control/viewprofile?partyId=admin] > > When your content file is uploaded, note the contentId and got to > page ShowContent (which render content using the tag ) > > [https://localhost:8443/content/control/showContent?contentId=X] > > The image will not be rendered without the given patch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12685) Content tag in a screen does not display correctly the image
Leila Mekika created OFBIZ-12685: Summary: Content tag in a screen does not display correctly the image Key: OFBIZ-12685 URL: https://issues.apache.org/jira/browse/OFBIZ-12685 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Upcoming Branch Reporter: Leila Mekika When we want to display a n image content within a screen through tag, images are not rendered correctly To test: Go to admin party profile page and upload a picture as a new "LGOIMGURL" for instance https://localhost:8443/partymgr/control/viewprofile?partyId=admin When your content file is uploaded, note the contentId and got to page ShowContent https://localhost:8443/content/control/showContent?contentId=X The image will not be rendered without the given patch. The screen ShowContent uses the tag -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
[ https://issues.apache.org/jira/browse/OFBIZ-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12684: - Description: As we have an auto-parameters-entity and an auto-parameters-service option in xml forms on-event-update-area tags, it could be useful to have an auto-parameters-form option that will propagate current form fields as parameters to the paginate or submit action link (for instance in modal "tunnel" processes) Currently, if you want to propagate the parameters of a form to a zone that is refreshed in ajax after the submit you have to write specific javascript code or to return all the parameters sent to the request through a service as OUT parameters and/or redirect-parameter. This feature will add automatically the form parameters on the generated on-event-update-area link To test, apply the OFBIZ_12684_Example.patch on a trunk environment (with demo data) then go to the following page and click on the "edit" button on line Web Store Warehouse: https://localhost:8443/catalog/control/ProductStoreFacilities?productStoreId=9000 The validation of the edition form should refresh correctly the list was: As we have an auto-parameters-entity and an auto-parameters-service option in xml forms on-event-update-area tags, it could be useful to have an auto-parameters-form option that will propagate current form fields as parameters to the paginate or submit action link (for instance in modal "tunnel" processes) Currently, if you want to propagate the parameters of a form to a zone that is refreshed in ajax after the submit you have to write specific javascript code or to return all the parameters sent to the request through a service as OUT parameters and/or redirect-parameter. This feature will add automa > Add auto-parameters-form option to on-event-update-area link in xml form > > > Key: OFBIZ-12684 > URL: https://issues.apache.org/jira/browse/OFBIZ-12684 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Priority: Trivial > Attachments: OFBIZ-12684.patch, OFBIZ-12684_Example.patch > > > As we have an auto-parameters-entity and an auto-parameters-service option in > xml forms on-event-update-area tags, it could be useful to have an > auto-parameters-form option that will propagate current form fields as > parameters to the paginate or submit action link (for instance in modal > "tunnel" processes) > > Currently, if you want to propagate the parameters of a form to a zone > that is refreshed in ajax after the submit you have to write specific > javascript code or to return all the parameters sent to the request through a > service as OUT parameters and/or redirect-parameter. > This feature will add automatically the form parameters on the generated > on-event-update-area link > To test, apply the OFBIZ_12684_Example.patch on a trunk environment (with > demo data) then go to the following page and click on the "edit" button on > line Web Store Warehouse: > https://localhost:8443/catalog/control/ProductStoreFacilities?productStoreId=9000 > The validation of the edition form should refresh correctly the list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
[ https://issues.apache.org/jira/browse/OFBIZ-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12684: - Attachment: OFBIZ-12684.patch OFBIZ-12684_Example.patch > Add auto-parameters-form option to on-event-update-area link in xml form > > > Key: OFBIZ-12684 > URL: https://issues.apache.org/jira/browse/OFBIZ-12684 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Priority: Trivial > Attachments: OFBIZ-12684.patch, OFBIZ-12684_Example.patch > > > As we have an auto-parameters-entity and an auto-parameters-service option in > xml forms on-event-update-area tags, it could be useful to have an > auto-parameters-form option that will propagate current form fields as > parameters to the paginate or submit action link (for instance in modal > "tunnel" processes) > > Currently, if you want to propagate the parameters of a form to a zone > that is refreshed in ajax after the submit you have to write specific > javascript code or to return all the parameters sent to the request through a > service as OUT parameters and/or redirect-parameter. > This feature will add automa -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12684) Add auto-parameters-form option to on-event-update-area link in xml form
Leila Mekika created OFBIZ-12684: Summary: Add auto-parameters-form option to on-event-update-area link in xml form Key: OFBIZ-12684 URL: https://issues.apache.org/jira/browse/OFBIZ-12684 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Upcoming Branch Reporter: Leila Mekika As we have an auto-parameters-entity and an auto-parameters-service option in xml forms on-event-update-area tags, it could be useful to have an auto-parameters-form option that will propagate current form fields as parameters to the paginate or submit action link (for instance in modal "tunnel" processes) Currently, if you want to propagate the parameters of a form to a zone that is refreshed in ajax after the submit you have to write specific javascript code or to return all the parameters sent to the request through a service as OUT parameters and/or redirect-parameter. This feature will add automa -- 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 ] Leila Mekika updated OFBIZ-12664: - Attachment: OFBIZ-12664_Example.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: Leila Mekika >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-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 ] Leila Mekika updated OFBIZ-12664: - Attachment: (was: OFBIZ-12664_Example.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: Leila Mekika >Priority: Trivial > Attachments: OFBIZ-12664.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-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 ] Leila Mekika 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=9000] 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 parameter 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: Leila Mekika >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-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 ] Leila Mekika updated OFBIZ-12664: - Attachment: (was: OFBIZ-12664_Example.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: Leila Mekika >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 parameter 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-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 ] Leila Mekika updated OFBIZ-12664: - Attachment: (was: OFBIZ-12664.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: Leila Mekika >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 parameter 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-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 ] Leila Mekika updated OFBIZ-12664: - Attachment: OFBIZ-12664.patch OFBIZ-12664_Example.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: Leila Mekika >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 parameter 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-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 ] Leila Mekika updated OFBIZ-12664: - Attachment: OFBIZ-12664.patch OFBIZ-12664_Example.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: Leila Mekika >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 parameter 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] [Created] (OFBIZ-12664) Automatic callback element propagation inside a modal "tunnel" process
Leila Mekika created OFBIZ-12664: Summary: 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: Leila Mekika 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 parameter 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-12663) Allow DynamicView use in standard performFind services
[ https://issues.apache.org/jira/browse/OFBIZ-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12663: - Description: This is a proposition to extend the use of standard find services (prepareFind, executeFind and performFind) to dynamicView. It can help to have performFind services (such has performFindParty) that use the same standard service To describe quickly, it adds dynamicViewEntity as an optional parameter of prepareFind, executeFind and performFind services and adapt the query accordingly was: This is a proposition to extend the use of standard find services (prepareFind, executeFind and performFind) to dynamicView. It can help to have performFind services (such has performFindParty) that use the same standard service > Allow DynamicView use in standard performFind services > -- > > Key: OFBIZ-12663 > URL: https://issues.apache.org/jira/browse/OFBIZ-12663 > Project: OFBiz > Issue Type: Improvement > Components: framework/common >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Priority: Major > Attachments: OFBIZ-12663.patch > > > This is a proposition to extend the use of standard find services > (prepareFind, executeFind and performFind) to dynamicView. > It can help to have performFind services (such has performFindParty) that use > the same standard service > To describe quickly, it adds dynamicViewEntity as an optional parameter of > prepareFind, executeFind and performFind services and adapt the query > accordingly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12663) Allow DynamicView use in standard performFind services
[ https://issues.apache.org/jira/browse/OFBIZ-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12663: - Attachment: OFBIZ-12663.patch > Allow DynamicView use in standard performFind services > -- > > Key: OFBIZ-12663 > URL: https://issues.apache.org/jira/browse/OFBIZ-12663 > Project: OFBiz > Issue Type: Improvement > Components: framework/common >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Priority: Major > Attachments: OFBIZ-12663.patch > > > This is a proposition to extend the use of standard find services > (prepareFind, executeFind and performFind) to dynamicView. > It can help to have performFind services (such has performFindParty) that use > the same standard service -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12663) Allow DynamicView use in standard performFind services
Leila Mekika created OFBIZ-12663: Summary: Allow DynamicView use in standard performFind services Key: OFBIZ-12663 URL: https://issues.apache.org/jira/browse/OFBIZ-12663 Project: OFBiz Issue Type: Improvement Components: framework/common Affects Versions: Upcoming Branch Reporter: Leila Mekika This is a proposition to extend the use of standard find services (prepareFind, executeFind and performFind) to dynamicView. It can help to have performFind services (such has performFindParty) that use the same standard service -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12619) Required field not working on upload type form
[ https://issues.apache.org/jira/browse/OFBIZ-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17561448#comment-17561448 ] Leila Mekika commented on OFBIZ-12619: -- Thank you Jacques, Sorry for the example, I didn't see your previous question... > Required field not working on upload type form > -- > > Key: OFBIZ-12619 > URL: https://issues.apache.org/jira/browse/OFBIZ-12619 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS >Affects Versions: Upcoming Branch >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Minor > Labels: trunk > Fix For: 18.12.06, 22.01.01 > > Attachments: OFBIZ-12619.patch > > > When trying to submit an upload form with empty required fields, > the validation is not blocked and the submit is made. > > Here is a patch to allow required validation control in upload forms -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12619) Required field not working on upload type form
[ https://issues.apache.org/jira/browse/OFBIZ-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12619: - Attachment: (was: OFBIZ-12619.patch) > Required field not working on upload type form > -- > > Key: OFBIZ-12619 > URL: https://issues.apache.org/jira/browse/OFBIZ-12619 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Leila Mekika >Priority: Minor > Labels: trunk > Attachments: OFBIZ-12619.patch > > > When trying to submit an upload form with empty required fields, > the validation is not blocked and the submit is made. > > Here is a patch to allow required validation control in upload forms -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (OFBIZ-12619) Required field not working on upload type form
[ https://issues.apache.org/jira/browse/OFBIZ-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12619: - Attachment: OFBIZ-12619.patch > Required field not working on upload type form > -- > > Key: OFBIZ-12619 > URL: https://issues.apache.org/jira/browse/OFBIZ-12619 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Leila Mekika >Priority: Minor > Labels: trunk > Attachments: OFBIZ-12619.patch > > > When trying to submit an upload form with empty required fields, > the validation is not blocked and the submit is made. > > Here is a patch to allow required validation control in upload forms -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (OFBIZ-12619) Required field not working on upload type form
[ https://issues.apache.org/jira/browse/OFBIZ-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12619: - Attachment: OFBIZ-12619.patch > Required field not working on upload type form > -- > > Key: OFBIZ-12619 > URL: https://issues.apache.org/jira/browse/OFBIZ-12619 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Reporter: Leila Mekika >Priority: Minor > Labels: trunk > Attachments: OFBIZ-12619.patch > > > When trying to submit an upload form with empty required fields, > the validation is not blocked and the submit is made. > > Here is a patch to allow required validation control in upload forms -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (OFBIZ-12619) Required field not working on upload type form
Leila Mekika created OFBIZ-12619: Summary: Required field not working on upload type form Key: OFBIZ-12619 URL: https://issues.apache.org/jira/browse/OFBIZ-12619 Project: OFBiz Issue Type: Improvement Components: ALL APPLICATIONS Reporter: Leila Mekika Attachments: OFBIZ-12619.patch When trying to submit an upload form with empty required fields, the validation is not blocked and the submit is made. Here is a patch to allow required validation control in upload forms -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (OFBIZ-12583) Convert SubscriptionServices.xml mini lang to groovy
[
https://issues.apache.org/jira/browse/OFBIZ-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-12583:
-
Description: {{Conversion of SubscriptionServices.xml file to groovy}}
> Convert SubscriptionServices.xml mini lang to groovy
>
>
> Key: OFBIZ-12583
> URL: https://issues.apache.org/jira/browse/OFBIZ-12583
> Project: OFBiz
> Issue Type: Sub-task
> Components: product
>Reporter: Leila Mekika
>Priority: Minor
> Attachments: OFBIZ-12583.patch
>
>
> {{Conversion of SubscriptionServices.xml file to groovy}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (OFBIZ-12583) Convert SubscriptionServices.xml mini lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12583: - Component/s: product > Convert SubscriptionServices.xml mini lang to groovy > > > Key: OFBIZ-12583 > URL: https://issues.apache.org/jira/browse/OFBIZ-12583 > Project: OFBiz > Issue Type: Sub-task > Components: product >Reporter: Leila Mekika >Priority: Minor > Attachments: OFBIZ-12583.patch > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-12583) Convert SubscriptionServices.xml mini lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12583: - Attachment: OFBIZ-12583.patch > Convert SubscriptionServices.xml mini lang to groovy > > > Key: OFBIZ-12583 > URL: https://issues.apache.org/jira/browse/OFBIZ-12583 > Project: OFBiz > Issue Type: Sub-task >Reporter: Leila Mekika >Priority: Minor > Attachments: OFBIZ-12583.patch > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12583) Convert SubscriptionServices.xml mini lang to groovy
Leila Mekika created OFBIZ-12583: Summary: Convert SubscriptionServices.xml mini lang to groovy Key: OFBIZ-12583 URL: https://issues.apache.org/jira/browse/OFBIZ-12583 Project: OFBiz Issue Type: Sub-task Reporter: Leila Mekika -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-12278) Link request-confirmation not generated on menus
[
https://issues.apache.org/jira/browse/OFBIZ-12278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17379712#comment-17379712
]
Leila Mekika commented on OFBIZ-12278:
--
Thanks [~nmalin]
> Link request-confirmation not generated on menus
>
>
> Key: OFBIZ-12278
> URL: https://issues.apache.org/jira/browse/OFBIZ-12278
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Trunk, 17.12.07
>Reporter: Leila Mekika
>Assignee: Nicolas Malin
>Priority: Minor
> Fix For: 18.12.01, Upcoming Branch
>
> Attachments: OFBIZ-12278.patch
>
>
> Menus link with request-confirmation and confirmation message do not generate
> the script that open confirmation
> To reproduce, you can check the link "Status to cancelled" on a created
> payment who does not ask for confirmation while his definition is done:
> {code:java}
> confirmation-message="You want to cancel this payment number
> ${payment.paymentId}?">
>
>
>
> {code}
> ex:
>
> [https://demo-stable.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
> [https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-12279) Macro renderLink default height and width not retrieved on menus
[ https://issues.apache.org/jira/browse/OFBIZ-12279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17379711#comment-17379711 ] Leila Mekika commented on OFBIZ-12279: -- Thank you [~jleroux] > Macro renderLink default height and width not retrieved on menus > > > Key: OFBIZ-12279 > URL: https://issues.apache.org/jira/browse/OFBIZ-12279 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-12279.patch > > > Menus link defaut parameters for height and width are not considered when the > link is generated > The problem seems to be that when parameter with empty value is passed to the > macro, macro default values are not retrieved. > *To reproduce* > you can create a "layered-modal" type link in a menu and click on the link > (without height nor width): > this will generate the link with parameters "data-dialog-height" and > "data-dialog-width" empty > *Patch provided* > When applied, the MacroMenuRenderer.renderLink will not send empty values to > the macro so that default value will be retrieved (what is actually done on > MacroFormRenderer.renderLookup) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-12279) Macro renderLink default height and width not retrieved on menus
[ https://issues.apache.org/jira/browse/OFBIZ-12279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17379030#comment-17379030 ] Leila Mekika edited comment on OFBIZ-12279 at 7/12/21, 8:06 AM: Hello [~jleroux], the implication is that when we open the layered modal, it is reduce to the minimum (title bar size) and we have to expand the modal window to see its content. I think it can be considered like a bug :) was (Author: mleila): Hello [~jleroux], the implication is that when we open the layered modal, it is reduce to the minimum and we have to expand the window to see its content. I think it can be considered like a bug :) > Macro renderLink default height and width not retrieved on menus > > > Key: OFBIZ-12279 > URL: https://issues.apache.org/jira/browse/OFBIZ-12279 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-12279.patch > > > Menus link defaut parameters for height and width are not considered when the > link is generated > The problem seems to be that when parameter with empty value is passed to the > macro, macro default values are not retrieved. > *To reproduce* > you can create a "layered-modal" type link in a menu and click on the link > (without height nor width): > this will generate the link with parameters "data-dialog-height" and > "data-dialog-width" empty > *Patch provided* > When applied, the MacroMenuRenderer.renderLink will not send empty values to > the macro so that default value will be retrieved (what is actually done on > MacroFormRenderer.renderLookup) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-12279) Macro renderLink default height and width not retrieved on menus
[ https://issues.apache.org/jira/browse/OFBIZ-12279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17379030#comment-17379030 ] Leila Mekika commented on OFBIZ-12279: -- Hello [~jleroux], the implication is that when we open the layered modal, it is reduce to the minimum and we have to expand the window to see its content. I think it can be considered like a bug :) > Macro renderLink default height and width not retrieved on menus > > > Key: OFBIZ-12279 > URL: https://issues.apache.org/jira/browse/OFBIZ-12279 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-12279.patch > > > Menus link defaut parameters for height and width are not considered when the > link is generated > The problem seems to be that when parameter with empty value is passed to the > macro, macro default values are not retrieved. > *To reproduce* > you can create a "layered-modal" type link in a menu and click on the link > (without height nor width): > this will generate the link with parameters "data-dialog-height" and > "data-dialog-width" empty > *Patch provided* > When applied, the MacroMenuRenderer.renderLink will not send empty values to > the macro so that default value will be retrieved (what is actually done on > MacroFormRenderer.renderLookup) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12279) Macro renderLink default height and width not retrieved on menus
[ https://issues.apache.org/jira/browse/OFBIZ-12279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12279: - Summary: Macro renderLink default height and width not retrieved on menus (was: Macro renderLink default height and width not used on menus) > Macro renderLink default height and width not retrieved on menus > > > Key: OFBIZ-12279 > URL: https://issues.apache.org/jira/browse/OFBIZ-12279 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: OFBIZ-12279.patch > > > Menus link defaut parameters for height and width are not considered when the > link is generated > The problem seems to be that when parameter with empty value is passed to the > macro, macro default values are not retrieved. > *To reproduce* > you can create a "layered-modal" type link in a menu and click on the link > (without height nor width): > this will generate the link with parameters "data-dialog-height" and > "data-dialog-width" empty > *Patch provided* > When applied, the MacroMenuRenderer.renderLink will not send empty values to > the macro so that default value will be retrieved (what is actually done on > MacroFormRenderer.renderLookup) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12279) Macro renderLink default height and width not used on menus
[ https://issues.apache.org/jira/browse/OFBIZ-12279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12279: - Attachment: OFBIZ-12279.patch > Macro renderLink default height and width not used on menus > --- > > Key: OFBIZ-12279 > URL: https://issues.apache.org/jira/browse/OFBIZ-12279 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: OFBIZ-12279.patch > > > Menus link defaut parameters for height and width are not considered when the > link is generated > The problem seems to be that when parameter with empty value is passed to the > macro, macro default values are not retrieved. > *To reproduce* > you can create a "layered-modal" type link in a menu and click on the link > (without height nor width): > this will generate the link with parameters "data-dialog-height" and > "data-dialog-width" empty > *Patch provided* > When applied, the MacroMenuRenderer.renderLink will not send empty values to > the macro so that default value will be retrieved (what is actually done on > MacroFormRenderer.renderLookup) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-12279) Macro renderLink default height and width not used on menus
Leila Mekika created OFBIZ-12279: Summary: Macro renderLink default height and width not used on menus Key: OFBIZ-12279 URL: https://issues.apache.org/jira/browse/OFBIZ-12279 Project: OFBiz Issue Type: Improvement Components: ALL APPLICATIONS Affects Versions: Trunk Reporter: Leila Mekika Menus link defaut parameters for height and width are not considered when the link is generated The problem seems to be that when parameter with empty value is passed to the macro, macro default values are not retrieved. *To reproduce* you can create a "layered-modal" type link in a menu and click on the link (without height nor width): this will generate the link with parameters "data-dialog-height" and "data-dialog-width" empty *Patch provided* When applied, the MacroMenuRenderer.renderLink will not send empty values to the macro so that default value will be retrieved (what is actually done on MacroFormRenderer.renderLookup) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12278) Link request-confirmation not generated on menus
[
https://issues.apache.org/jira/browse/OFBIZ-12278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-12278:
-
Attachment: OFBIZ-12278.patch
> Link request-confirmation not generated on menus
>
>
> Key: OFBIZ-12278
> URL: https://issues.apache.org/jira/browse/OFBIZ-12278
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Trunk, 17.12.07
>Reporter: Leila Mekika
>Assignee: Nicolas Malin
>Priority: Minor
> Attachments: OFBIZ-12278.patch
>
>
> Menus link with request-confirmation and confirmation message do not generate
> the script that open confirmation
> To reproduce, you can check the link "Status to cancelled" on a created
> payment who does not ask for confirmation while his definition is done:
> {code:java}
> confirmation-message="You want to cancel this payment number
> ${payment.paymentId}?">
>
>
>
> {code}
> ex:
>
> [https://demo-stable.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
> [https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12278) Link request-confirmation not generated on menus
[
https://issues.apache.org/jira/browse/OFBIZ-12278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-12278:
-
Attachment: (was: OFBIZ-12278.patch)
> Link request-confirmation not generated on menus
>
>
> Key: OFBIZ-12278
> URL: https://issues.apache.org/jira/browse/OFBIZ-12278
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Trunk, 17.12.07
>Reporter: Leila Mekika
>Assignee: Nicolas Malin
>Priority: Minor
>
> Menus link with request-confirmation and confirmation message do not generate
> the script that open confirmation
> To reproduce, you can check the link "Status to cancelled" on a created
> payment who does not ask for confirmation while his definition is done:
> {code:java}
> confirmation-message="You want to cancel this payment number
> ${payment.paymentId}?">
>
>
>
> {code}
> ex:
>
> [https://demo-stable.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
> [https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12278) Link request-confirmation not generated on menus
[
https://issues.apache.org/jira/browse/OFBIZ-12278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-12278:
-
Attachment: OFBIZ-12278.patch
> Link request-confirmation not generated on menus
>
>
> Key: OFBIZ-12278
> URL: https://issues.apache.org/jira/browse/OFBIZ-12278
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Trunk, 17.12.07
>Reporter: Leila Mekika
>Assignee: Nicolas Malin
>Priority: Minor
> Attachments: OFBIZ-12278.patch
>
>
> Menus link with request-confirmation and confirmation message do not generate
> the script that open confirmation
> To reproduce, you can check the link "Status to cancelled" on a created
> payment who does not ask for confirmation while his definition is done:
> {code:java}
> confirmation-message="You want to cancel this payment number
> ${payment.paymentId}?">
>
>
>
> {code}
> ex:
>
> [https://demo-stable.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
> [https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12278) Link request-confirmation not generated on menus
[
https://issues.apache.org/jira/browse/OFBIZ-12278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-12278:
-
Attachment: (was: OFBIZ-12278.patch)
> Link request-confirmation not generated on menus
>
>
> Key: OFBIZ-12278
> URL: https://issues.apache.org/jira/browse/OFBIZ-12278
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Trunk, 17.12.07
>Reporter: Leila Mekika
>Assignee: Nicolas Malin
>Priority: Minor
> Attachments: OFBIZ-12278.patch
>
>
> Menus link with request-confirmation and confirmation message do not generate
> the script that open confirmation
> To reproduce, you can check the link "Status to cancelled" on a created
> payment who does not ask for confirmation while his definition is done:
> {code:java}
> confirmation-message="You want to cancel this payment number
> ${payment.paymentId}?">
>
>
>
> {code}
> ex:
>
> [https://demo-stable.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
> [https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12278) Link request-confirmation not generated on menus
[
https://issues.apache.org/jira/browse/OFBIZ-12278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-12278:
-
Description:
Menus link with request-confirmation and confirmation message do not generate
the script that open confirmation
To reproduce, you can check the link "Status to cancelled" on a created payment
who does not ask for confirmation while his definition is done:
{code:java}
{code}
ex:
[https://demo-stable.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
[https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
was:
Menus link with request-confirmation and confirmation message do not generate
the script that open confirmation
To reproduce, you can check the link "Status to cancelled" on a created payment
who does not ask for confirmation thus his definition is done:
{code:java}
{code}
ex:
[https://demo-stable.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
[https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
> Link request-confirmation not generated on menus
>
>
> Key: OFBIZ-12278
> URL: https://issues.apache.org/jira/browse/OFBIZ-12278
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Trunk, 17.12.07
>Reporter: Leila Mekika
>Priority: Minor
> Attachments: OFBIZ-12278.patch
>
>
> Menus link with request-confirmation and confirmation message do not generate
> the script that open confirmation
> To reproduce, you can check the link "Status to cancelled" on a created
> payment who does not ask for confirmation while his definition is done:
> {code:java}
> confirmation-message="You want to cancel this payment number
> ${payment.paymentId}?">
>
>
>
> {code}
> ex:
>
> [https://demo-stable.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
> [https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12278) Link request-confirmation not generated on menus
[
https://issues.apache.org/jira/browse/OFBIZ-12278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-12278:
-
Attachment: OFBIZ-12278.patch
> Link request-confirmation not generated on menus
>
>
> Key: OFBIZ-12278
> URL: https://issues.apache.org/jira/browse/OFBIZ-12278
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Trunk, 17.12.07
>Reporter: Leila Mekika
>Priority: Minor
> Attachments: OFBIZ-12278.patch
>
>
> Menus link with request-confirmation and confirmation message do not generate
> the script that open confirmation
> To reproduce, you can check the link "Status to cancelled" on a created
> payment who does not ask for confirmation while his definition is done:
> {code:java}
> confirmation-message="You want to cancel this payment number
> ${payment.paymentId}?">
>
>
>
> {code}
> ex:
>
> [https://demo-stable.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
> [https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (OFBIZ-12278) Link request-confirmation not generated on menus
Leila Mekika created OFBIZ-12278:
Summary: Link request-confirmation not generated on menus
Key: OFBIZ-12278
URL: https://issues.apache.org/jira/browse/OFBIZ-12278
Project: OFBiz
Issue Type: Improvement
Components: ALL APPLICATIONS
Affects Versions: 17.12.07, Trunk
Reporter: Leila Mekika
Menus link with request-confirmation and confirmation message do not generate
the script that open confirmation
To reproduce, you can check the link "Status to cancelled" on a created payment
who does not ask for confirmation thus his definition is done:
{code:java}
{code}
ex:
[https://demo-stable.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
[https://demo-trunk.ofbiz.apache.org/accounting/control/paymentOverview?paymentId=9000]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-12051) Improve makeRangeCondition in file EntityDateFilterCondition.java
[ https://issues.apache.org/jira/browse/OFBIZ-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12051: - Description: When using makeRangeCondition for a project, it seems that one case is not returned by the generated condition: When we have a value with both from and thrudate greater than given range How to test: * Create an agreement with fromDate = current year start date and endDate = current year end date in [agreement screen|https://localhost:8443/accounting/control/EditAgreement] * Apply OFBIZ-12051-TESTSCREEN.patch to add a "range" field in agreement find screen which allow filtering using makeRangeCondition filter. Got to agreement [find screen|https://localhost:8443/accounting/control/FindAgreement] and enter a range period in current year. * The newly created agreement does not appears in result list * Apply OFBIZ-12051.patch to add a "range" field in agreement find screen which allow filtering using makeRangeCondition filter. * Try again to search [agreements|https://localhost:8443/accounting/control/FindAgreement] with the same range period. * The newly created agreement must appear was: When using makeRangeCondition for a project, it seems that one case is not returned by the generated condition: When we have a value with both from and thrudate greater than given range How to test: * Create an agreement with fromDate = current year start date and endDate = current year end date in [agreement screen|https://localhost:8443/accounting/control/EditAgreement] * Apply OFBIZ-12051-TESTSCREEN.patch to add a "range" field in agreement find screen whiwh allow filtering using makeRangeCondition filter. Got to agreement [find screen|https://localhost:8443/accounting/control/FindAgreement] and enter a range period in current year. * The newly created agreement does not appears in result list * Apply OFBIZ-12051.patch to add a "range" field in agreement find screen which allow filtering using makeRangeCondition filter. * Try again to search [agreements|https://localhost:8443/accounting/control/FindAgreement] with the same range period. * The newly created agreement must appear > Improve makeRangeCondition in file EntityDateFilterCondition.java > - > > Key: OFBIZ-12051 > URL: https://issues.apache.org/jira/browse/OFBIZ-12051 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-12051-TESTSCREEN.txt, OFBIZ-12051.patch > > > When using makeRangeCondition for a project, it seems that one case is not > returned by the generated condition: > When we have a value with both from and thrudate greater than given range > > How to test: > * Create an agreement with fromDate = current year start date and endDate = > current year end date in [agreement > screen|https://localhost:8443/accounting/control/EditAgreement] > * Apply OFBIZ-12051-TESTSCREEN.patch to add a "range" field in agreement > find screen which allow filtering using makeRangeCondition filter. > Got to agreement [find > screen|https://localhost:8443/accounting/control/FindAgreement] and enter a > range period in current year. > * The newly created agreement does not appears in result list > > * Apply OFBIZ-12051.patch to add a "range" field in agreement find screen > which allow filtering using makeRangeCondition filter. > * Try again to search > [agreements|https://localhost:8443/accounting/control/FindAgreement] with the > same range period. > * The newly created agreement must appear -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12051) Improve makeRangeCondition in file EntityDateFilterCondition.java
[ https://issues.apache.org/jira/browse/OFBIZ-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12051: - Description: When using makeRangeCondition for a project, it seems that one case is not returned by the generated condition: When we have a value with both from and thrudate greater than given range How to test: * Create an agreement with fromDate = current year start date and endDate = current year end date in [agreement screen|https://localhost:8443/accounting/control/EditAgreement] * Apply OFBIZ-12051-TESTSCREEN.patch to add a "range" field in agreement find screen whiwh allow filtering using makeRangeCondition filter. Got to agreement [find screen|https://localhost:8443/accounting/control/FindAgreement] and enter a range period in current year. * The newly created agreement does not appears in result list * Apply OFBIZ-12051.patch to add a "range" field in agreement find screen which allow filtering using makeRangeCondition filter. * Try again to search [agreements|https://localhost:8443/accounting/control/FindAgreement] with the same range period. * The newly created agreement must appear was: When using makeRangeCondition for a project, it seems that one case is not returned by the generated condition: When we have a value with both from and thrudate greater than given range How to test: * Create an agreement with fromDate = current year start date and endDate = current year end date in [agreement screen|[https://localhost:8443/accounting/control/EditAgreement].] * Apply OFBIZ-12051-TESTSCREEN.patch to add a "range" field in agreement find screen whiwh allow filtering using makeRangeCondition filter. Got to agreement [find screen|https://localhost:8443/accounting/control/FindAgreement] and enter a range period in current year. * The newly created agreement does not appears in result list * Apply OFBIZ-12051.patch to add a "range" field in agreement find screen whiwh allow filtering using makeRangeCondition filter. * Try again to search [agreements|https://localhost:8443/accounting/control/FindAgreement] with the same range period. * The newly created agreement must appear > Improve makeRangeCondition in file EntityDateFilterCondition.java > - > > Key: OFBIZ-12051 > URL: https://issues.apache.org/jira/browse/OFBIZ-12051 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-12051-TESTSCREEN.txt, OFBIZ-12051.patch > > > When using makeRangeCondition for a project, it seems that one case is not > returned by the generated condition: > When we have a value with both from and thrudate greater than given range > > How to test: > * Create an agreement with fromDate = current year start date and endDate = > current year end date in [agreement > screen|https://localhost:8443/accounting/control/EditAgreement] > * Apply OFBIZ-12051-TESTSCREEN.patch to add a "range" field in agreement > find screen whiwh allow filtering using makeRangeCondition filter. > Got to agreement [find > screen|https://localhost:8443/accounting/control/FindAgreement] and enter a > range period in current year. > * The newly created agreement does not appears in result list > * Apply OFBIZ-12051.patch to add a "range" field in agreement find screen > which allow filtering using makeRangeCondition filter. > * Try again to search > [agreements|https://localhost:8443/accounting/control/FindAgreement] with the > same range period. > * The newly created agreement must appear -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12051) Improve makeRangeCondition in file EntityDateFilterCondition.java
[ https://issues.apache.org/jira/browse/OFBIZ-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12051: - Description: When using makeRangeCondition for a project, it seems that one case is not returned by the generated condition: When we have a value with both from and thrudate greater than given range How to test: * Create an agreement with fromDate = current year start date and endDate = current year end date in [agreement screen|[https://localhost:8443/accounting/control/EditAgreement].] * Apply OFBIZ-12051-TESTSCREEN.patch to add a "range" field in agreement find screen whiwh allow filtering using makeRangeCondition filter. Got to agreement [find screen|https://localhost:8443/accounting/control/FindAgreement] and enter a range period in current year. * The newly created agreement does not appears in result list * Apply OFBIZ-12051.patch to add a "range" field in agreement find screen whiwh allow filtering using makeRangeCondition filter. * Try again to search [agreements|https://localhost:8443/accounting/control/FindAgreement] with the same range period. * The newly created agreement must appear was: When using makeRangeCondition for a project, it seems that one case is not returned by the generated condition: When we have a value with both from and thrudate greater than given range > Improve makeRangeCondition in file EntityDateFilterCondition.java > - > > Key: OFBIZ-12051 > URL: https://issues.apache.org/jira/browse/OFBIZ-12051 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-12051-TESTSCREEN.txt, OFBIZ-12051.patch > > > When using makeRangeCondition for a project, it seems that one case is not > returned by the generated condition: > When we have a value with both from and thrudate greater than given range > > How to test: > * Create an agreement with fromDate = current year start date and endDate = > current year end date in [agreement > screen|[https://localhost:8443/accounting/control/EditAgreement].] > * Apply OFBIZ-12051-TESTSCREEN.patch to add a "range" field in agreement > find screen whiwh allow filtering using makeRangeCondition filter. > Got to agreement [find > screen|https://localhost:8443/accounting/control/FindAgreement] and enter a > range period in current year. > * The newly created agreement does not appears in result list > * Apply OFBIZ-12051.patch to add a "range" field in agreement find screen > whiwh allow filtering using makeRangeCondition filter. > * Try again to search > [agreements|https://localhost:8443/accounting/control/FindAgreement] with the > same range period. > * The newly created agreement must appear -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12051) Improve makeRangeCondition in file EntityDateFilterCondition.java
[ https://issues.apache.org/jira/browse/OFBIZ-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12051: - Attachment: OFBIZ-12051-TESTSCREEN.txt > Improve makeRangeCondition in file EntityDateFilterCondition.java > - > > Key: OFBIZ-12051 > URL: https://issues.apache.org/jira/browse/OFBIZ-12051 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-12051-TESTSCREEN.txt, OFBIZ-12051.patch > > > When using makeRangeCondition for a project, it seems that one case is not > returned by the generated condition: > When we have a value with both from and thrudate greater than given range > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-12051) Improve makeRangeCondition in file EntityDateFilterCondition.java
[ https://issues.apache.org/jira/browse/OFBIZ-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-12051: - Attachment: OFBIZ-12051.patch > Improve makeRangeCondition in file EntityDateFilterCondition.java > - > > Key: OFBIZ-12051 > URL: https://issues.apache.org/jira/browse/OFBIZ-12051 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-12051.patch > > > When using makeRangeCondition for a project, it seems that one case is not > returned by the generated condition: > When we have a value with both from and thrudate greater than given range > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OFBIZ-12051) Improve makeRangeCondition in file EntityDateFilterCondition.java
Leila Mekika created OFBIZ-12051: Summary: Improve makeRangeCondition in file EntityDateFilterCondition.java Key: OFBIZ-12051 URL: https://issues.apache.org/jira/browse/OFBIZ-12051 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Leila Mekika Fix For: Trunk When using makeRangeCondition for a project, it seems that one case is not returned by the generated condition: When we have a value with both from and thrudate greater than given range -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (OFBIZ-11361) Convert PartyServices.xml mini-lang to groovyDSL
[ https://issues.apache.org/jira/browse/OFBIZ-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055917#comment-17055917 ] Leila Mekika edited comment on OFBIZ-11361 at 3/10/20, 1:01 PM: Hello [~sberg] and [~nmalin] . For information, I just attached a patch to this Jira for the migration of PartyServices.xml You're welcome to review it was (Author: mleila): Hello [~sberg] and [~nmalin] . For information, I just attached a patch to this Jira for the migration of PartyServices.xml > Convert PartyServices.xml mini-lang to groovyDSL > > > Key: OFBIZ-11361 > URL: https://issues.apache.org/jira/browse/OFBIZ-11361 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Minor > Labels: groovy, mini-lang > Attachments: OFBIZ-11361.patch > > > Migration of file PartyServices.xml to groovy > h4. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11361) Convert PartyServices.xml mini-lang to groovyDSL
[ https://issues.apache.org/jira/browse/OFBIZ-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055917#comment-17055917 ] Leila Mekika commented on OFBIZ-11361: -- Hello [~sberg] and [~nmalin] . For information, I just attached a patch to this Jira for the migration of PartyServices.xml > Convert PartyServices.xml mini-lang to groovyDSL > > > Key: OFBIZ-11361 > URL: https://issues.apache.org/jira/browse/OFBIZ-11361 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Minor > Labels: groovy, mini-lang > Attachments: OFBIZ-11361.patch > > > Migration of file PartyServices.xml to groovy > h4. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11361) Convert PartyServices.xml mini-lang to groovyDSL
[ https://issues.apache.org/jira/browse/OFBIZ-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-11361: - Attachment: OFBIZ-11361.patch > Convert PartyServices.xml mini-lang to groovyDSL > > > Key: OFBIZ-11361 > URL: https://issues.apache.org/jira/browse/OFBIZ-11361 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Minor > Labels: groovy, mini-lang > Attachments: OFBIZ-11361.patch > > > Migration of file PartyServices.xml to groovy > h4. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11211) Fix multi modal opening
[ https://issues.apache.org/jira/browse/OFBIZ-11211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954662#comment-16954662 ] Leila Mekika commented on OFBIZ-11211: -- Hello [~jleroux] , [~dcarl] I would like to suggest an update to simplify a little bit the current code. You can see this in the attached patch 'OFBIZ-11211-V2': what do you think of it ? > Fix multi modal opening > --- > > Key: OFBIZ-11211 > URL: https://issues.apache.org/jira/browse/OFBIZ-11211 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Demus Carl >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 17.12.01, 18.12.01 > > Attachments: OFBIZ-11211-V2.patch, OFBIZ-11211.patch > > > The issue is that when closing the modal the div inside html dom is not > removed. Then opening a second time create another identical div. Since a > lookup is based on an unique id, this id is no more unique... > > This issue is link to my previous issue OFBIZ-11210 > Attached patch fix the issue -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-11211) Fix multi modal opening
[ https://issues.apache.org/jira/browse/OFBIZ-11211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-11211: - Attachment: OFBIZ-11211-V2.patch > Fix multi modal opening > --- > > Key: OFBIZ-11211 > URL: https://issues.apache.org/jira/browse/OFBIZ-11211 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Demus Carl >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 17.12.01, 18.12.01 > > Attachments: OFBIZ-11211-V2.patch, OFBIZ-11211.patch > > > The issue is that when closing the modal the div inside html dom is not > removed. Then opening a second time create another identical div. Since a > lookup is based on an unique id, this id is no more unique... > > This issue is link to my previous issue OFBIZ-11210 > Attached patch fix the issue -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11179) Change current view-link requirement to allow use of entity-condition only in view-entities
[ https://issues.apache.org/jira/browse/OFBIZ-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16943381#comment-16943381 ] Leila Mekika commented on OFBIZ-11179: -- Thanks Jacques ! > Change current view-link requirement to allow use of entity-condition only > in view-entities > > > Key: OFBIZ-11179 > URL: https://issues.apache.org/jira/browse/OFBIZ-11179 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: ExampleWithoutKeyMap.xml, OFBIZ-11179.patch > > > To explain the subject, i will give an example encountered recently: > We used, for a customer project, a view with Agreement, Virtual and Variant > product entities and where the agreement can be attached to a virtual OR a > variant product. > So to make a view returning Variant Product, Virtual Product AND Agreement > informations, i could not create a view, as the key-map link is mandatory and > made it impossible. > I can not have an alternative relation to the same entity so we have to > duplicate member-entity and an alternative relation path. The result is a > complicated and ugly entity-view > I think this can have been much simpler if i could have done it directly > through the entity-condition (see the AGPA/PDTA view link in attached file > ExampleWithoutKeyMap.xml) > So the purpose of this jira is to add the possibility to create a view-link > without key map, if there is an entity-condition. > You can test by applying the given patch and add the entity view from > attached file ExampleWithoutKeyMap.xml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OFBIZ-11179) Change current view-link requirement to allow use of entity-condition only in view-entities
[ https://issues.apache.org/jira/browse/OFBIZ-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922311#comment-16922311 ] Leila Mekika commented on OFBIZ-11179: -- Hello [~jacques.le.roux] , thanks for the test. I added it in applications/datamodel/entitydef/product-entitymodel.xml (sorry, the package-name was not clear) > Change current view-link requirement to allow use of entity-condition only > in view-entities > > > Key: OFBIZ-11179 > URL: https://issues.apache.org/jira/browse/OFBIZ-11179 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: ExampleWithoutKeyMap.xml, OFBIZ-11179.patch > > > To explain the subject, i will give an example encountered recently: > We used, for a customer project, a view with Agreement, Virtual and Variant > product entities and where the agreement can be attached to a virtual OR a > variant product. > So to make a view returning Variant Product, Virtual Product AND Agreement > informations, i could not create a view, as the key-map link is mandatory and > made it impossible. > I can not have an alternative relation to the same entity so we have to > duplicate member-entity and an alternative relation path. The result is a > complicated and ugly entity-view > I think this can have been much simpler if i could have done it directly > through the entity-condition (see the AGPA/PDTA view link in attached file > ExampleWithoutKeyMap.xml) > So the purpose of this jira is to add the possibility to create a view-link > without key map, if there is an entity-condition. > You can test by applying the given patch and add the entity view from > attached file ExampleWithoutKeyMap.xml -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (OFBIZ-11179) Change current view-link requirement to allow use of entity-condition only in view-entities
[ https://issues.apache.org/jira/browse/OFBIZ-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-11179: - Description: To explain the subject, i will give an example encountered recently: We used, for a customer project, a view with Agreement, Virtual and Variant product entities and where the agreement can be attached to a virtual OR a variant product. So to make a view returning Variant Product, Virtual Product AND Agreement informations, i could not create a view, as the key-map link is mandatory and made it impossible. I can not have an alternative relation to the same entity so we have to duplicate member-entity and an alternative relation path. The result is a complicated and ugly entity-view I think this can have been much simpler if i could have done it directly through the entity-condition (see the AGPA/PDTA view link in attached file ExampleWithoutKeyMap.xml) So the purpose of this jira is to add the possibility to create a view-link without key map, if there is an entity-condition. You can test by applying the given patch and add the entity view from attached file ExampleWithoutKeyMap.xml was: To explain the subject, i will give an example encountered recently: We used, for a customer project, a view with Agreement, Virtual and Variant product entities and where the agreement can be attached to a virtual OR a variant product. So to make a view returning Variant Product, Virtual Product AND Agreement informations, i could not create a view, as the key-map link is mandatory and made it impossible. I can not have an alternative relation to the same entity so we have to duplicate member-entity and an alternative relation path (see attached file ExampleWithKeyMap.xml) And as the coalesce is not an existing function, it require to update the framework. The result is a complicated and ugly entity-view I think this can have been much simpler if i could have done it directly through the entity-condition (see the AGPA/PDTA view link in attached file ExampleWithoutKeyMap.xml) So the purpose of this jira is to add the possibility to create a view-link without key map, if there is an entity-condition. You can test by applying the given patch and add the entity view from attached file ExampleWithoutKeyMap.xml > Change current view-link requirement to allow use of entity-condition only > in view-entities > > > Key: OFBIZ-11179 > URL: https://issues.apache.org/jira/browse/OFBIZ-11179 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: ExampleWithoutKeyMap.xml, OFBIZ-11179.patch > > > To explain the subject, i will give an example encountered recently: > We used, for a customer project, a view with Agreement, Virtual and Variant > product entities and where the agreement can be attached to a virtual OR a > variant product. > So to make a view returning Variant Product, Virtual Product AND Agreement > informations, i could not create a view, as the key-map link is mandatory and > made it impossible. > I can not have an alternative relation to the same entity so we have to > duplicate member-entity and an alternative relation path. The result is a > complicated and ugly entity-view > I think this can have been much simpler if i could have done it directly > through the entity-condition (see the AGPA/PDTA view link in attached file > ExampleWithoutKeyMap.xml) > So the purpose of this jira is to add the possibility to create a view-link > without key map, if there is an entity-condition. > You can test by applying the given patch and add the entity view from > attached file ExampleWithoutKeyMap.xml -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (OFBIZ-11179) Change current view-link requirement to allow use of entity-condition only in view-entities
[ https://issues.apache.org/jira/browse/OFBIZ-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-11179: - Description: To explain the subject, i will give an example encountered recently: We used, for a customer project, a view with Agreement, Virtual and Variant product entities and where the agreement can be attached to a virtual OR a variant product. So to make a view returning Variant Product, Virtual Product AND Agreement informations, i could not create a view, as the key-map link is mandatory and made it impossible. I can not have an alternative relation to the same entity so we have to duplicate member-entity and an alternative relation path (see attached file ExampleWithKeyMap.xml) And as the coalesce is not an existing function, it require to update the framework. The result is a complicated and ugly entity-view I think this can have been much simpler if i could have done it directly through the entity-condition (see the AGPA/PDTA view link in attached file ExampleWithoutKeyMap.xml) So the purpose of this jira is to add the possibility to create a view-link without key map, if there is an entity-condition. You can test by applying the given patch and add the entity view from attached file ExampleWithoutKeyMap.xml was: To explain the subject, i will give an example encountered recently: We used, for a customer project, a view with Agreement, Virtual and Variant product entities and where the agreement can be attached to a virtual OR a variant product. So to make a view returning Variant Product, Virtual Product AND Agreement informations, i could not create a view, as the key-map link is mandatory and made it impossible. I can not have an alternative relation to the same entity so we have to duplicate member-entity and an alternative relation path (see attached file ExampleWithKeyMap.xml) And as the coalesce is not an existing function, it require to update the framework. The result is a complicated and ugly entity-view I think this can have been much simpler if i could have done it directly through the entity-condition (see the AGPA/PDTA view link in attached file ExampleWithoutKeyMap.xml) So the purpose of this jira is to add the possibility to create a view-link without key map, only if there is an entity-condition. You can test by applying the given patch and add the entity view from attached file ExampleWithoutKeyMap.xml > Change current view-link requirement to allow use of entity-condition only > in view-entities > > > Key: OFBIZ-11179 > URL: https://issues.apache.org/jira/browse/OFBIZ-11179 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: ExampleWithKeyMap.xml, ExampleWithoutKeyMap.xml, > OFBIZ-11179.patch > > > To explain the subject, i will give an example encountered recently: > We used, for a customer project, a view with Agreement, Virtual and Variant > product entities and where the agreement can be attached to a virtual OR a > variant product. > So to make a view returning Variant Product, Virtual Product AND Agreement > informations, i could not create a view, as the key-map link is mandatory and > made it impossible. > I can not have an alternative relation to the same entity so we have to > duplicate member-entity and an alternative relation path (see attached file > ExampleWithKeyMap.xml) > And as the coalesce is not an existing function, it require to update the > framework. The result is a complicated and ugly entity-view > I think this can have been much simpler if i could have done it directly > through the entity-condition (see the AGPA/PDTA view link in attached file > ExampleWithoutKeyMap.xml) > So the purpose of this jira is to add the possibility to create a view-link > without key map, if there is an entity-condition. > You can test by applying the given patch and add the entity view from > attached file ExampleWithoutKeyMap.xml -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (OFBIZ-11179) Change current view-link requirement to allow use of entity-condition only in view-entities
[ https://issues.apache.org/jira/browse/OFBIZ-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-11179: - Attachment: OFBIZ-11179.patch > Change current view-link requirement to allow use of entity-condition only > in view-entities > > > Key: OFBIZ-11179 > URL: https://issues.apache.org/jira/browse/OFBIZ-11179 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: ExampleWithKeyMap.xml, ExampleWithoutKeyMap.xml, > OFBIZ-11179.patch > > > To explain the subject, i will give an example encountered recently: > We used, for a customer project, a view with Agreement, Virtual and Variant > product entities and where the agreement can be attached to a virtual OR a > variant product. > So to make a view returning Variant Product, Virtual Product AND Agreement > informations, i could not create a view, as the key-map link is mandatory and > made it impossible. > I can not have an alternative relation to the same entity so we have to > duplicate member-entity and an alternative relation path (see attached file > ExampleWithKeyMap.xml) > And as the coalesce is not an existing function, it require to update the > framework. The result is a complicated and ugly entity-view > I think this can have been much simpler if i could have done it directly > through the entity-condition (see the AGPA/PDTA view link in attached file > ExampleWithoutKeyMap.xml) > So the purpose of this jira is to add the possibility to create a view-link > without key map, only if there is an entity-condition. > You can test by applying the given patch and add the entity view from > attached file ExampleWithoutKeyMap.xml -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (OFBIZ-11179) Change current view-link requirement to allow use of entity-condition only in view-entities
Leila Mekika created OFBIZ-11179: Summary: Change current view-link requirement to allow use of entity-condition only in view-entities Key: OFBIZ-11179 URL: https://issues.apache.org/jira/browse/OFBIZ-11179 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Leila Mekika To explain the subject, i will give an example encountered recently: We used, for a customer project, a view with Agreement, Virtual and Variant product entities and where the agreement can be attached to a virtual OR a variant product. So to make a view returning Variant Product, Virtual Product AND Agreement informations, i could not create a view, as the key-map link is mandatory and made it impossible. I can not have an alternative relation to the same entity so we have to duplicate member-entity and an alternative relation path (see attached file ExampleWithKeyMap.xml) And as the coalesce is not an existing function, it require to update the framework. The result is a complicated and ugly entity-view I think this can have been much simpler if i could have done it directly through the entity-condition (see the AGPA/PDTA view link in attached file ExampleWithoutKeyMap.xml) So the purpose of this jira is to add the possibility to create a view-link without key map, only if there is an entity-condition. You can test by applying the given patch and add the entity view from attached file ExampleWithoutKeyMap.xml -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (OFBIZ-11179) Change current view-link requirement to allow use of entity-condition only in view-entities
[ https://issues.apache.org/jira/browse/OFBIZ-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-11179: - Attachment: ExampleWithoutKeyMap.xml ExampleWithKeyMap.xml > Change current view-link requirement to allow use of entity-condition only > in view-entities > > > Key: OFBIZ-11179 > URL: https://issues.apache.org/jira/browse/OFBIZ-11179 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: ExampleWithKeyMap.xml, ExampleWithoutKeyMap.xml > > > To explain the subject, i will give an example encountered recently: > We used, for a customer project, a view with Agreement, Virtual and Variant > product entities and where the agreement can be attached to a virtual OR a > variant product. > So to make a view returning Variant Product, Virtual Product AND Agreement > informations, i could not create a view, as the key-map link is mandatory and > made it impossible. > I can not have an alternative relation to the same entity so we have to > duplicate member-entity and an alternative relation path (see attached file > ExampleWithKeyMap.xml) > And as the coalesce is not an existing function, it require to update the > framework. The result is a complicated and ugly entity-view > I think this can have been much simpler if i could have done it directly > through the entity-condition (see the AGPA/PDTA view link in attached file > ExampleWithoutKeyMap.xml) > So the purpose of this jira is to add the possibility to create a view-link > without key map, only if there is an entity-condition. > You can test by applying the given patch and add the entity view from > attached file ExampleWithoutKeyMap.xml -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (OFBIZ-10692) Groovy DSL runService Exception Management
[
https://issues.apache.org/jira/browse/OFBIZ-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737285#comment-16737285
]
Leila Mekika edited comment on OFBIZ-10692 at 1/11/19 8:27 AM:
---
Hello [~jacques.le.roux],
Thanks for the test. I only think of compilation :) but i didn't check with the
current trunk version.
For information, we also are adding an integration test to secure this
improvement in case of a groovy lib update. We will add it to the patch when it
will be ready
> Groovy DSL runService Exception Management
> --
>
> Key: OFBIZ-10692
> URL: https://issues.apache.org/jira/browse/OFBIZ-10692
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Leila Mekika
>Assignee: Gil Portenseigne
>Priority: Minor
> Labels: patch
> Attachments: OFBIZ-10692-TEST.patch, OFBIZ-10692.patch
>
>
> Like discussed in thread :
> [https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
>
> This ticket try to improve the way that errors are rendered when using {{run
> service}} groovy DSL method.
>
> To reproduce and test patch:
> apply the attached patch [^OFBIZ-10692-TEST.patch] (it adds a control on
> createUomConversionDated service) and try to create a conversion rate with a
> fromDate greater than the thruDate here:
> https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company
>
> You should then see the following error:
> The Following Errors Occurred: Error calling event:
> org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
> (org.apache.ofbiz.service.ExecutionServiceException: Through date can't be
> same or smaller than from date)
>
> With [^OFBIZ-10692.patch] update, the error must be displayed like:
> The Following Errors Occurred: Through date can't be same or smaller
> than from date
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10722) Date-find error when used in two forms of a same screen
[ https://issues.apache.org/jira/browse/OFBIZ-10722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724096#comment-16724096 ] Leila Mekika commented on OFBIZ-10722: -- Thanks ! > Date-find error when used in two forms of a same screen > --- > > Key: OFBIZ-10722 > URL: https://issues.apache.org/jira/browse/OFBIZ-10722 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Leila Mekika >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10722.patch > > > When we have more than one form, in a screen, that use a date-find field, the > second date-find picker is not working. > To reproduce, you can add a new form with a date-find and call it below > FindInvoices in FindInvoices screen > Then load page [https://localhost:8443/accounting/control/findInvoices] . You > should see that there is no picker on ne second date-find > > The patch adds an id that allow renderDateFindField macro script to work for > both fields -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10722) Date-find error when used in two forms of a same screen
[ https://issues.apache.org/jira/browse/OFBIZ-10722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-10722: - Attachment: OFBIZ-10722.patch > Date-find error when used in two forms of a same screen > --- > > Key: OFBIZ-10722 > URL: https://issues.apache.org/jira/browse/OFBIZ-10722 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Leila Mekika >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10722.patch > > > When we have more than one form, in a screen, that use a date-find field, the > second date-find picker is not working. > To reproduce, you can add a new form with a date-find and call it below > FindInvoices in FindInvoices screen > Then load page [https://localhost:8443/accounting/control/findInvoices] . You > should see that there is no picker on ne second date-find > > The patch adds an id that allow renderDateFindField macro script to work for > both fields -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10722) Date-find error when used in two forms of a same screen
[ https://issues.apache.org/jira/browse/OFBIZ-10722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-10722: - Description: When we have more than one form, in a screen, that use a date-find field, the second date-find picker is not working. To reproduce, you can add a new form with a date-find and call it below FindInvoices in FindInvoices screen Then load page [https://localhost:8443/accounting/control/findInvoices] . You should see that there is no picker on ne second date-find The patch adds an id that allow renderDateFindField macro script to work for both fields was: When we have more than one form, in a screen, that use a date-find field, the second date-find picker is not working. To reproduce, you can duplicate the form FindInvoices in FindInvoices screen and load page [https://localhost:8443/accounting/control/findInvoices] The patch adds an id that allow renderDateFindField macro script to work for both fields > Date-find error when used in two forms of a same screen > --- > > Key: OFBIZ-10722 > URL: https://issues.apache.org/jira/browse/OFBIZ-10722 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Leila Mekika >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10722.patch > > > When we have more than one form, in a screen, that use a date-find field, the > second date-find picker is not working. > To reproduce, you can add a new form with a date-find and call it below > FindInvoices in FindInvoices screen > Then load page [https://localhost:8443/accounting/control/findInvoices] . You > should see that there is no picker on ne second date-find > > The patch adds an id that allow renderDateFindField macro script to work for > both fields -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10722) Date-find error when used in two forms of a same screen
[ https://issues.apache.org/jira/browse/OFBIZ-10722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-10722: - Description: When we have more than one form, in a screen, that use a date-find field, the second date-find picker is not working. To reproduce, you can duplicate the form FindInvoices in FindInvoices screen and load page [https://localhost:8443/accounting/control/findInvoices] The patch adds an id that allow renderDateFindField macro script to work for both fields was: When we have more than one form, in a screen, that use a date-find field, the second date-find picker is not working. The patch adds an id that allow renderDateFindField macro script to work for both fields > Date-find error when used in two forms of a same screen > --- > > Key: OFBIZ-10722 > URL: https://issues.apache.org/jira/browse/OFBIZ-10722 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Reporter: Leila Mekika >Priority: Minor > Fix For: Trunk > > > When we have more than one form, in a screen, that use a date-find field, the > second date-find picker is not working. > To reproduce, you can duplicate the form FindInvoices in FindInvoices screen > and load page [https://localhost:8443/accounting/control/findInvoices] > > The patch adds an id that allow renderDateFindField macro script to work for > both fields -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10722) Date-find error when used in two forms of a same screen
Leila Mekika created OFBIZ-10722: Summary: Date-find error when used in two forms of a same screen Key: OFBIZ-10722 URL: https://issues.apache.org/jira/browse/OFBIZ-10722 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Reporter: Leila Mekika Fix For: Trunk When we have more than one form, in a screen, that use a date-find field, the second date-find picker is not working. The patch adds an id that allow renderDateFindField macro script to work for both fields -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10692) Groovy DSL runService Exception Management
[
https://issues.apache.org/jira/browse/OFBIZ-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-10692:
-
Attachment: OFBIZ-10692-TEST.patch
> Groovy DSL runService Exception Management
> --
>
> Key: OFBIZ-10692
> URL: https://issues.apache.org/jira/browse/OFBIZ-10692
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Leila Mekika
>Priority: Minor
> Labels: patch
> Attachments: OFBIZ-10692-TEST.patch, OFBIZ-10692.patch
>
>
> Like discussed in thread :
> [https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
>
> This ticket try to improve the way that errors are rendered when using \{run
> service} groovy DSL method.
>
> To reproduce and test patch:
> apply the attached patch [^OFBIZ-10692-TEST.patch] (it adds a control on
> createUomConversionDated service) and try to create a conversion rate with a
> fromDate greater than the thruDate here:
>
> [https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company]
>
> You should then see the following error:
> The Following Errors Occurred: Error calling event:
> org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
> (org.apache.ofbiz.service.ExecutionServiceException: Through date can't be
> same or smaller than from date)
>
> With OFBIZ-10692.patch update, the error must be displayed like:
> The Following Errors Occurred: Through date can't be same or smaller
> than from date
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10692) Groovy DSL runService Exception Management
[
https://issues.apache.org/jira/browse/OFBIZ-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-10692:
-
Attachment: (was: OFBIZ-10692-TEST.patch)
> Groovy DSL runService Exception Management
> --
>
> Key: OFBIZ-10692
> URL: https://issues.apache.org/jira/browse/OFBIZ-10692
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Leila Mekika
>Priority: Minor
> Labels: patch
> Attachments: OFBIZ-10692-TEST.patch, OFBIZ-10692.patch
>
>
> Like discussed in thread :
> [https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
>
> This ticket try to improve the way that errors are rendered when using \{run
> service} groovy DSL method.
>
> To reproduce and test patch:
> apply the attached patch [^OFBIZ-10692-TEST.patch] (it adds a control on
> createUomConversionDated service) and try to create a conversion rate with a
> fromDate greater than the thruDate here:
>
> [https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company]
>
> You should then see the following error:
> The Following Errors Occurred: Error calling event:
> org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
> (org.apache.ofbiz.service.ExecutionServiceException: Through date can't be
> same or smaller than from date)
>
> With OFBIZ-10692.patch update, the error must be displayed like:
> The Following Errors Occurred: Through date can't be same or smaller
> than from date
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10692) Groovy DSL runService Exception Management
[
https://issues.apache.org/jira/browse/OFBIZ-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-10692:
-
Attachment: OFBIZ-10692-TEST.patch
OFBIZ-10692.patch
> Groovy DSL runService Exception Management
> --
>
> Key: OFBIZ-10692
> URL: https://issues.apache.org/jira/browse/OFBIZ-10692
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Leila Mekika
>Priority: Minor
> Labels: patch
> Attachments: OFBIZ-10692-TEST.patch, OFBIZ-10692.patch
>
>
> Like discussed in thread :
> [https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
>
> This ticket try to improve the way that errors are rendered when using \{run
> service} groovy DSL method.
>
> To reproduce and test patch:
> apply the attached patch 'OFBIZ-10692_test.patch' (it adds a control on
> createUomConversionDated service) and try to create a conversion rate with a
> fromDate greater than the thruDate here:
>
> [https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company]
>
> You should then see the following error:
> The Following Errors Occurred: Error calling event:
> org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
> (org.apache.ofbiz.service.ExecutionServiceException: Through date can't be
> same or smaller than from date)
>
> With OFBIZ-10692.patch update, the error must be displayed like:
> The Following Errors Occurred: Through date can't be same or smaller
> than from date
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10692) Groovy DSL runService Exception Management
[
https://issues.apache.org/jira/browse/OFBIZ-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-10692:
-
Description:
Like discussed in thread :
[https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
This ticket try to improve the way that errors are rendered when using \{run
service} groovy DSL method.
To reproduce and test patch:
apply the attached patch [^OFBIZ-10692-TEST.patch] (it adds a control on
createUomConversionDated service) and try to create a conversion rate with a
fromDate greater than the thruDate here:
[https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company]
You should then see the following error:
The Following Errors Occurred: Error calling event:
org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
(org.apache.ofbiz.service.ExecutionServiceException: Through date can't be same
or smaller than from date)
With OFBIZ-10692.patch update, the error must be displayed like:
The Following Errors Occurred: Through date can't be same or smaller than
from date
was:
Like discussed in thread :
[https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
This ticket try to improve the way that errors are rendered when using \{run
service} groovy DSL method.
To reproduce and test patch:
apply the attached patch 'OFBIZ-10692_test.patch' (it adds a control on
createUomConversionDated service) and try to create a conversion rate with a
fromDate greater than the thruDate here:
[https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company]
You should then see the following error:
The Following Errors Occurred: Error calling event:
org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
(org.apache.ofbiz.service.ExecutionServiceException: Through date can't be same
or smaller than from date)
With OFBIZ-10692.patch update, the error must be displayed like:
The Following Errors Occurred: Through date can't be same or smaller than
from date
> Groovy DSL runService Exception Management
> --
>
> Key: OFBIZ-10692
> URL: https://issues.apache.org/jira/browse/OFBIZ-10692
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Leila Mekika
>Priority: Minor
> Labels: patch
> Attachments: OFBIZ-10692-TEST.patch, OFBIZ-10692.patch
>
>
> Like discussed in thread :
> [https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
>
> This ticket try to improve the way that errors are rendered when using \{run
> service} groovy DSL method.
>
> To reproduce and test patch:
> apply the attached patch [^OFBIZ-10692-TEST.patch] (it adds a control on
> createUomConversionDated service) and try to create a conversion rate with a
> fromDate greater than the thruDate here:
>
> [https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company]
>
> You should then see the following error:
> The Following Errors Occurred: Error calling event:
> org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
> (org.apache.ofbiz.service.ExecutionServiceException: Through date can't be
> same or smaller than from date)
>
> With OFBIZ-10692.patch update, the error must be displayed like:
> The Following Errors Occurred: Through date can't be same or smaller
> than from date
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10692) Groovy DSL runService Exception Management
[
https://issues.apache.org/jira/browse/OFBIZ-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-10692:
-
Attachment: (was: OFBIZ-10692.patch)
> Groovy DSL runService Exception Management
> --
>
> Key: OFBIZ-10692
> URL: https://issues.apache.org/jira/browse/OFBIZ-10692
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Leila Mekika
>Priority: Minor
> Labels: patch
>
> Like discussed in thread :
> [https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
>
> This ticket try to improve the way that errors are rendered when using \{run
> service} groovy DSL method.
>
> To reproduce and test patch:
> apply the attached patch 'OFBIZ-10692_test.patch' (it adds a control on
> createUomConversionDated service) and try to create a conversion rate with a
> fromDate greater than the thruDate here:
>
> [https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company]
>
> You should then see the following error:
> The Following Errors Occurred: Error calling event:
> org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
> (org.apache.ofbiz.service.ExecutionServiceException: Through date can't be
> same or smaller than from date)
>
> With OFBIZ-10692.patch update, the error must be displayed like:
> The Following Errors Occurred: Through date can't be same or smaller
> than from date
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10692) Groovy DSL runService Exception Management
[
https://issues.apache.org/jira/browse/OFBIZ-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-10692:
-
Labels: patch (was: )
> Groovy DSL runService Exception Management
> --
>
> Key: OFBIZ-10692
> URL: https://issues.apache.org/jira/browse/OFBIZ-10692
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Leila Mekika
>Priority: Minor
> Labels: patch
> Attachments: OFBIZ-10692.patch
>
>
> Like discussed in thread :
> [https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
>
> This ticket try to improve the way that errors are rendered when using \{run
> service} groovy DSL method.
>
> To reproduce and test patch:
> apply the attached patch 'OFBIZ-10692.patch' (it adds a control on
> createUomConversionDated service) and try to create a conversion rate with a
> fromDate greater than the thruDate here:
> [https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company]
>
> You should then see the following error:
> The Following Errors Occurred: Error calling event:
> org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
> (org.apache.ofbiz.service.ExecutionServiceException: Through date can't be
> same or smaller than from date)
>
> With OFBIZ-10692.patch update, the error must be displayed like:
> The Following Errors Occurred: Through date can't be same or smaller than
> from date
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10692) Groovy DSL runService Exception Management
[
https://issues.apache.org/jira/browse/OFBIZ-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-10692:
-
Description:
Like discussed in thread :
[https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
This ticket try to improve the way that errors are rendered when using \{run
service} groovy DSL method.
To reproduce and test patch:
apply the attached patch 'OFBIZ-10692.patch' (it adds a control on
createUomConversionDated service) and try to create a conversion rate with a
fromDate greater than the thruDate here:
[https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company]
You should then see the following error:
The Following Errors Occurred: Error calling event:
org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
(org.apache.ofbiz.service.ExecutionServiceException: Through date can't be same
or smaller than from date)
With OFBIZ-10692.patch update, the error must be displayed like:
The Following Errors Occurred: Through date can't be same or smaller than
from date
was:
Like discussed in thread :
[https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
This ticket try to improve the way that errors are rendered when using \{run
service} groovy DSL method.
> Groovy DSL runService Exception Management
> --
>
> Key: OFBIZ-10692
> URL: https://issues.apache.org/jira/browse/OFBIZ-10692
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Leila Mekika
>Priority: Major
> Attachments: OFBIZ-10692.patch
>
>
> Like discussed in thread :
> [https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
>
> This ticket try to improve the way that errors are rendered when using \{run
> service} groovy DSL method.
>
> To reproduce and test patch:
> apply the attached patch 'OFBIZ-10692.patch' (it adds a control on
> createUomConversionDated service) and try to create a conversion rate with a
> fromDate greater than the thruDate here:
> [https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company]
>
> You should then see the following error:
> The Following Errors Occurred: Error calling event:
> org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
> (org.apache.ofbiz.service.ExecutionServiceException: Through date can't be
> same or smaller than from date)
>
> With OFBIZ-10692.patch update, the error must be displayed like:
> The Following Errors Occurred: Through date can't be same or smaller than
> from date
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10692) Groovy DSL runService Exception Management
[
https://issues.apache.org/jira/browse/OFBIZ-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-10692:
-
Attachment: OFBIZ-10692.patch
> Groovy DSL runService Exception Management
> --
>
> Key: OFBIZ-10692
> URL: https://issues.apache.org/jira/browse/OFBIZ-10692
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Leila Mekika
>Priority: Major
> Attachments: OFBIZ-10692.patch
>
>
> Like discussed in thread :
> [https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
>
> This ticket try to improve the way that errors are rendered when using \{run
> service} groovy DSL method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10692) Groovy DSL runService Exception Management
[
https://issues.apache.org/jira/browse/OFBIZ-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leila Mekika updated OFBIZ-10692:
-
Priority: Minor (was: Major)
> Groovy DSL runService Exception Management
> --
>
> Key: OFBIZ-10692
> URL: https://issues.apache.org/jira/browse/OFBIZ-10692
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Leila Mekika
>Priority: Minor
> Attachments: OFBIZ-10692.patch
>
>
> Like discussed in thread :
> [https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
>
> This ticket try to improve the way that errors are rendered when using \{run
> service} groovy DSL method.
>
> To reproduce and test patch:
> apply the attached patch 'OFBIZ-10692.patch' (it adds a control on
> createUomConversionDated service) and try to create a conversion rate with a
> fromDate greater than the thruDate here:
> [https://localhost:8443/accounting/control/viewFXConversions?organizationPartyId=Company]
>
> You should then see the following error:
> The Following Errors Occurred: Error calling event:
> org.apache.ofbiz.webapp.event.EventHandlerException: Service invocation error
> (org.apache.ofbiz.service.ExecutionServiceException: Through date can't be
> same or smaller than from date)
>
> With OFBIZ-10692.patch update, the error must be displayed like:
> The Following Errors Occurred: Through date can't be same or smaller than
> from date
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OFBIZ-10692) Groovy DSL runService Exception Management
Leila Mekika created OFBIZ-10692:
Summary: Groovy DSL runService Exception Management
Key: OFBIZ-10692
URL: https://issues.apache.org/jira/browse/OFBIZ-10692
Project: OFBiz
Issue Type: Improvement
Affects Versions: Trunk
Reporter: Leila Mekika
Like discussed in thread :
[https://lists.apache.org/thread.html/5a8e1caed0bcf29889c6b88ec1916947cf092d6f99d7dfe27cbef8c0@%3Cdev.ofbiz.apache.org%3E]
This ticket try to improve the way that errors are rendered when using \{run
service} groovy DSL method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10340) Changing visual them from product store overrides context parameter
[ https://issues.apache.org/jira/browse/OFBIZ-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453782#comment-16453782 ] Leila Mekika commented on OFBIZ-10340: -- Hello [~suraj.khurana], it seems to be because Lookup display override session attribute _LAST_VIEW_NAME_. Request selectTheme is then trying to redirect to LookupPartyName > Changing visual them from product store overrides context parameter > --- > > Key: OFBIZ-10340 > URL: https://issues.apache.org/jira/browse/OFBIZ-10340 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Upcoming Branch >Reporter: Suraj Khurana >Assignee: Suraj Khurana >Priority: Major > > Steps to regenerate: > Go to product store detail page from catalog menu. > Change visual theme and press Update. > Due to change in visual theme of ecommerce, context parameter gets updated > and page renders with no theme. > Context parameter should not gets override and Updating visual them should > result in proper detail page as required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-7741) Address scope peculiarities within search/find functionality of projectmgr
[ https://issues.apache.org/jira/browse/OFBIZ-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453723#comment-16453723 ] Leila Mekika commented on OFBIZ-7741: - Hello [~pfm.smits], I tried to reproduce in a recent trunk and didn't encounter the problem. I tested it with DemoEmployee1 and DemoEmployee3 who can only see their project Do you always encounter the problem ? And if yes, can you give us details (user, etc) so that we can reproduce ? Thanks > Address scope peculiarities within search/find functionality of projectmgr > -- > > Key: OFBIZ-7741 > URL: https://issues.apache.org/jira/browse/OFBIZ-7741 > Project: OFBiz > Issue Type: Improvement > Components: projectmgr >Reporter: Pierre Smits >Priority: Critical > > Currently the search/find functions in the projectmgr component also > retrieves projects a user is not a participant in. This is especially > critical regarding projects with scope 'WES_PRIVATE - private' or > 'WES_CONFIDENTIAL - confidential'. > These project may only be search for/found by users that are exlicit > participants of the projects. This over ruless the generic permissions of > 'PROJECTMGR_ADMIN' or 'PROJECTMGR_VIEW'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9986) Convert InvoiceServices.xml mini lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-9986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-9986: Attachment: OFBIZ-9986.patch > Convert InvoiceServices.xml mini lang to groovy > --- > > Key: OFBIZ-9986 > URL: https://issues.apache.org/jira/browse/OFBIZ-9986 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: OFBIZ-9986.patch > > > Migration of file InvoiceServices.xml to groovy -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9986) Convert InvoiceServices.xml mini lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-9986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257276#comment-16257276 ] Leila Mekika commented on OFBIZ-9986: - The patch is a first version. For now, it convert getNextInvoiceId, invoiceSequenceEnforced and invoiceSequenceRestart > Convert InvoiceServices.xml mini lang to groovy > --- > > Key: OFBIZ-9986 > URL: https://issues.apache.org/jira/browse/OFBIZ-9986 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: OFBIZ-9986.patch > > > Migration of file InvoiceServices.xml to groovy -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9986) Convert InvoiceServices.xml mini lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-9986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-9986: Issue Type: Sub-task (was: Task) Parent: OFBIZ-9350 > Convert InvoiceServices.xml mini lang to groovy > --- > > Key: OFBIZ-9986 > URL: https://issues.apache.org/jira/browse/OFBIZ-9986 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > > Migration of file InvoiceServices.xml to groovy -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9986) Convert InvoiceServices.xml mini lang to groovy
Leila Mekika created OFBIZ-9986: --- Summary: Convert InvoiceServices.xml mini lang to groovy Key: OFBIZ-9986 URL: https://issues.apache.org/jira/browse/OFBIZ-9986 Project: OFBiz Issue Type: Task Components: accounting Affects Versions: Trunk Reporter: Leila Mekika Priority: Minor Migration of file InvoiceServices.xml to groovy -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9985) Convert BudgetServices.xml mini lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-9985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-9985: Attachment: OFBIZ-9985.patch > Convert BudgetServices.xml mini lang to groovy > -- > > Key: OFBIZ-9985 > URL: https://issues.apache.org/jira/browse/OFBIZ-9985 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > Attachments: OFBIZ-9985.patch > > > This is an attempt to migrate BudgetServices.xml to groovy file version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9985) Convert BudgetServices.xml mini lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-9985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leila Mekika updated OFBIZ-9985: Issue Type: Sub-task (was: Task) Parent: OFBIZ-9350 > Convert BudgetServices.xml mini lang to groovy > -- > > Key: OFBIZ-9985 > URL: https://issues.apache.org/jira/browse/OFBIZ-9985 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Leila Mekika >Priority: Minor > > This is an attempt to migrate BudgetServices.xml to groovy file version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9985) Convert BudgetServices.xml mini lang to groovy
Leila Mekika created OFBIZ-9985: --- Summary: Convert BudgetServices.xml mini lang to groovy Key: OFBIZ-9985 URL: https://issues.apache.org/jira/browse/OFBIZ-9985 Project: OFBiz Issue Type: Task Components: accounting Affects Versions: Trunk Reporter: Leila Mekika Priority: Minor This is an attempt to migrate BudgetServices.xml to groovy file version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9371) Add entity PartyGeo
[ https://issues.apache.org/jira/browse/OFBIZ-9371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049256#comment-16049256 ] Leila Mekika commented on OFBIZ-9371: - Hello Michael, I admit I didn't consider this entity: thanks for this info ! In fact I simplified saying that it was for fiscal reason: We have fiscal countries to attach to the actor without managing the tax in ofbiz. We may also have an actor responsible for the management of this fiscal area and we may have to attach him also to a country. That's why we choose to create this new Entity. But maybe this is really specific > Add entity PartyGeo > --- > > Key: OFBIZ-9371 > URL: https://issues.apache.org/jira/browse/OFBIZ-9371 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Leila Mekika >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-9371.patch > > > This add an association entity (and related screens/CRUD services) between > Party and Geo. > We can then link an actor with one or several country, state, country, etc.. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9372) Convert AcctgAdminServices.xml mini lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-9372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16028829#comment-16028829 ] Leila Mekika commented on OFBIZ-9372: - Thanks [~gil portenseigne]. And thanks [~deepak.dixit] and [~jacques.le.roux] for the review and advices ! > Convert AcctgAdminServices.xml mini lang to groovy > -- > > Key: OFBIZ-9372 > URL: https://issues.apache.org/jira/browse/OFBIZ-9372 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Leila Mekika >Assignee: Gil Portenseigne >Priority: Minor > Attachments: OFBIZ-9372.patch > > > This is an attempt to migrate AcctgAdminServices.xml to groovy file version. > The discussion is still running about the automation of the migration and the > langage to use for service migration (Java or groovy) > In both case, maybe this can help migrate it to java or to identify some > automatic migration matching patterns. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (OFBIZ-9371) Add entity PartyGeo
[ https://issues.apache.org/jira/browse/OFBIZ-9371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022762#comment-16022762 ] Leila Mekika edited comment on OFBIZ-9371 at 5/24/17 12:00 PM: --- Hi Pierre and Michael, thanks for the comment. In fact we had the following case for one of our customer: one of his party group needed to be related to several countries for fiscal purpose. So we added this entity to create the link instead of creating many addresses with _NA_ and only the country and a new purpose "FISCAL_LOCATION". was (Author: mleila): Hi Pierre and Michael, in fact we had the following case for one of our customer: one of his party group needed to be related to several countries for fiscal purpose. So we added this entity to create the link instead of creating many addresses with _NA_ and only the country and a new purpose "FISCAL_LOCATION". > Add entity PartyGeo > --- > > Key: OFBIZ-9371 > URL: https://issues.apache.org/jira/browse/OFBIZ-9371 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Leila Mekika >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-9371.patch > > > This add an association entity (and related screens/CRUD services) between > Party and Geo. > We can then link an actor with one or several country, state, country, etc.. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
