secondary method in decision step.

[Dart, Jocelyn]

Hi Elad,
 
Before, after and secondary methods are passed values via automatic binding - not direct parameter entry.
Essentially this means that you are passed the same elements as are passed to the main task providing you have
matching container elements defined of course.
 
In any case, the scenario you have described is not a proper use of before, after or secondary methods.
 
If you want to call another transaction on the client side, use a separate work item.
 
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of ezra
Sent: Monday,5 January 2004 3:37 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: secondary method in decision step.
 
 
Hello,
I am trying to send a decision step WI, which according to user decision,
runs either a background process or calls a transaction on the client side.
The problem is that after the decision is made, the process goes back to
server side, and I am unable to call a transaction on the client side.
I thought of using the secondary method that runs after the processing of
the decision step, but it seems that i cannot pass parameters o the methos.
 
Has anyone met with this kind of problem ?
Does anyone have a solution ?
 
Thanks,
Elad.