Skip to main content

Can someone from SourceCode explain to me how on earth this is possible:


I had a destination user of Originator's Manager in my first Activity.


The Originator I tested with did not have a Manager, ok. So I expect the Instance to go into an Error State and show me something meaningfull to solve the problem, but nooooooo, instead the user submitting the form got an error when trying to submit the InfoPath form!


When I looked at the console I saw that the Destination Rule for the 1st Activity is resolved BEFORE the process Start is attempted?


Furthermore, the Process was stuck in a RUNNING state and not an ERROR state?


How is it possible that the start of the process is affected by something that is supposed to happen disconnected from the process start, i.e. an Activity in the Process? Maybe that is why it takes so long to submit a form and why it almost without fail times out the first time a form is submitted.

I just had my good buddy brandon help in testing this on SP1 We were able to submit the form without error. When I looked at the process instance it shows it as active. However, when I look under worklists in the workspace under management , it shows it without a user. Then we can now delegate it to someone. Looks like this is how it should work and now does work in SP1

Hi Deon,


Is your process started synchronous or asycnronous? It almost sounds like it's a sync start.


Also with regards to the long InfoPath start time the first time you submit, have a look at the web.config file in the runtimeservices folder where there is a little comment about changing the submit between sync or async and why it had to be done that way.


Cheers,


G

Thanx Gerhard,


I can't see any comments in my web.config, it is configured as follows:


<appSettings>  
  <add key="SubmitAsynchronously" value="false"/>
  <add key="StartWorkflowAsynchronously" value="true"/>
 </appSettings>


What are the implications of changing this?


With SP1 the client submitting the InfoPath form still get's an error message the 1st time he submits but not when submit is clicked a second time, unfortunately this is a big problem since there are now 2 instances running for the same form.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings