[
https://issues.apache.org/jira/browse/OFBIZ-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-5397.
----------------------------------
Resolution: Fixed
Fix Version/s: Release Branch 13.07
Release Branch 12.04
SVN trunk
Release Branch 11.04
Assignee: Jacques Le Roux
Thanks Christian,
Your slightly modified patch is in
trunk r1544444
R13.07 r1544446
R12.04 r1544447
R11.04 r1544448
I simply used the token _@_ as separator to prevent wrong splits in case @ or _
would have been used in facilities or contactMechs Ids (though it's not
possible OOTB from UI, those Ids are generated)
> Incorrect selected ship destination displayed on purchase order entry form
> --------------------------------------------------------------------------
>
> Key: OFBIZ-5397
> URL: https://issues.apache.org/jira/browse/OFBIZ-5397
> Project: OFBiz
> Issue Type: Bug
> Reporter: Christian Carlow
> Assignee: Jacques Le Roux
> Fix For: Release Branch 11.04, SVN trunk, Release Branch 12.04,
> Release Branch 13.07
>
> Attachments: OFBIZ-5397.patch
>
>
> Selected ship group destinations are displayed incorrectly on the purchase
> order entry Shipping page. The first ship group destination is selected
> without checking if any of the other destinations were selected. Part of the
> problem is that the facilityId of the destination chosen is not specified in
> the parameters passed to CheckOutEvents finalizeOrderEntry function.
> To reproduce:
> 1. Create an order to DemoSupplier
> 2. Add any supplier product to the order and click Finalize Order
> 3. Click Continue until you reach the Shipping page
> 4. Choose the second shipping destination and click Continue
> 5. Click the Shipping link to go back to the previous shipping page
> 6. Notice that the second destination is not selected
> The second destination is actually assigned because it appears on the
> confirmation page but no code exists to check the correct radio option. The
> facilityId will have to be passed in somehow to allow such logic to be
> correctly implemented.
--
This message was sent by Atlassian JIRA
(v6.1#6144)