Re: MOSS 2007 Out of the Box Workflows Broken
- From: Claudia <Claudia@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 21 Nov 2007 08:00:00 -0800
I will add that choosing the Allow Multiple Seletions also prevents users
from editing lists in datasheet view, exporting lists to excel, and using
that field in custom workflows through SharePoint Designer.
Are you also getting the Form is Closed error when you try to view or edit
workflow tasks?
"gregmaass@xxxxxxxxx" wrote:
Thanks much, Claudia- #1 and #3 both were causing problems which have.
now gone away. Multiple selections for the Assigned to field also were
causing other problems- user filter web parts apparently do not work
if you are filtering on an assigned to field that allows multiple
fields.
On Nov 20, 1:38 pm, Claudia <Clau...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Not entirely. I've figured out the following:
1) Regarding the email issue: This happened as a result of us changing the
default system column "Assigned To" to allow multiple selections. When we
changed it back to the default setting the random emailing stopped.
2) We also changed the choices of the default system column "Task Status" to
match the values that our organization uses for project task tracking. Since
theworkflowuses the default Task content type to manageworkflowtasks we
figured that this is why the system was not completing the workflows so we
changed those back as well.
3) We also discovered that if you have aworkflow(the default parallel and
serial) that has the option "Update approval status" marked as yes and do not
have the document library or list set to "Require content approval" theworkflowwill not complete and will throw an error.
4) Lastly, the Form is Closed error has not be resolved. We have a call in
with Microsoft Tech Support and they have not been able to diagnose the root
cause. We did find that is recorded on the server as error 7056
'ows_TaskStatus' is a duplicate attribute name. Once aworkflowcompletes we
are no longer able to view or edit theworkflowtask. We can create a clean
web application and restore everything but the document library and it works
fine. Once we restore the document library with custom content types the
error starts and infects all sites in the web application.
"gregma...@xxxxxxxxx" wrote:
On Oct 10, 12:37 pm, Claudia <Clau...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
I am having major issues with workflows. Example: An parallel approval
workflowis created on a document. It is kicked off properly and the user is
able to view the document and the task from the link provided in the email.
When the task is marked as approved theworkflowdoes not complete. Instead
it kicks off an email to 5 users (who are not realted to theworkflowthat I
can see) saying that the taskhas been reassignedto them. When they click
on the link to edit the task an Infopath Form Services error is thrown and a
message The Form Has Been Closed appears. You can get to theworkflowfrom
the document menu, but not from the task list itself. I'm officially stumped
and under the gun to get the issue resolved. Can anyone point me in the
direction of some possible resolutions? Thanks in advance.
Have you gotten a fix for this- I have the exact same issue.
- References:
- Re: MOSS 2007 Out of the Box Workflows Broken
- From: gregmaass
- Re: MOSS 2007 Out of the Box Workflows Broken
- From: gregmaass
- Re: MOSS 2007 Out of the Box Workflows Broken
- Prev by Date: Re: owstimer.exe using excessive memory
- Next by Date: Re: Fulltextsqlquery and null values
- Previous by thread: Re: MOSS 2007 Out of the Box Workflows Broken
- Next by thread: Re: Infopath not working
- Index(es):
Relevant Pages
|