You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Bruno Busco (JIRA)" <ji...@apache.org> on 2010/08/26 02:10:17 UTC

[jira] Updated: (OFBIZ-3902) Improving the Party Find Screen

     [ https://issues.apache.org/jira/browse/OFBIZ-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Busco updated OFBIZ-3902:
-------------------------------

    Attachment: NewFindParty.patch

> Improving the Party Find Screen
> -------------------------------
>
>                 Key: OFBIZ-3902
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3902
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: party
>            Reporter: Bruno Busco
>            Priority: Minor
>         Attachments: NewFindParty.patch
>
>
> I have done some work to improve the Party Find Screen.
> Now it uses a standard FindScreenDecorator. Almost all column are sortable, the pagination is flexible as the standard.
> I have created a new entity for the form used in this screen "PartyDetails".
> The contact fields like PostalAddress etc. are still missing 
> The button on the right to access the orders, requests etc. are not available becouse I do not know how to add them in a form field.
> In any case I think it is better to not have them to remove a dependence of Party from Orders etc.
> These buttons are still available on the SubTabBar of the Party details screen.
> So, now, the user should go to the party details screen (clicking on the PartyID) and then use the menu.
> This menu could at a later stage be injected by the Order application so that the dependence issue will definitively be solved.
> Could someone please give a look to the patch and give some help?
> - How to add the contact fields that are still missing?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.