Customization of pickList services

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Customization of pickList services

Shereen
Hi All

I changed in the order flow a little and therefore now I have to do some customization in the picking process

My flow goes as follows
I've added an attribute in the customer party called require prepayment this indicates if the customer should make down payments in the his orders or not.
in the sales order I do checking if this customer has the require prepayment attribute the prepayment should be received first then the order shall move from "ORDER_APPROVED "to a state called "Ready for shipping"
Now regarding the picking I want the order that are ready to be picked should be either of the two cases:
1-Ready to ship
2-Approved and the customer doesnt have the require prepayment attribute

I was able to do that checking using ftl and groovy by using orderReaderHelper to get the customer then check the require prepayment attribute but how can I make that checking in pickListservices
in that service the checking is done this way

 <condition-list combine="and">
                        <condition-expr field-name="orderTypeId" value="SALES_ORDER"/>
                        <condition-expr field-name="statusId" value="ORDER_APPROVED"/>
                        <condition-expr field-name="isRushOrder" from-field="parameters.isRushOrder" ignore-if-empty="true"/>
                    </condition-list>
Can I modify this to match the scanrio I want
In other way make the order possible for picking if it's status is "READY_TO_SHIP" or
if the order status is "ORDER_APPROVED" and the customer doesn't have the require prepayment field
does the minilang allow me to write such a code ? or it would be safer to make the scenario I want want lead to another status and simply check on that status?
Reply | Threaded
Open this post in threaded view
|

Re: Customization of pickList services

BJ Freeman
you first have to decide how your going to do life cycle of you changes
against future updates from ofbiz.

if you are going to want to upgrade as some point then you should follow
the patterns used in ofbiz.

=========================
BJ Freeman
Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com  <http://www.specialtymarket.com/>
Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man

>
Shereen sent the following on 10/31/2010 12:51 AM:

> Hi All
>
> I changed in the order flow a little and therefore now I have to do some
> customization in the picking process
>
> My flow goes as follows
> I've added an attribute in the customer party called require prepayment this
> indicates if the customer should make down payments in the his orders or
> not.
> in the sales order I do checking if this customer has the require prepayment
> attribute the prepayment should be received first then the order shall move
> from "ORDER_APPROVED "to a state called "Ready for shipping"
> Now regarding the picking I want the order that are ready to be picked
> should be either of the two cases:
> 1-Ready to ship
> 2-Approved and the customer doesnt have the require prepayment attribute
>
> I was able to do that checking using ftl and groovy by using
> orderReaderHelper to get the customer then check the require prepayment
> attribute but how can I make that checking in pickListservices
> in that service the checking is done this way
>
>   <condition-list combine="and">
>                          <condition-expr field-name="orderTypeId"
> value="SALES_ORDER"/>
>                          <condition-expr field-name="statusId"
> value="ORDER_APPROVED"/>
>                          <condition-expr field-name="isRushOrder"
> from-field="parameters.isRushOrder" ignore-if-empty="true"/>
>                      </condition-list>
> Can I modify this to match the scanrio I want
> In other way make the order possible for picking if it's status is
> "READY_TO_SHIP" or
> if the order status is "ORDER_APPROVED" and the customer doesn't have the
> require prepayment field
> does the minilang allow me to write such a code ? or it would be safer to
> make the scenario I want want lead to another status and simply check on
> that status?
>