Execute reserves workitem (was: work items getting reserved)

[Breslavets, Sergey]

Hi Michael,
 
this probably sounds like an obvious suggestion, by did you check WI_Display tab
for your decision task?
 
WF Builder by default assigns the function module SWU2_INPLACE_DECISION_PROCESS
for adaptation of the workitem preview in the workplace - it causes the decision
task to be displayed in the preview window (instead on Full screen mode). It
also puts the workitem in "RESERVED" mode (since SWW_WW_EXECUTE is not called,
like in case of Web Workplace).
 
Thanks,
Sergey
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]
Sent: Friday, December 06, 2002 4:52 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Execute reserves workitem (was: work items getting
reserved)
 
 
Hi Sergey,
Thanks for the info. The scenario I mentioned relates to the SAPGUI
(i.e. using Sapgui, executing merely reserves the WI). Interestingly
enough, I tried this via the Web workplace, and it gets even more
strange:
Executing the WI does not change it's status at all. No log entries are
created either until it is completed. Following are the log entries for
a WI which I executed twice and cancelled and completed on the third
time:
Dialog work item created
Completed by hand
Work item reserved
Work item processing complete
 
Either way, it does not explain why one WI behaves differently to all
the others. i.e. where other decision tasks go to Ready, this one goes
to reserved. And of course my original (real) problem - why does it not
execute in full screen???
Thanks
Mike
 
 
 
On Thu, Dec 05, 2002 at 04:28:38PM -0600, Breslavets, Sergey wrote:
> Hi Michael,
>
> normal status flow (happy path) for the dialog workitem look like this:
> READY -> SELECTED(RESERVED) -> STARTED(IN PROCESS) -> COMPLETED.
>
> the processing logic for a workitem is a little different on the web. If you
are
> executing your workitem from web inbox (transaction BWSP), control is NOT
passed
> to the function SWW_WW_EXECUTE which normally calls object method to process
the
> workitem. Instead, the ITS service associated with the web transaction for the
> task is called (BWWF_WI_DECI for user decision) - this ITS service drives
> execution of the workitem.
> Since the function SWW_WW_EXECUTE (which is normally responsible for changing
> the workitem status from "RESERVED" to "STARTED") is not called when the
> workitem is executed from the web, the status is left unchanged as "RESERVED".
>
> Also, you can change appearance of your user decision on the web by setting
your
> using a custom task/ITS service for the user decision step, or customizing ITS
> service for workflow inbox altogether (copy service BSWP to e.g. Z_BWSP and
> modify) - that's what we did for our implementation.
>
> regards,
> sergey
>
> -----Original Message-----
>> From: Michael Pokraka [mailto:workflow at quirky.me.uk]
> Sent: Thursday, December 05, 2002 1:32 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Execute reserves workitem (was: work items getting
> reserved)
>
>
> Hi Sergey,
> I'm afraid I'd have to disagree with you. When a user executes a
> decision task it's status normally changes to STARTED (at least it does
> so for quite a few other decision tasks in our system). If the user
> backs out, it remains STARTED.
> Perhaps there is a difference in SAP versions - I'm working on a 4.6c
> system.
>
> The other curious coincidence is that this particular task will not
> execute in a full screen, so I'm all but convinced that this behaviour
> is linked.
>
> Thanks for your input though!
> Cheers
> Mike
>
>
>
> On Thu, Dec 05, 2002 at 12:38:32PM -0600, Breslavets, Sergey wrote:
> > Michael,
> >
> > "RESERVED" means that the workitem was assigned to particular agent who
> started
> > processing it. You don't see "STARTED" status, because it's moved to "READY"
> > when it's sent to agents' inbox.
> >
> > Basically, dialog workitem initially is created in status "READY" and
> available
> > to all responsible agents. When one of them starts executing the workitem WF
> > system "reserves" it for that person, its status is changed to 'RESERVED',
and
> > it's removed from other agent's inboxes. It'll stay "reserved" for that
agent
> > until he/she completes the task (sets status to "COMPLETED", rejects
execution
> > (if possible), forwards, resubmit or replace it. Last action sets workitem
> back
> > to status "READY" and makes it available to all responsible agents again.
> >
> > Does it answer your question?
> >
> > Sergey
> >
> > -----Original Message-----
> > From: Michael Pokraka [mailto:workflow at quirky.me.uk]
> > Sent: Thursday, December 05, 2002 10:50 AM
> > To: SAP-WUG at MITVMA.MIT.EDU
> > Subject: Execute reserves workitem (was: work items getting reserved)
> >
> >
> > Hi all,
> > I've a problem which may relate to the other one below.
> > I recently posted a problem in getting a WI to execute fullscreen rather
> > than in the SBWP preview window. Well, it's still not happening, even
> > though it should. What is of interest is that execution will only change
> > the WI status to RESERVED.
> >
> > In effect, user dblclicks, item changes to RESERVED and decision is
> > presented in the preview window. If I cancel by any means it remains in
> > RESERVED status, and if I click on a decision it goes straight to
> > completed. Not even a whiff of a STARTED status.
> >
> > I'm running out of ideas, any clues?
> >
> > Cheers
> > Mike
> >
> >
> > On Tue, Dec 03, 2002 at 01:45:39PM -0700, Marty Braithwaite wrote:
> > > We have a custom approval workflow tied to the personal expense
transaction
> > trip_ewt.  The users enter their expenses into workplace, the trip is sent
to
> an
> > approver's inbox for approval or rejection.  The approvers access their work
> > items via the workplace inbox and the only functionality they are given from
> > there is to click on the work item, view the trip details and approve,
reject
> or
> > send back for changes.  It doesn't happen very often, but once in awhile we
> find
> > a work item that has been reserved by the approver and just sits there in
> > process.  I know how to fix it, but can anyone tell me how this might be
> > happening?
> > >
> > >
> > > Thanks in advance,
> > > Marty Braithwaite
> > > CPrail SAP Sustainment Team
> > >
> > >
> > > ------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT
> > ------------------------------
> > >
> > > Computer viruses can be transmitted via email. Recipient should check this
> > email and any attachments for the presence of viruses. Sender and sender
> company
> > accept no liability for any damage caused by any virus transmitted by this
> > email.
> > >
> > > This email transmission and any accompanying attachments contain
> confidential
> > information intended only for the use of the individual or entity named
above.
> > Any dissemination, distribution, copying or action taken in reliance on the
> > contents of this email by anyone other than the intended recipient is
strictly
> > prohibited.  If you have received this email in error please immediately
> delete
> > it and  notify sender at the above email address.
> > >
> > >
> > > Le courrier ilectronique peut jtre porteur de virus informatiques.  Le
> > destinataire doit donc passer le prisent courriel et les pihces qui y sont
> > jointes au ditecteur de virus.  Lexpiditeur et son employeur diclinent toute
> > responsabiliti pour les dommages causis par un virus contenu dans le
courriel.
> > >
> > > Le prisent message et les pihces qui y sont jointes contiennent des
> > renseignements confidentiels destinis uniquement ` la personne ou `
lorganisme
> > nommi ci-dessus.  Toute diffusion, distribution, reproduction ou utilisation
> > comme rifirence du contenu du message par une autre personne que le
> destinataire
> > est formellement interdite.  Si vous avez regu ce courriel par erreur,
> veuillez
> > le ditruire immidiatement et en informer lexpiditeur ` ladresse ci-dessus.
> > >
> > > ------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT
> > ------------------------------