I filed this with support but thought maybe one or two of you might be interested to know about it:
We came across a scenario in one of our workflows that causes an error that should be caught and either avoided or reported better in TeamSite. The situation is when a user inadvertently selects a privatized file and starts a job including that privatized file. This happens because some of our users when deploying an entire site will simply execute the "select all" button and then start the job. The job has an updatetask that simply updates another workarea in the same branch with the files attached to the workflow. The updatetask results in a conflict, and the conflict window shows that the privatized file is in conflict, but the error message (the comment field) in the conflict window shows "Unspecified error found during update" and it shows the privatized file as being a deleted file as opposed to identifying it as a privatized file. There is no way to proceed through the conflict unless you remove that privatized file from the task - it is stuck forever in a state of conflict. This is bad because the average user doesn't know what a privatized file is, and since the resolve conflict window doesn't indicate anything about the fact that the privatized file cannot be updated into another area, the user has no clue how to remedy the situation. This should be fixed by not allowing a privatized file to be included in an updatetask or at least providing a better error message. The fact that privatized files are allowed to be included in an updatetask seems like a bug to me.
This problem can be seen by creating a simple workflow that utilizes an updatetask to move files from one workarea to another, attaching a privatized file to a job and looking at the Resolve Conflict window that occurs as a result of the updatetask not being able to complete.
Dave SmithSr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com
