Need a real task decline action

[hager]

In Windchill 10.0 we had a real task decline action: when a task is assigned to many users, a user had the ability either to accept the task - the task disappeared in all other user's task list - or to decline the task - the task disappeared from the user's task list and no changes for other users

Since Windchill 10.2, the accept action is still the same, but the decline action changed: you must first accept, before being able to decline (a little bit crazy, no?)

After declining the task is still in your task list and reappears by all other users

See CS39267

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS39267&art_lang=en&posno=1&q=decline%20task&source=search

Actually, this action is only an "undo accept" action

We need a real task "refusal" like before: I don't want it, I don't want to see it anymore!

Of course, the last user should not be able to "refuse" the task

[JeffZemsky]

There should not be any change to this - the behavior in the article is still consistent.  This seems like a bug - do you have a call#?

[BenPerry]

Jeffrey Zemsky‌,

In the screenshot below, the task is assigned to the Designer role.  The Designer Group group is the role on the Change Notice team.  And 5 users are in that group.  Therefore 5 users have this task.  This might be a unique use case, but in general the task is "Potential" for 5 users.

The intention is that this user clicks on Decline for ECN0033612 in order to get it "off their plate".

You think that it seems like a bug that we get the error message instead of the task disappearing from this user (but remaining as Potential for the other 4 users)?

[hager]

Hi Jeff,

Yes, I opened Call C12924930

In Windchill 10.2, the behavior is as described in CS39267... but different than in 10.0!

I get now the same message as Ben.

After Accept+Decline action, the other users will get a new email for task notification... completely crazy!

And absolutely unusable

[BenPerry]

Jeffrey Zemsky‌‌,

I'm following up on this one.  Can you please revisit my post above.  Do you think it is a bug if a user gets an error message for a Potential task that they attempt to decline?

[hager]

Hello,

After cross checking with the TS, it seems to be the same behavior as in a standard 10.0 installation. So the TS convinced me we probably had a customization on this function. But I cannot find it back!! (our former customization expert left the company...)

Anyway, the current behavior, which probably "works to spec", is not helpful

What we need is a really "reject" function as described by Ben

[JeffZemsky]

Ben - sorry I had not gotten to reply.  We did verify with older releases that it did work the same so its not a bug - there was no change in functionality.  Should probably update the idea above to reflect that so there is no confusion.

[cmarquardt]

Agreed with Jeff that I think this is the way it has always been, but this behavior as designed is just not helpful.  Decline should work exactly like Accept, where it filters it off of your plate but it remains on everyone else' task list.  It is honestly confusing to me that this is not the way it functions. ¯\_(ツ)_/¯

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.