Hi,
I just wanted to give a bit of advice on this. I wouldn't implement this.
Why do I say that?
We thought of the same thing and I've heard of this asked before and it's just not a good idea unless you can really pinpoint WHEN to cancel.
Example:
I'm an end-user and I want to order a new computer with 'x' features and accessories. I submit a catalog item. It goes through a form of asset management check first to check current stock and see if we need to buy new...or we have prior used equipment available, if new is needed...it goes to finance for approval and they see if the department charge code entered has appropriate budget/allowance for it...then once approved it goes to procurement to purchase the equipment, etc...then it goes to local IT to set up date/time to do installation and initial setup, etc...
So...given your question about allowing users to cancel...WHEN would that happen? You want them to be able to cancel at any point? So it could after it was purchased and already with IT? ...you may see the issue here.
What we've recommended is that they contact the Service Desk if they wish to cancel, and the Service Desk will work with the relevant teams that have tasks and let them know of the cancellation and organize it a bit more than an end-user clicking a cancel button screeching everything to a sudden halt.
So there may be other catalog items where cancelling isn't as impactful...but I don't think globally offering a cancel option is a wise choice.
Just my 2 cents.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
