AW: Decision method is coded to remember last option

[Becker Stephan (extern)]

Hi there,
 
I just came across this issue. It comes in two flavours:
 
When processing a user decision with confirmation, take out the =
function
module in the "WI display" tab of the activity maintenance in the WS, =
then
it'll work all right. The cause for this error is that variables are =
being
passed sloppily when processing user decisions inline in the inbox =
through
the said function module.. SAP say they will not fix this as it is =
seldom=20
 
When processing methods with result parameters and end confirmations =
(like
any old approval), something similar happens. This is cured by an OSS =
note
(number escapes me at present..).
 
Hth,
Stephan
 
 
 
-----Urspr=FCngliche Nachricht-----
Von: Kisloff, Philip B [mailto:Philip.Kisloff at astrazeneca.com]
Gesendet: Dienstag, 28. Mai 2002 17:25
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Decision method is coded to remember last option
 
 
Hi all,
 
We are in 4.6C, and when I cancel processing of a generic user decision =
task
using the confirmation prompt,
the workitem returns to my inbox as expected. What is not expected by =
me is
when I re-process the decision
I can not change the original result - I am presented with the =
confirmation
prompt again.
 
I checked the code and found the following. I think this was introduced =
as
standard because the object header does
indicate any modifications. I'm sure it never worked like this before, =
does
anyone know what's up? I understand from
colleagues this behaviour has been known about through several patches, =
we
are currently on SAPKB46C28.
 
*-{
  SWC_GET_ELEMENT CONTAINER   '_RESULT'  WI_RETURN.
  IF SY-SUBRC EQ 0.
    IF NOT WI_RETURN IS INITIAL.
      I_AM_ALREADY_PROCESSED =3D 'X'.
    ENDIF.
  ENDIF.
*-}
 
 
Regards
 
Phil