PierreSmits opened a new pull request #407:
URL: https://github.com/apache/ofbiz-framework/pull/407


   Currently the create buttons for the main objects of the order components 
are located within the find and profile widgets/templates of those object.
   In order to improve the usability of OFBiz (and thus the appeal of it for 
adopters and users) these create buttons/links/etc. should be in a main action 
menu visible at all times when a user is working within the component.
   
   Modified:
   added: MainActionMenu for the order component, having:
   
   menu-item to start the order creation
   menu-item to start the quote creation
   menu-item to start the request creation
   menu-item to start the requirement creation
   menu-item to start the return creation
   menu-item to start the allocation plan creation
   removed: menu-item to create a request from RequestSubTabBar
   AllocationPlanScreens.xml
   added: decorator-section for pre-body to include the MainActionMenu
   CommonScreens.xml
   improved: grouping regarding customer requests
   CustRequestScreens.xml
   added: decorator-section for pre-body to include the MainActionMenu
   removed 'menu-bar' decorator section
   OrderEntryCommonScreens.xml
   added: decorator-section for pre-body to include the MainActionMenu
   OrderReturnScreens.xml
   added: decorator-section for pre-body to include the MainActionMenu
   removed: 'basic-nav' container
   OrderViewScreens.xml
   added: decorator-section for pre-body to include the MainActionMenu
   QuoteScreens.xml
   added: decorator-section for pre-body to include the MainActionMenu
   removed: container with create quote link
   QuoteWorkEffortScreens.xml
   added: decorator-section for pre-body to include the MainActionMenu
   ReportScreens.xml
   added: decorator-section for pre-body to include the MainActionMenu
   RequirementScreens.xml
   added: decorator-section for pre-body to include the MainActionMenu
   removed: container having create link


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to