[
https://issues.apache.org/jira/browse/OFBIZ-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473306
]
Jacopo Cappellato commented on OFBIZ-659:
-----------------------------------------
Anil,
about your last question about agreement screens:
* I think that the agreement selection should be done as soon as possible; the
reason is that the selected agreement is optionally used to determine the
currency for the cart and (for sales agreement) also the prices of the products
sold to a customer
* about the terms screen: I think that it is more natural to have it in the
checkout screens, if you really think we should move it in the order init
screens for me it's ok, but leave this as a configurable option (I mean that
playing with the controller entries should allow us to change the behaviour);
also there are plans to make the terms screen also available to sales orders
(if an agreement is selected), right now it is only shown for purchase orders
Thanks for your work on this!
> Refactoring Create Order process
> --------------------------------
>
> Key: OFBIZ-659
> URL: https://issues.apache.org/jira/browse/OFBIZ-659
> Project: OFBiz (The Open for Business Project)
> Issue Type: Improvement
> Components: order
> Reporter: Anil K Patel
> Attachments: OrderChekOutProcessRefac.patch,
> OrderProcessSimpleMethods.patch
>
>
> Focus of this Jira Issue is Refactoring Create Order Process, Implement a
> parallel code as needed so that the current Code remains intact.
> From David's email on Mailing list.
> Just some quick thoughts...
> Following the pattern of the anonymous and other checkout processes
> in the ecommerce app would be a great way to go.
> In the order manager there are various paths through the checkout
> process so we might have, for example, 2 different sets of request-
> map definitions and two different "progress bars", one for sales
> orders and one for purchase orders. These two different sets of high-
> level artifacts can point to the same views, services/events,
> screens, data prep scripts, etc wherever the two processes overlap.
> -David
> My Initial comments
> The anonymous checkout process in Ecommerce component provides some high
> level guiding principals. Few things that I can think of are
> 1) moving some code that's embedded in Java classes into small simple methods.
> 2) Moving process control logic from event handlers to Controller file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
