How to identify that an event occurred outside the workflow?

[Ho, Eva Tak Wai]

Hi All,
 
The last comment that Andrew made is true in deed. If you still think having a step in the WF canceling itself is ugly, instead of using ApproveInteractive method, make the step a decision step. Once confirmed OK to unlock, subsequent WF step performs a background unlock at an appropriate time (eg. after all the notifications are sent).
 
Regards, Eva
-----Original Message-----
From: Rankin, Andrew AJ [mailto:Andrew.J.Rankin at BHPBilliton.com]
Sent: Thursday,22 August 2002 3:21 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: How to identify that an event occurred outside the
workflow?
 
 
Hi Christiana
 
Firstly if the ApproveInteractive method was asynchronous then it would have
a terminating APPROVED event, in which case there would be no need for the
'confirm end processing'. This would be the best way of handling the
situation, but if the method has to be synchronous and you want to use the
'confirm end processing', what about putting in a process control step just
prior to it, and in that process control you cancel the other wait step for
the  APPROVED event. This way when the event happens you won't have to worry
about your 'confirm end processing' being cancelled by the wait step. The
only problem then is if they don't actually approve it and it's done outside
of workflow in the meantime, your wait step is dead and nothing happens.
Another way to look your present situation is that if the wait step picks up
the APPROVED event and ends the workflow, why should the user need to
confirm end of processing? Maybe what you have is fine as it is.
 
Regards
Andrew Rankin
 
-----Original Message-----
From: Cristiana d'Agosto [mailto:cristiana.dagosto at au.pwcglobal.com]
Sent: Thursday, 22 August 2002 13:58
To: SAP-WUG at MITVMA.MIT.EDU
Subject: How to identify that an event occurred outside the workflow?
 
 
Hi All,
 
I'm using 4.6c and implementing a workflow to Process Leave. Employees will
be applying for leave via ESS and workflow will be triggered.
 
The work item goes to the manager for approval but depending on the type of
leave the manager's approval will not unlock the record. Instead the record
will be sent to a central area where a few other checks will be done. I
created a task that will execute ABSENCE.ApproveInteractive ie. the user
will be taken to the screen and upon saving it the record will be ulocked
(this will generate event APPROVED). This task is also set up with
indicator for Confirm End Processing switched on.
 
I also have a Wait for event APPROVED step that will terminate the workflow
- this step was set up because someone might unlock the record via PA30,
outside the workflow...can you see the problem happening? Well, when the
user executes the work item and saves the record, the event APPROVED is
generated and terminates the workflow before the Confirm End Processing
screen happens...
 
How can I identify that an event has been generated outside the workflow?
If there is a way of doing it, I will be able to control if the Wait step
will terminate the workflow or not.
 
Any other ideas?
 
Much thanks and regards
 
Cristiana
_________________________________________________________________
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.
 
EOM
 
NOTICE - This message and any attached files may contain information that is
confidential and/or subject of legal privilege intended only for use by the
intended recipient. If you are not the intended recipient or the person
responsible for delivering the message to the intended recipient, be advised
that you have received this message in error and that any dissemination,
copying or use of this message or attachment is strictly forbidden, as is
the disclosure of the information therein.  If you have received this
message in error please notify the sender immediately and delete the
message.