I just submitted an RFE to Remedy Support.. I would like to know the user
communities thought on it..
Right now it is possible to disable workflow. However during the process of
development whenever some piece of workflow is rendered as obsolete and marked
as disabled, this, if not manually removed, continues to remain in the system
and as the system grows one can end up with a whole lot of redundant workflow.
ITSM 7 is a great example.
With time this could become unmanageable if not deleted periodically.
It would be nice, instead of just having the ability just to disable objects,
if there was some function that could 'mark objects for deletion'. So if the
Enable/Disable flag could be extended to Enable/Disable/Delete.
All objects 'marked for deletion' could then either periodically or manually be
actually deleted by invoking some function 'Delete Obsolete Objects'.
The advantage of having this would be a migration process from one environment
to another, where a developer could export all objects with the inclusion of
those that are marked for deletion so that these would be marked for deletion
on the server that you are exporting all the new workflow which includes
objects 'marked for deletion'.
>From a developers as well as an admins perspecitve I think this would be a
>great idea to implement.
Please do let me know what you guys think of this idea..
Cheers
Joe
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
