Hi Catherine,

Here is one of the scenario. I want to test /design a Form that could be filled by the general public.  In this case, there's no login asked for that person to fill the form.

If I use our VAR kit, then that public user will need to authenticate to the Form to initially fill the form and this is not what I want to test/demo.

The main difference between both Public and Authenticated Forms is that the Authenticated user does get a dashboard of what was previously submitted and a list of pending approvals, but for the Public user, I don't think they can followup, well I can't really tell you because I can't simulate it in my VAR kit.  If I need to demo it, I would need to ask one of my customer that bought it and ask him if I can use his system to test out something or demo it to another customer (Which is not really a good idea).

Because there are important and subtle differences in the behavior between Forms Portal and Basic Form, it then becomes important to see them, test them and use this in our development testing, POC and Demos.

The second scenario is that I am on the technical side and before I start designing the official process at a customer, it aways starts on my VAR system at the office.  if I can't test real life scenarios here with my VAR kit, then I'm kind of loosing my time as I have to go onsite to customer to do the job (for customer that doesn't allow us remote access.  It then becomes a matter of productivity to me.

The last thing is... if I can't test out all features, then it becomes difficult to test out and make efficient New Feature Request based on facts and real tests scenarios.  Most of the great ideas for New Features are coming from trying to setup something on Demos or POC, and this is happening when we are trying to get into new market and respond to new Business Processes.

Let me know if you have additional questions,

Best regards,

Daniel