[ 
https://issues.apache.org/jira/browse/OFBIZ-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13854884#comment-13854884
 ] 

Jacques Le Roux commented on OFBIZ-5387:
----------------------------------------

Hi Christian,

It works and I could commit it almost as it (you forgot to localise the submit 
button : 
<input type="submit" value="${uiLabelMap.CommonDelete}" class="smallSubmit"/>). 

But we eventually want to remove all freemarker templates in the backend (see 
OFBIZ-5040). Could you transform EditFacilityCarrierShipment.ftl in a form 
widget?

> Improve to allow purchase order ship method options
> ---------------------------------------------------
>
>                 Key: OFBIZ-5387
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5387
>             Project: OFBiz
>          Issue Type: Improvement
>            Reporter: Christian Carlow
>             Fix For: SVN trunk
>
>         Attachments: OFBIZ-5387-0.patch, 
> OFBIZ-5387-SupplierProductServices.patch
>
>
> OFBiz should be improved to allow shipment methods to be selected for a 
> purchase order from a supplier.  Currently optionsettings.ftl sets the 
> shipping method as a hidden field with value "STANDARD@_NA" for purchase 
> orders.  I have the need to keep track of the shipping methods as well as due 
> dates of purchase order items.
> The shipment methods will have to somehow be related back to the supplier.  
> Currently the shipment methods are determined by those related to the store 
> but no store is associated with a cart for purchase orders.  
> Stores could be created for all suppliers specifically for associating 
> carriers and shipment methods and the order creation form could be updated so 
> that the supplier store is selected instead of the supplier party.  The 
> ProductStore payToPartyId field could be used to identify the supplier that 
> is supposed to be associated with the store.
> Anyone else have some ideas?



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to