InfoPath Dev

Hi

We just purchased QRules,  and injected it into my Browser Form.

After I injected it,  I noticed that when I run the design checker that I now get errors about e-mail not supported in Sandbox solutions.   Our form has several cases where it will send an email to users (When Requests are open/closed etc.)

Does using QRules mean that we will not be able to send emails with our forms?

Thanks

Chris 

Hi Chris-

Thanks for your purchase!

It's not necessarily a limitation of qRules, but rather a limitation of the sandbox service.

You can workaround it by admin deploying the form. Is that a possibility for you?

No that is not a possibility.
Darn,  I wish I would have known that before we purchased this.   The email notifications are critical to this support form.

So using QRules means no email sends at all,  unless admin approved?
Has this always been the case?  

 Hi -

The issue is that forms with code in the Sandbox (published directly to the library) cannot have email submit connections. Here's a link with more info on this.

If you aren't able to admin approve your form, and this means you need to take a different direction, please contact [email protected] about a refund for your qRules purchase. Please reference this thread in the email.

If the form has be published directly to the form library and has to have email submit connections, it won't be able to also have code, whether qRules or custom code.

That's too bad,  we were really hoping to be able to use this.
Has this always been the case?  I noticed your blog post was published in March 2012.    I tried the demo out of QRules about a year ago,  and back then I thought I had it working and I don't remember seeing those warnings.

I think it would be a benefit to your customers to have this more clearly displayed/explained on the QRules products page. 
Something that says that this functionality would be lost in SandBoxed browser forms.  

Thanks!

Well, it has always been the case that forms with code cannot have email submit connections in them if they are published directly to the library. Here is the Microsoft page with the same information. It is not the case that functionality is being lost specific to qRules - any form with any code is going to have this issue in the browser.

I think for most of our qRules customers that are not using Office365, admin approving has not been an issue as an alternative.