Startup Workflow from URL - Arguments Not Being Passed

Permanently deleted user

September 16, 2014 20:27

Hi There,

I recently ran into an issue where a workflow that I've created will fail when I attempt to call it using the URL parameter at startup. Upon investigating in Fiddler, I found that the call to the workflow: 

 

http://SERVER/Geocortex/Essentials/Internal/REST/sites/SITE/workflows/FindPoll/run?ts=635464561005631352 where the arguments are passed into the workflow are 'null' rather than being populated with the correct values which would enable to allow the workflow to run.

The odd thing is that when I call the workflow from the 'I want to' menu everything works as expected. Has anyone else experienced something like this that they may be able to offer some suggestions?

Thanks,

-Warren

 

0

• 

  Bernard Macnab

  September 18, 2014 01:05

  Hello Warren,

  What is the format of the URL you are using to launch the site?

  What happens if you set the workflow to run on startup through Essentials Manager?

  0
• 

  Bernard Macnab

  September 18, 2014 02:56

  Hello Warren,

  When I launched your site I checked my Fiddler.  I found a few workflow related calls.

  http://maps.waterloo.ca/Geocortex/Essentials/REST/sites/PublicMap/workflows/FindPoll/run?f=json&inargs=...... This has all of the arguments set to a null value.   http://maps.waterloo.ca/Geocortex/Essentials/REST/sites/PublicMap/workflows/FindPoll/run?ts=635465549760766613

  This has some of the arguments set to certain values. The map service id and the layer id were populated with values.

     

  0

Please sign in to leave a comment.