secondary method in decision step.

[ezra]

Thank you,
Sorry for the direct reply.
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Wednesday, January 07, 2004 2:23 AM
To: 'ezra'
Subject: RE: secondary method in decision step.
 
 
Elad,
If you are using the SAP Business Workplace inbox and use the "advance with
dialog" option in the workflow step then they move straight through to the
next dialog work item if they are also an agent of the next dialog work
item.
 
Please do not reply to me again directly.  As a full-time paid consultant,
please understand that it is not appropriate for me to provide individual
consulting.  All communication should be via the SAP-WUG so everyone learns.
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: ezra [mailto:saarell at netvision.net.il]
Sent: Tuesday,6 January 2004 6:05 PM
To: Dart, Jocelyn
Subject: RE: secondary method in decision step.
 
 
Hello,
What I want to get is that right after the user makes his selection in the
decision step, a popup with the long text appears.
Maybe I lack some knowledge, but according to my knowledge if I'll use a
separate WI to open the project or the long text,
The user will have to open his inbox again, and excecute the WI in order to
open the project.
 
Is there a way to define the WI in such a manner that it'll run on client
side automatically ?
 
Thank you,
Elad Ezra Saar.
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Tuesday, January 06, 2004 2:35 AM
To: 'ezra'
Subject: RE: secondary method in decision step.
 
 
Hi Ezra, I don't see the problem - the point of a such a user decision is to
give you 4 outcomes.  From the 4 outcomes you add your
steps to do the processing.  So the steps after approve and reject are
background steps and the steps after open the project or open the
project long text are dialog steps.  Why do you think you need everything in
the one step??  Why do you need to avoid using ABAP??
 
 
Please reply via the SAP-WUG.
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: ezra [mailto:saarell at netvision.net.il]
Sent: Monday,5 January 2004 5:50 PM
To: Dart, Jocelyn
Subject: RE: secondary method in decision step.
 
 
Thank you very much,
You have mentioned that I should use a separate WI...
I'd like to give you an example for my decision step's options :
 
        1. approve a project            <- background processing
        2. reject a project             <- background processing
        3. open the project             <- client side (dialog)
        4. open project's long text     <- client side (dialog)
 
How can I use a separate WI and still perform this functionality without
using ABAP ?
 
thank you,
Elad.
 
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Dart, Jocelyn
Sent: Monday, January 05, 2004 12:14 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: secondary method in decision step.
 
 
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.