[jira] [Commented] (OFBIZ-7117) LookupAccount search screen 'Find' button redirect to Lookup Group
[
https://issues.apache.org/jira/browse/OFBIZ-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15500699#comment-15500699
]
Nicolas Malin commented on OFBIZ-7117:
--
Yes, just I hadn't finish yet :)
> LookupAccount search screen 'Find' button redirect to Lookup Group
> --
>
> Key: OFBIZ-7117
> URL: https://issues.apache.org/jira/browse/OFBIZ-7117
> Project: OFBiz
> Issue Type: Bug
> Components: party
>Affects Versions: Trunk
>Reporter: Montalbano Florian
>Assignee: Nicolas Malin
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> How to reproduce :
> 1) Go to a person party profile : i.e.
> https://localhost:8443/partymgr/control/viewprofile?partyId=admin
> 2) Click on 'Create New' from the 'List Related Accounts' section
> 3) Click on the 'Look up button' (for searching through the account party id)
> 4) Notice the title of the pop-up : "Lookup Party with the role Account" and
> the limited number of result.Lookup Party with the role Account.
> 5) Click on the 'Find' button (empty search)
> 6) Notice the new title "Lookup Group" and the new set of result
> Root of the behaviour :
> In "ofbiz/applications/party/widget/partymgr/LookupScreens.xml", there is the
> definition of the "LookupAccount" screen. This screen is the pop-up showing
> up when you click on the 'Lookup button' . It includes two forms :
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> and
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> The first one, is the one used for the search when you click on the 'Find'
> button. By looking at this form's code, we can see that its target is the
> "LookupPartyGroup" screen. So when you click on the 'Find' button, a
> different screen is loaded and the title and the behaviour of the pop-up is
> modified. This screen is composed from the two same forms than the original
> one.
> Solution ? :
> I don't know if it's possible to overload the target of a form when it's
> called but if it is possible, then we may call the same form with the target
> "LookupAccount". If not, I think we need to create another form with the
> target "LookupAccount".
> Thanks,
> Florian
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7117) LookupAccount search screen 'Find' button redirect to Lookup Group
[
https://issues.apache.org/jira/browse/OFBIZ-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15500696#comment-15500696
]
Nicolas Malin commented on OFBIZ-7117:
--
It's work as well !
Commited on trunk at revision 1761314
thanks
> LookupAccount search screen 'Find' button redirect to Lookup Group
> --
>
> Key: OFBIZ-7117
> URL: https://issues.apache.org/jira/browse/OFBIZ-7117
> Project: OFBiz
> Issue Type: Bug
> Components: party
>Affects Versions: Trunk
>Reporter: Montalbano Florian
>Assignee: Nicolas Malin
>Priority: Minor
>
> How to reproduce :
> 1) Go to a person party profile : i.e.
> https://localhost:8443/partymgr/control/viewprofile?partyId=admin
> 2) Click on 'Create New' from the 'List Related Accounts' section
> 3) Click on the 'Look up button' (for searching through the account party id)
> 4) Notice the title of the pop-up : "Lookup Party with the role Account" and
> the limited number of result.Lookup Party with the role Account.
> 5) Click on the 'Find' button (empty search)
> 6) Notice the new title "Lookup Group" and the new set of result
> Root of the behaviour :
> In "ofbiz/applications/party/widget/partymgr/LookupScreens.xml", there is the
> definition of the "LookupAccount" screen. This screen is the pop-up showing
> up when you click on the 'Lookup button' . It includes two forms :
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> and
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> The first one, is the one used for the search when you click on the 'Find'
> button. By looking at this form's code, we can see that its target is the
> "LookupPartyGroup" screen. So when you click on the 'Find' button, a
> different screen is loaded and the title and the behaviour of the pop-up is
> modified. This screen is composed from the two same forms than the original
> one.
> Solution ? :
> I don't know if it's possible to overload the target of a form when it's
> called but if it is possible, then we may call the same form with the target
> "LookupAccount". If not, I think we need to create another form with the
> target "LookupAccount".
> Thanks,
> Florian
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7117) LookupAccount search screen 'Find' button redirect to Lookup Group
[
https://issues.apache.org/jira/browse/OFBIZ-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15500683#comment-15500683
]
Jacques Le Roux commented on OFBIZ-7117:
BTW should we not close?
> LookupAccount search screen 'Find' button redirect to Lookup Group
> --
>
> Key: OFBIZ-7117
> URL: https://issues.apache.org/jira/browse/OFBIZ-7117
> Project: OFBiz
> Issue Type: Bug
> Components: party
>Affects Versions: Trunk
>Reporter: Montalbano Florian
>Assignee: Nicolas Malin
>Priority: Minor
>
> How to reproduce :
> 1) Go to a person party profile : i.e.
> https://localhost:8443/partymgr/control/viewprofile?partyId=admin
> 2) Click on 'Create New' from the 'List Related Accounts' section
> 3) Click on the 'Look up button' (for searching through the account party id)
> 4) Notice the title of the pop-up : "Lookup Party with the role Account" and
> the limited number of result.Lookup Party with the role Account.
> 5) Click on the 'Find' button (empty search)
> 6) Notice the new title "Lookup Group" and the new set of result
> Root of the behaviour :
> In "ofbiz/applications/party/widget/partymgr/LookupScreens.xml", there is the
> definition of the "LookupAccount" screen. This screen is the pop-up showing
> up when you click on the 'Lookup button' . It includes two forms :
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> and
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> The first one, is the one used for the search when you click on the 'Find'
> button. By looking at this form's code, we can see that its target is the
> "LookupPartyGroup" screen. So when you click on the 'Find' button, a
> different screen is loaded and the title and the behaviour of the pop-up is
> modified. This screen is composed from the two same forms than the original
> one.
> Solution ? :
> I don't know if it's possible to overload the target of a form when it's
> called but if it is possible, then we may call the same form with the target
> "LookupAccount". If not, I think we need to create another form with the
> target "LookupAccount".
> Thanks,
> Florian
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7117) LookupAccount search screen 'Find' button redirect to Lookup Group
[
https://issues.apache.org/jira/browse/OFBIZ-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15500681#comment-15500681
]
Jacques Le Roux commented on OFBIZ-7117:
Well done guys, thanks!
> LookupAccount search screen 'Find' button redirect to Lookup Group
> --
>
> Key: OFBIZ-7117
> URL: https://issues.apache.org/jira/browse/OFBIZ-7117
> Project: OFBiz
> Issue Type: Bug
> Components: party
>Affects Versions: Trunk
>Reporter: Montalbano Florian
>Assignee: Nicolas Malin
>Priority: Minor
>
> How to reproduce :
> 1) Go to a person party profile : i.e.
> https://localhost:8443/partymgr/control/viewprofile?partyId=admin
> 2) Click on 'Create New' from the 'List Related Accounts' section
> 3) Click on the 'Look up button' (for searching through the account party id)
> 4) Notice the title of the pop-up : "Lookup Party with the role Account" and
> the limited number of result.Lookup Party with the role Account.
> 5) Click on the 'Find' button (empty search)
> 6) Notice the new title "Lookup Group" and the new set of result
> Root of the behaviour :
> In "ofbiz/applications/party/widget/partymgr/LookupScreens.xml", there is the
> definition of the "LookupAccount" screen. This screen is the pop-up showing
> up when you click on the 'Lookup button' . It includes two forms :
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> and
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> The first one, is the one used for the search when you click on the 'Find'
> button. By looking at this form's code, we can see that its target is the
> "LookupPartyGroup" screen. So when you click on the 'Find' button, a
> different screen is loaded and the title and the behaviour of the pop-up is
> modified. This screen is composed from the two same forms than the original
> one.
> Solution ? :
> I don't know if it's possible to overload the target of a form when it's
> called but if it is possible, then we may call the same form with the target
> "LookupAccount". If not, I think we need to create another form with the
> target "LookupAccount".
> Thanks,
> Florian
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7117) LookupAccount search screen 'Find' button redirect to Lookup Group
[
https://issues.apache.org/jira/browse/OFBIZ-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15500682#comment-15500682
]
Jacques Le Roux commented on OFBIZ-7117:
BTW should we not close?
> LookupAccount search screen 'Find' button redirect to Lookup Group
> --
>
> Key: OFBIZ-7117
> URL: https://issues.apache.org/jira/browse/OFBIZ-7117
> Project: OFBiz
> Issue Type: Bug
> Components: party
>Affects Versions: Trunk
>Reporter: Montalbano Florian
>Assignee: Nicolas Malin
>Priority: Minor
>
> How to reproduce :
> 1) Go to a person party profile : i.e.
> https://localhost:8443/partymgr/control/viewprofile?partyId=admin
> 2) Click on 'Create New' from the 'List Related Accounts' section
> 3) Click on the 'Look up button' (for searching through the account party id)
> 4) Notice the title of the pop-up : "Lookup Party with the role Account" and
> the limited number of result.Lookup Party with the role Account.
> 5) Click on the 'Find' button (empty search)
> 6) Notice the new title "Lookup Group" and the new set of result
> Root of the behaviour :
> In "ofbiz/applications/party/widget/partymgr/LookupScreens.xml", there is the
> definition of the "LookupAccount" screen. This screen is the pop-up showing
> up when you click on the 'Lookup button' . It includes two forms :
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> and
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> The first one, is the one used for the search when you click on the 'Find'
> button. By looking at this form's code, we can see that its target is the
> "LookupPartyGroup" screen. So when you click on the 'Find' button, a
> different screen is loaded and the title and the behaviour of the pop-up is
> modified. This screen is composed from the two same forms than the original
> one.
> Solution ? :
> I don't know if it's possible to overload the target of a form when it's
> called but if it is possible, then we may call the same form with the target
> "LookupAccount". If not, I think we need to create another form with the
> target "LookupAccount".
> Thanks,
> Florian
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7117) LookupAccount search screen 'Find' button redirect to Lookup Group
[
https://issues.apache.org/jira/browse/OFBIZ-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15500653#comment-15500653
]
Nicolas Malin commented on OFBIZ-7117:
--
OK not backport, my correction didn't work on stable branch
> LookupAccount search screen 'Find' button redirect to Lookup Group
> --
>
> Key: OFBIZ-7117
> URL: https://issues.apache.org/jira/browse/OFBIZ-7117
> Project: OFBiz
> Issue Type: Bug
> Components: party
>Affects Versions: Trunk
>Reporter: Montalbano Florian
>Assignee: Nicolas Malin
>Priority: Minor
>
> How to reproduce :
> 1) Go to a person party profile : i.e.
> https://localhost:8443/partymgr/control/viewprofile?partyId=admin
> 2) Click on 'Create New' from the 'List Related Accounts' section
> 3) Click on the 'Look up button' (for searching through the account party id)
> 4) Notice the title of the pop-up : "Lookup Party with the role Account" and
> the limited number of result.Lookup Party with the role Account.
> 5) Click on the 'Find' button (empty search)
> 6) Notice the new title "Lookup Group" and the new set of result
> Root of the behaviour :
> In "ofbiz/applications/party/widget/partymgr/LookupScreens.xml", there is the
> definition of the "LookupAccount" screen. This screen is the pop-up showing
> up when you click on the 'Lookup button' . It includes two forms :
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> and
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> The first one, is the one used for the search when you click on the 'Find'
> button. By looking at this form's code, we can see that its target is the
> "LookupPartyGroup" screen. So when you click on the 'Find' button, a
> different screen is loaded and the title and the behaviour of the pop-up is
> modified. This screen is composed from the two same forms than the original
> one.
> Solution ? :
> I don't know if it's possible to overload the target of a form when it's
> called but if it is possible, then we may call the same form with the target
> "LookupAccount". If not, I think we need to create another form with the
> target "LookupAccount".
> Thanks,
> Florian
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7117) LookupAccount search screen 'Find' button redirect to Lookup Group
[
https://issues.apache.org/jira/browse/OFBIZ-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15499337#comment-15499337
]
Nicolas Malin commented on OFBIZ-7117:
--
Commited on trunk at revision 1761257, I will check if will need to backport
> LookupAccount search screen 'Find' button redirect to Lookup Group
> --
>
> Key: OFBIZ-7117
> URL: https://issues.apache.org/jira/browse/OFBIZ-7117
> Project: OFBiz
> Issue Type: Bug
> Components: party
>Affects Versions: Trunk
>Reporter: Montalbano Florian
>Assignee: Nicolas Malin
>Priority: Minor
>
> How to reproduce :
> 1) Go to a person party profile : i.e.
> https://localhost:8443/partymgr/control/viewprofile?partyId=admin
> 2) Click on 'Create New' from the 'List Related Accounts' section
> 3) Click on the 'Look up button' (for searching through the account party id)
> 4) Notice the title of the pop-up : "Lookup Party with the role Account" and
> the limited number of result.Lookup Party with the role Account.
> 5) Click on the 'Find' button (empty search)
> 6) Notice the new title "Lookup Group" and the new set of result
> Root of the behaviour :
> In "ofbiz/applications/party/widget/partymgr/LookupScreens.xml", there is the
> definition of the "LookupAccount" screen. This screen is the pop-up showing
> up when you click on the 'Lookup button' . It includes two forms :
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> and
> {code} location="component://party/widget/partymgr/LookupForms.xml"/>{code}
> The first one, is the one used for the search when you click on the 'Find'
> button. By looking at this form's code, we can see that its target is the
> "LookupPartyGroup" screen. So when you click on the 'Find' button, a
> different screen is loaded and the title and the behaviour of the pop-up is
> modified. This screen is composed from the two same forms than the original
> one.
> Solution ? :
> I don't know if it's possible to overload the target of a form when it's
> called but if it is possible, then we may call the same form with the target
> "LookupAccount". If not, I think we need to create another form with the
> target "LookupAccount".
> Thanks,
> Florian
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
