Agents of Rejected SC Cart

[Susan R. Keohan]

Hi all,

We are on SRM 5.0, using custom workflows for SC Approval.  We have made copies of the SAP-delivered 
Approval and Rejection tasks, and modified them (gently) to contain some additional elements.

Scenario:  A cart is created, and passes up the chain through several levels of approval.  At some 
point, it is rejected, and should return to the previous level.  All possible approvers at that 
previous level are gathered and returned as possible agents for the Rejected Task (remembering, this 
is basically just a copy of the SAP-delivered task, TS10008061).  The task is delivered, the 
workflow log shows all the possible agents correctly.  Carts are either wholly approved or rejected. 
  If a cart is rejected, we still want to be able to put it back into approval, unless the cart is 
deleted.

The issue is that not all the possible agents can process the rejected task.

Agent1 can drill into the cart, and is presented with the 'Accept Changes' and 'Change' buttons. 
Following their action on that screen, they are presented with the 'Save', 'Refresh', and 'Check' 
buttons.  If Agent1 chooses 'Save', the workflow task is completed and it moves along nicely.

Agent2 can drill into the cart, but only sees the 'Change' button.  They can change the cart, then 
get the 'Save' and 'Check' buttons.  If Agent2 chooses 'Save', the cart is save, but the workflow 
log shows *no action* on the rejected task.  The copy of TS10008061 is still in status ready, and 
available to all the possible agents, as if nobody had actually touched it.

Can anyone shed some light on why certain agents of a task would not be able to process it ? (even 
if they think they have ?)

Thanks
Sue
-- 
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu