You are viewing limited content. For full access, please sign in.

Question

Question

Workflow Designer Validation - Chaining HTTP Activities through While & For Each activities

asked on August 6, 2015
 
 

This looks like a validation error in the WF designer but maybe I'm going about it entirely wrong.

 

Goal

To have a workflow establish an http session in a web app and perform a routine per document and not trip over other sibling workflows.

 

Issue

If I have the workflow login and logout of the webapp, with some activities in between, it appears this will cause conflict if say 40 of these workflows fire at once. They'll end up logging each other out of ASP.net sessions and stumbling over each other.

 

If I have one workflow login, then try to loop two activities using either a while or a for each, the activity after the loop won't validate.

 

 

Any advice appreciated,

 

Carl

 
0 0

Replies

replied on August 6, 2015

Did you add the loop after you'd already set up the other activities? Activities inside of loops have their own scopes, so that's would be why you're getting the validation error on the "Logout of Forms" request. Can you set up so you can get the cookies from a separate activity out of the loop?

2 0
replied on August 6, 2015 Show version history

I did add the loop last and that makes sense. It would be nice if loops could pass the latest instance of the tokens from the activities within, to activities outside the loop.

 

My workaround is to add in a non-necessary HTTP activity to basically refresh the page outside the loop just to pass cookies on to the logout activity. Wasn't sure if there was a cleaner way around this as I'm not sure this will work with all web applications going forward.

 

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.