Hi all, I have a list WF called “Submissions” that is associated with List A. Within this WF, I have an App Step that includes the “create item in List B” logic. The scenario is:
- Users goes to List A to enter information and Submit
- Once submitted, the WF in List A kicks off
- List A’s WF has logic that will add the newly submitted information from List A to List B
- Information entered in List A is then added to List B as a newly created item
- List B has a WF called “Review” that starts a Task Process for Administrators and notifies them
On both of the WFs I have the Start Option as “Start workflow automatically when an item is created”.
When a user enters information in List A the WF kicks off no problem. But when the information from List A is added to List B, the WF in List B does not kick off at all to start a Task Process for Admins.
The logic is sound but I don’t have any idea why the WF in List B is not kicking off when a new item is added from List A.
Can someone enlighten me on how this is not working and advise on a fix?
Keith is correct. The second workflow will not start. It is by design to prevent recursion (workflow triggering workflow triggering workflow, etc.)
I messaged you in private chat. Â It is easier than going back and forth
Really? Wow, I’ve been told that I could do so using App Step. With that being said, how can I then accomplish what I need?
List A has different permission levels to List B. What I’m required to do is to have users with Contr perms to fill out form in List A. Once completed, List B will be populated with user’s input from List A.Â
List B has perms only for Admins for which they need to review and move the process along. Hence, the WF in List B.
If what you’re saying is true how can this be achieved?
You can’t kick off a 2013 workflow from an item that is created from another workflow. Â Start your task process from list A instead of list B.
