Reactivating deactivated event type linkages

[Martinek, Jerry]

Hi, once again, thank you for the prompt responses. I understand the points
and reasons and therefore I started the transport process.
 
For the record, in this particular scenario, the problem was caused by an
unacceptable default parameter setting for WF-BATCH.
 
When the id was setup it wasn't assigned a valid default printer value. So
when the object method called a function to create a smartforms spool
request which was then converted to PDF and sent to a selected agent, the
process failed. As soon as the problem was discovered, the id was adjusted
accordingly but by then it was too late.
 
Thank you for the clarification.
 
Jerry Martinek
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Monday, November 05, 2001 3:14 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Reactivating deactivated event type linkages
 
 
Hi Jerry/Alon,
 
Yes I agree with Alon.  An event only gets deactivated if there is something
 
technically wrong with the event linkage or the workflow version being
instantiated.
The automatic deactivate is to stop it causing havoc in your production
system.
So really the problem should be diagnosed, fixed in your development system,
 
and the new workflow version/event linkage transported through along with
the
reactivation.
 
Really that sort of error should never happen in production if your testing
is
thorough enough.  So I would also suggesting making a careful note of what
caused the
problem and  ensuring that appropriate checks are included in whatever
testing
and quality assurance procedures you have for workflow to avoid the problem
occurring in other workflows or future versions of the same workflow.
 
Regards,
 
Jocelyn Dart
Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email  <mailto:jocelyn.dart at sap.com> jocelyn.dart at sap.com
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
-----Original Message-----
From: Raskin, Alon (Soliance) [mailto:ARaskin at cps-satx.com]
Sent: Tuesday, 6 November 2001 10:00 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Reactivating deactivated event type linkages
 
 
 
I think the argument here from the BASIS guys is why is the workflow
deactivated? Obviously there was some sort of technical error (binding,
etc). If that is the case then they want you to fix the error, and then
reactivate the workflow in the source system and transport that
re-activation. Its better that all changes are made in the source system and
then transported rather then maintaining two versions of a workflow. Also,
one thing us workflow guys don't see is the bigger picture as far as system
landscape. For example, the fix you made probably needs to be transported to
all systems (including the re-activation of the workflow). This cant be done
if they allow you to manually activate the workflow. I also hate it when the
BASIS guys lock me out but I do see their point.
 
 
 
I am not sure what SAP's recommended approach for this is. Perhaps Alan or
Jocelyn want to comment?
 
 
 
Alon Raskin
 
Workflow Advisor - Soliance
 
(xtn. 3183)
 
 
 
-----Original Message-----
From: Martinek, Jerry [mailto:Jerry.Martinek at icbc.com]
Sent: November 05 2001 4:55
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Reactivating deactivated event type linkages
 
 
 
Hi, thank you for the prompt responses.
 
 
 
How is this managed in other installations and also, what is SAP's
recommended approach to this scenario? I understand that if the environment
is non-modifiable, the only way to solve this problem is via a subsequent
transport and etc.....
 
 
 
I can't see logic in going through the change control/management process to
reactivate a link.
 
 
 
Thank you,
 
Jerry Martinek
 
-----Original Message-----
From: Raskin, Alon (Soliance) [mailto:ARaskin at cps-satx.com]
Sent: Monday, November 05, 2001 2:23 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Reactivating deactivated event type linkages
 
My understanding is that your BASIS team is correct. You need to
re-transport.
 
 
 
 
 
Alon Raskin
 
Workflow Advisor - Soliance
 
(xtn. 3183)
 
 
 
-----Original Message-----
From: Martinek, Jerry [mailto:Jerry.Martinek at icbc.com]
Sent: November 05 2001 3:56
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Reactivating deactivated event type linkages
 
 
 
Hi, I am looking for help/confirmation on how to 'reactivate'  a deactivated
event linkage due to a prior system error.
 
If the WF system deactivates an existing event linkage definition due to a
problem, how do you reactivate it after the problem is corrected?
 
I ran into this problem and due to the fact that the environment is
non-modifiable, the only way I can reactivate this linkage is via a
subsequent transports. SWU0 fails due to the environment state.
 
I was under the impression that this was something the WF administrator
should be able to restart once the problem is corrected. Our Basis team is
questioning this statement and therefore telling me I need to use a
subsequent transport to reactivate.
 
Thanking in advance
Jerry Martinek
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20011105/3a1cf552/attachment.htm