De-activation / removing of workflows

[Mike Pokraka]

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, wug at bergtop-ict.nl wrote:
> All,<BR>
> <BR>
> I am working on an evaluation of existing workflows in both production and
> development.<BR>
> These are workflows which are built in a period of 6 years. A lot of
> development is done, subworkflows are created, in new
> versions&nbsp;replaced by methods, replacement to OO classes, etc.<BR>
> <BR>
> A number of workflows are no longer used. We are now evaluating what to do
> with these workflow definitions.<BR>
> <BR>
> 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?<BR>
> <BR>
> Best regards,<BR>
> Robert<BR>
> <BR>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>