[ http://issues.apache.org/jira/browse/OFBIZ-455?page=comments#action_12449740 ] Eriks Dobelis commented on OFBIZ-455: -------------------------------------
I vote for Organization Context. I would prefer storing organization context in the session. If the user can see organization context in select near language select, then he should not be too confused. OFBIZ-118 initially was not talking about selecting of organization context, but about various ways to limit access to data. So for me sounds that your patch would more naturally fit in this issue. I suggest we separate patch switching organization context from the patches limiting access to data in different components, providing defaults, etc., so that we would have smaller patches, which are more easily manageable (i.e. sooner tested and committed). Once we have organization context switching "infrastructure" we can gradually start using it in different places. > Selecting active organization party > ----------------------------------- > > Key: OFBIZ-455 > URL: http://issues.apache.org/jira/browse/OFBIZ-455 > Project: OFBiz (The Open for Business Project) > Issue Type: New Feature > Reporter: Eriks Dobelis > Attachments: activeOrgParty.diff, selectingOrganizationalContext.jpg > > > Idea is to provide possibility to select active organization party id, which > then could be used: > 1) to provide default in different components (e.g. in creating invoices, > payments, accounting transactions, etc.); > 2) in implementation of OFBIZ-118, i.e. to show or hide data based on the > active organization; > 3) to improve current Accounting/Companies/Admin so that organizationPartyId > is remembered throughout the session (if not changed). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
