De-activation / removing of workflows

[Robert van den Berg]

I tried it just now but the change of status does nothing.... Is
apparently only a setting for information....
 
But when you go from the workflow builder start screen in the menu to
"Additional data - Agent assignment - Maintain" and then go to the
Attributes, you have a checkbox for "Locked for instantiation". This
prevents the workflow to appear in SWUI so the workflow can not be
started. I think that this is the option to "de-activate"  the workflow.
 
Just for your info on this Friday ;-)
 
Kind regards,
Robert
 
On Sep 2, 2009 14:16 "Mike Pokraka" <wug at workflowconnections.com>wrote:
> No idea, never tried starting an obsolete WF. Should be easy enough to
> test on a dummy WF.
> Cheers,
> Mike
> On Wed, September 2, 2009 10:53 am, <wug at bergtop-ict.nl> wrote:
> > Mike,
> > thanx for the reply. 1 small question: do you know if the change to
> > status
> > "Obsolete" also prevents the workflow from starting (manual for
> > example)?
> > (I normally don't change this status, it is always "undefined")
> > Regards,
> > Robert On Tue, 1 Sep 2009 14:58 , Mike Pokraka
> > <wug at workflowconnections.com>sent:
> > > Definitely
> > > wouldn't suggest removing them. 6 years in accounting terms is
> > > short, well below many archiving retention times.
> > > So if your auditor needs to see an approval of a PO from 4 years
> > > ago the
> > > old WF definition is required to display the archived WF log.
> > > I don't see any issue with having the unused WFs just harmlessly
> > > existing.
> > > You could mark them as obsolete and add a visual indicator into
> > > the name
> > > and/or abbreviation.
> > > Cheers,
> > > Mike
> > > On Tue, September 1, 2009 9:28 am, 
> > > wrote:
> > > > All,
> > > >
> > > > I am working on an evaluation of existing workflows
> > > in both production and
> > > > development.
> > > > These are workflows which are built in a period of 6
> > > years. A lot of
> > > > development is done, subworkflows are created, in new
> > > > versions replaced by methods, replacement to OO
> > > classes, etc.
> > > >
> > > > A number of workflows are no longer used. We are now
> > > evaluating what to do
> > > > with these workflow definitions.
> > > >
> > > > Does anyone know the approach of SAP? Is it possible
> > > to de-activate these
> > > > workflows? (and then I don't mean to de-activation of
> > > the start-event,
> > > > this I knew already ;-) Or is it advised to remove
> > > these workflows?
> > > >
> > > > Best regards,
> > > > Robert
> > > >
> > > > _______________________________________________
> > > > SAP-WUG mailing list
> > > >
> > > >
> > > >
> > > _______________________________________________
> > > SAP-WUG mailing list
> > _______________________________________________
> > SAP-WUG mailing list
> > <SAP-WUG at mit.edu>
> > <http://mailman.mit.edu/mailman/listinfo/sap-wug>
> _______________________________________________
> SAP-WUG mailing list
> <SAP-WUG at mit.edu>
> <http://mailman.mit.edu/mailman/listinfo/sap-wug>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090904/3a636821/attachment.htm