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 steps in an approval workflow using SPD 2007. Is it possible to use any custom actions to do this?
Unfortunately the SharePoint Designer 2007 workflows are sequential which means you cannot repeat steps. Your two options are to either instantiate an instance of the workflow for each pass forward, or to try and duplicate the steps which is a really bad idea and should only be used in very specific and simple situations.
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
Within my workflow using SPD I am using the "Create New Item" action to create a new Task list item this is fired when a holidayrequest item is created. My problem is I cannot see how to create/store a link back to the orignial holiday request item that created the task, so I can display this in the Task's edit form.
I have an InfoPath form that starts a workflow (on item created). The business requirement is that after submission form must be read-only (no changes to the initial request can be made). However workflow must change certain properties of the form (e.g. approval time, approval phase etc.). By default SharePoint workflows run under initiator account, however I am wondering would you recommend creating an event handler that is going to kick start a workflow under system account. Workflow would than be able to revoke all the contribute privileges but still be able to update the form during
nature. Typical workflows are about the document, like getting it approved or reviewed or some such. In this case the workflow needs to create new documents, InfoPath forms perhaps. Using task forms... but I can't find anything ideal, or even just something I'm semi happy with. I'm hoping that people could answer with ways they can think of for using a workflow to drive further document creation...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
of departments is not possible since they can't be expected to know the appointed representatives of every department. I can create a task through the "Create List Item" action, but the workflow is marked...I am trying to create a workflow on SharePoint 2007 that should go like so: User adds a new item in the "Faults" list. When creating it, he ticks the boxes for whatever departments needs to address... is finished. The problem: if I create a workflow in SharePoint Designer 2007 and create multiple steps checking to see "if X department was ticked then assign task to user", it will wait until
of work level that can be suggested. I should also note that keeping the list linked with the spreadsheet is undesired. We want to be able to download the spreadsheet as a reference. Because... to Spreadsheet, but it does not appear to support automated subdivision of the list items into separate worksheets. I do not know if Excel Services that come with MOSS are capable of it, but we do not have MOSS so we cannot consider it an option for now. EDIT It seems that by mentioning "out-of-the-box", I am implying that I'd prefer something quick and simple. Let's dispel that. I do a lot
I have an InfoPath form embedded in a MOSS 2007 page. The form is for requesting approval for a project. The submit button submits the form data to a form library. That triggers a workflow to get approval for the request. So far, my workflow uses the "Collect Data From User" action and the "Send and email" action. I configured data collection option so that there are two inputs: two radio buttons for approve/reject and a comment field. I built the email body and subject using dynamic strings and variables from the form data. I would like this approval process to be simple for the person
Within my workflow I am using the 'Collect Data from user'. I want to send a custom email (by turning of alerts on the Task list) and using the Send Email action. My problem is I want to send a link with the task to approve in an email to the user the task has been assigned to (approver). But the action ''Collect Data from user' pauses until the task is edited which won't happen because I haven't sent the details to the approver via an email! Is there any way to get around this? Or get a reference from a newly created task back to item that created it from the 'Collect Data from user
Does anyone know what permission levels are required to allow a user to create content but not approve it? I’ve just spent the afternoon trying this and am more confused than when I started. For instance… If I add a user into the Designer site permission group I can create pages – excellent, just as I would expect. If I create a new site permissions level - let’s call it ‘customer-designer’ - by copying the Designer site permission level and then assign this ‘customer-designer’ level to a new site permission group. I then add my user into the new group and… I cannot create pages, even