Search

SharePoint Workflow: OnTaskChanged Doesn't Respond When Allowing Multiple "Assigned To" Users by boulderbum

Closed
as By Design Help for as By Design

6
Sign in to vote
0
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 273487
Opened: 4/25/2007 4:20:37 PM
Access Restriction: Public
0
Workaround(s)
4
User(s) can reproduce this bug
If you modify a task list to allow multiple selections for the "Assigned To" column then update a task through the SharePoint API, not only with OnTaskChanged not respond, but the workflow will lock the task so it will no longer be manually editable.
Details (expand)

Product Version

 
Product Language
 

Operating System
 
Operating System Language
 

Architecture
 

Priority
(1=blocking, 2=important, 3=nice to have)
 

Severity
(1=major functionality issue, 2=important functionality issue, 3=nice to have)
 

Steps to Reproduce
 
Actual Results
 
Expected Results
 
Component Usage
(any information on your scenario that may help in investigating your issue)
 

How often does this happen?
Always Happens

Have you seen this problem in other versions?
No, this is new to the most recent version

File Attachments
0 attachments
Sign in to post a comment.
Posted by boulderbum on 5/1/2007 at 12:53 PM
"By design"?!? You've got to be kidding.

I can see accounting for both singular and multiple "Assigned To" values, and I can see (but would dislike) just not supporting multiple "Assigned To" values, but the current behavior is erratic and inelegant.

Not firing OnTaskChanged is bad enough, but there's no way the intended design called for the workflow irreparably locking the task as it does.

Treating this bug as you have leaves me with an even lower opinion of the quality of the SharePoint product.
Posted by Vaasu on 11/18/2008 at 1:03 AM
Even I am facing the same issue.

Could anyone please help in solving this issue or suggest an work around?
Posted by QUYENHUH on 12/9/2008 at 7:17 PM
Same issue. Disappointment SharePoint Workflow
Posted by Fiodir on 12/9/2009 at 3:36 PM
Is there any solution in future release or hot fixes to fix this issue? If this is by design, the design is a flaw. and needs to be corrected.
Posted by prashanthspark on 1/21/2010 at 4:25 AM
PrashanthSpark
I have development envirnoment where it stopped custom workflow working suddenly !! :(
Now i have UAT & this stops abruptly like this seriously very bad. iam nt able to view in attached event onTaskChanged

Please anyone let me know how can i fix this! i tried using three state workflow it works thier but some issue for custom one's
© 2010 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement