I have the requirement to make a workflow fire when a task is modified and after it has been completed.
After the task has been completed, I am trying to set it back to an uncompleted status. From another work flow I update the task 'status' from 'completed' to 'not started'. The status gets updated but after the task is completed the second time the status is not updated from 'not started' to 'completed'.
The reason seems to be because i am unable to update the task's 'outcome' column from 'completed' to '' (blank). Is there a way to update this field non programatically?
Specifically which column in the Task list stores the outcome of the 'Save Draft' or 'Complete Task' button?
Many Thanks, Nav
You can have more than one status-type field and use them for different purposes.
I have a task list that has a single-line text column, a Status column and a Modified By column (among others). It appears that the default view has the single-line text column taking up all the room it can, making the status and modified by column go to 2-line formatting. I'd like to force the Status and Modified By columns to display on only one line, and let the single-line text go to 2-lines if it needs to. How would I go about getting the single-line text column to lose priority for space? EDIT: I did the cheap fix of making the column names larger, but would like a better solution
We have a InfoPath Form Library with Visual Studio Workflows on an MOSS 2007. Now to some of the form we're missing tasks in the tasklist and there isn't a status in the column of the workflow. But the workflow had been started ... we're noticing, that all the affected forms have in common that the workflow (and the tasks of course) was finished. Has somebody an idea what happened? Is there maybe a process or a setting that "cleans up" finished tasks and workflows?
I don't suppose there's a way to get an InfoPath task form to save it's state once it's submitted. In a workflow I don't delete the tasks, I just set them to complete. I don't pre populate much of the task forms as it's down to the user to complete the form. Some of the task forms are quite important and I'd like them to retain their entered fields after the workflow has moved on, or even completed itself.
/. I have contradictory observations: When John adds an item to the library while working from W2, the workflow is initiated but goes to Stopped status, and the other list is not updated. When John... is configured to allow the workflows to be initiated. I cannot seem to find any aspect of SP groups or users or permissions which would affect a user's ability to initiate workflow from one workstation but not another. Am I looking at some Active Directory / Windows Domain permissions issue here? Has anyone seen this kind of issue where Workflow execution ends in Stopped status, but only
SharePoint workflow by nature is document centric in that you have to have a 'thing'; A object for the workflow to run on. This object can be a document, form or simple list item but this thing has to exist as the anchor and context of the workflow. What I've started thinking about is a more abstract sort of workflow and how it would be useful in SharePoint. Workflows are user driven processes after all but the workflow or business process might want to trigger on an event instead of a user needing something done. So perhaps an accident happens for example. The event might be manual
I have an initial workflow in Sharepoint Designer that triggers whenever an item is created and also whenever an item has changed in the 'Employee' list . Within second workflow I am updating the 'Employee' list and the workflow above is triggered. Is there any way I can check in the intial workflow if the item has been updated by a user or if it was updated by a workflow. In the case if the item was updated by a workflow I would not want to trgigger it. Many Thanks,
I have a requirement to design a multi level approval workflow using SPD 2007. The workflow has three levels of approval. If the 1st or 2nd or 3rd level of approvers rejects the task it should go back to the previous level of user to continue with the same workflow instance. The workflow should not stop since when the InfoPath form is updated in the Forms library, a new WF instance will be created if there is no active task on that workflow. Has anyone worked on a similar requirement? If yes, please let me know. Also, let me know if it is possible to move back and forth between workflow
I'm looking at building a solution that will use this as it's base: Content Types as Statuses and I'd like to know if it's possible to create a DVWP form that only allows the first form, eg the initial status, to be filled out. After the initial status is created, when displaying the form, have a workflow button connect to an initiation form, which will in turn update the item and content type. I'll need to not let the form display the 2nd or 3rd status until the first is completed. Is this possible? Or a better question, does this question make sense LOL?