Workflow on sales order price change

Question

I am trying to create a workflow to trigger when the net price on a sales order line has been changed. I would like the workflow email to contain both the value before the change and the value after. I am close, but seem to not be able to capture the correct line. If there are 3 lines on the sales order, I get 3 emails when I only want 2 email with the information from the line which the price was changed. 
 Here is my workflow and data model. Any suggestions?

ardzimano · Answer

#You would have to write a function like this a nd call it as below and save it in a file YFUNCS 
 #The message part is as below: 
 #################################################################### 
 Order |[F:SOH]SOHNUM | has been updated by |GUSER| Date and Time |Datetime$| 
 |FUNC YFUNCS.PRICE_CHANGES()| 
 ######################################################### 
 #The function is as below 
 Funprog PRICE_CHANGES() Local Char ALL_CHANGES(250) 
 ALL_CHANGES='Price Changes: ' +chr$(13) + chr$(10) For [F:SOP] Where SOHNUM=[M:SOH0]SOHNUM ALL_CHANGES += num$(SOPLIN/1000)+': '+ num$([F:SOP]NETPRI) +' TO '+ num$([M:SOH4]NETPRI(SOPLIN/1000))+chr$(13) + chr$(10) Next End ALL_CHANGES 
 #For more help email dzimanoar@gmail.com

ardzimano · Answer

You would place it in a Script called YFUNCS under Development ->Script Dictionary->Scripts->Script Editor. Then Compile it. For more help email dzimanoar@gmail.com

Michael91 · Answer

It could have something to do with the "type" under the conditions. You have this set to header, when it should be line level workflow. In this case, it will evaluate the condition based on each line instead of the header (all lines).

Xavier.Buxade · Answer

Hi ardzimano, 
 My big doubt now (if you are 100% sure this is working) is that when workflow is executed the changes are not stored in database. But what I remember, for example workflow creation we use [F:xxx], then is after write. I don't now if in update is previous ReWrite (could you confirm please?), but if its after then take a look of that: 
 
 Other recommendation maybe is this: Since in X3 we have Clob vars and workflow message field is like this:

maybe is better to define your variable ALL_CANCHES like this: Local clbfile ALL_CHANGES(5) Because for example if you have this kind of prices 3,2 
 Line # 1: 100.00 TO 100.00 
 You will not inform more than 10 lines. 
 BUT I'll prefer to create a new field in SOP table called ZNEWPRICE, then with APRES_MODIF check with zc and [M:SOH4] if have change and is not a new line. Then the workflow will be by line with a simple condition (ZNEWPRICE<>0). This will give more freedom to consultants or customers to design the text and also you could the new price in the workflow monitor. 
 Also you will give more functionality to your customer, for example: 
 
 Crete a User Query with the Orders changed you can filter UPDDAT=Date-1 or whatelse 
 Create a Portal with a query with the Orders changed you can filter UPDDAT=Date-1 or whatelse. (versions higher V6). 
 Create reports and send by email. 
 
 And Writting this to you, other idea comes to my mind, maybe you can use the auditory table and work with that. (available since V5) 
 
 Best Regards,

Sage X3

Workflow on sales order price change

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING