Skip to Content
avatar image
Former Member

Changes to shopping cart during approval.

We are running the N-Step approval workflow WS14000133.

The issue we are having is when an approver makes a change to the shopping cart during approval (Task TS10008126) we would like this to trigger the step that sends the cart back to the requestor to check/approve(Task TS10008061).

The desired behaviour occurs if the approver makes a change to the price, but not if other aattributes of the shopping cart are changed such as the vendor or the description.

The workflow determines if the cart should be passed back to the requestor based on the approve_or_reject flag in the approval task container. This variable is set to 4 when the price is changed, but 0 if other attributes are changed.

The security level for the approver to 'High' so that the workflow does not restart.

Is there any way to control what changes to the shopping cart will cause the workflow to create the task for the requestor.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Sep 02, 2008 at 12:32 PM


    Approver's security level must be set to '2' if you want to send back the shopping card to the requester.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Imthiaz Ahmed

      What I am saying is that I want the workflow to continue and it is. This is not the issue. I am happy with the way that the security level is working.

      The issue is that I would like the workflow to send a task to the requisitioner for ANY change that is made to the shopping cart. The standard solution will only send a notification to the requisition if a change is made to the value of the cart.

      We need to pick up all changes such as the description or the vendor.

      If you look at workflow WS14000134 you will see that after the approval step there is a decision step that will route the workflow to the notification to creator task or by-pass it. This is based on a variable that is set by the approval task. If the value is changed the value is set to 4, but if the vendor is changed then the value remains as 0.

      The question here is 'Can we influence the way that this approval state variable is set?'