I have a multi-step Sharepoint workflow in task list A that starts when a new task is created in that list and creates a task in another list, B. When that task in list B is completed, I would like the workflow in list A to create another task in list C.
I am using Sharepoint Designer 2007 to build all of this and at the moment I have this represented by multiple steps. So, step one is to create the task in the other list, and store its ID as a variable. Step 2 is conditional on a value in the task created by step one being marked complete, and it creates a task in the next list, and so on.
However, when I run the workflow, it marks its status as complete as soon as the item in the first list is completed, and does not go on to create the task outlined in Step 2 of the workflow.
I would like to know why the workflow is marking itself complete at the end of step one, and why the subsequent steps are not executed. Thanks in advance for your help.
I feel some problem with your logic.
You should have two workflows for doing this task
Workflow associated with list A to create a task in list B
Workflow associated with list B to create a task in list C
I shall explain it step by step.
You need to create a hidden field in List B to store list A's ID
Create a workflow associated with A on item creation for creating new item in B and copy the A's ID in B's hidden field
Create another workflow associated with list B for creating new item in C. You can get the A's record by comparing the A's id field with B's hidden field
Related
I need to create a sharepoint list for task assignments. There is a predefined list of people to whom task should be assigned (Note: it does not need to be a sharepoint list, its just an example of displaying the needed data - employees names):
Ideally, the 'Assigned to:' column would automatically populate in the demonstrated manner:
Meaning, whenever a user adds a new element, he puts another Task, the assignment is done automatically in the given order. I've tried every idea that I came up with and nothing worked.
Any solution here highly appreciated.
I came up with temporary solution which assings random people [out of given 3] to newly created tasks. Solution + results below:
Resulting list:
Now, I need to replace the "rand" function in "Get item" [middle section] in Power Automate with anything that lists employees in given order, not randomly. Please advise
Working solution:
Seems kinda basic algoryhtmic problem.
What I suggest :
First load list of employees (Get Items activity)
Then use the ID column of the newly inserted item and apply the modulo of number of employees to get the index of the employee to assign the task to
then grab the nth employee login to assign the task
I'm having a site workflow and I'm creating new list item with status column value as "Pending" in one step and in the next step I want to wait for the same newly created item to update its status column value as "Approve/ Reject".
I want to use site workflow only so is there any way to wait until the current item update (item created in previous step.)
Items created by a workflow do not trigger a second workflow by design to prevent runaway recursion.
The item created by the site workflow could be assigned a workflow with a modify trigger to allow it to run as soon as it is edited by a user. This list workflow can validate the changes made to the item and take action on valid or invalid data.
I'm creating a WF with SharePoint designer 2013.
The work flow should be approved by 3 company members. So, I added a new column to my custom WF task list called "Approval stage" which is a choice column and should has values "Analyst, Reviewer and Manager".
When assigning a task for each user, I need to set the value of this column.
For now, I can update it only after the task is finished (approved or rejected). But I need to set it in the assigning process.
How can I do it??
When you create a task you will get an output as an ID on the basis of that you can update the field related to that task item.
I'm currently working on a nintex list workflow for List A. I want a certain step in this workflow to run when an associated folder for the item in library B is modified.
For example:
User adds document to Item 1 in Library B
This then fires Nintex step to change status of Item 1 in List A
Any suggestions?
You could make a new workflow on Library B which updates a status column in List A when the document is added. In list A workflow you can use "wait for item update" shape to run you steps once the status was changed.
Create a list level workflow in library B, change the trigger settings from manual to Create or change item. Then configure it so that it queries for the item in List A using the common field(lookup field), Update the item.
I have 2 lists: List A and List B.
My goal is to copy over an item in List A to List B.
In SharePoint Designer 2007, here are the available Workflow commands:
- Create List Item
- Update List Item
- Copy List Item
Which command creates a list item in List B "if it does not exist", and updates the list item in List B "if it exists"?
I had this same question yesterday at work. Here is how I solved it today.
Lists:
Parent: List A
Target: List B
Create the workflow and associate it with the Parent List.
The workflow can start however you please.
You will need 3 Steps in your workflow.
Step 1: Create a workflow variable and use a lookup to set the variable to the Title (this can be any unique field) of the Target list. I chose the Title field because I knew it would be unique to each item.
No conditions required.
Action: Set Variable:Foo to Bar (where Bar is the field you chose to match against)
Step 2: Check if the variable you just assigned equals the title (or unique field of your choice) of the item you just created/edited in the Parent list.
So your condition will be: If Variable:Foo equals Bar (where Bar is the field you chose)
and your Action will be: Stop the workflow
Step 3: If we make it to step 3, then our variable did not match an existing item
No conditions are required in this step.
Action: Copy Item then stop the workflow.
That's it!
Additionally, if you'd like to loop through your lists and process everything, this article was very helpful for me:
SharePoint Looping Workflow - How to: Loop through and process all items in a list
I hope this makes sense. And I hope it works for you as well as it has for me!
Your workflow will need to check list B first. If the item exists then it will need to "Update List Item". If it does not exists, it will need to "Copy List Item".
So how can you check?
There's a great article on doing that here:
http://blog-sharepoint.blogspot.com/2009/08/spd-workflow-test-if-value-exists-in.html