Replace User decision step

[Ashish Paranjpe]

Hi Phil,
Thanks a lot for this clarification.

Regards,
Ashish


On 12/22/06, Kisloff, Philip B <Philip.Kisloff at astrazeneca.com> wrote:
>
>  Hi Ashish
>
> This is just the way SAP behaves. Workflow has to settle on a default
> behaviour, which is always reserved after execution until manually
> replaced. SAP could have chosen to automatically replaced and require
> a manual reserve as required, but arguably that would encourage some users
> to hold on to workitems in an executed state, unless they took the extra
> effort of reserving the workitem again. Could be some "downstream"
> implications if that was to happen ?
>
> Just an opinion
>
> Phil
>
> -----Original Message-----
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]*On Behalf
> Of *Ashish Paranjpe
> *Sent:* 22 December 2006 13:55
> *To:* SAP-WUG at mit.edu
> *Subject:* Replace User decision step
>
> Hi All,
> I am not sure whether the below issue has a solution or not.
>
>
> A workflow triggers a user decision step which is available to a list of
> agents assigned to an org unit. One of the agents(users) executes the
> workitem. Suddenly realises that he/she does not have enough data so presses
> the button 'Cancel workitem and remain in inbox'. What is happening now is
> that the workitem is still reserved by the same user and disappears from
> other users' inbox. I think it should be that as soon as the user presses
> Cancel, the workitem should be replaced.
>
> Is this really an issue and has a solution or is this just the way SAP
> behaves?
>
>
> Thanks in advance,
> Ashish
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061227/e2297af5/attachment.htm