You can mark specific Views or Forms to be available anonymously. For example, you may wanth to expose a View / Form to public users who do not have user accounts in your organization's Identity Store. Enabling anonymous access on a View / Form would allow these external users to access that specific View / Form without having to provide credentials.
It isn't quite as simple as enabling an anonymous runtime. A workflow task must be assigned to a destination. That destination user is then the only one permitted to action the task.
It IS possible to do this, but a bit of extra work is required. I've seen this done by assigning tasks to a generic account, and then using logic built into task action pages to authenticate and authorize the individual user. This isn't exactly the same as what you want, but the same ideas should apply. If you want an "anonymous" user to action a task, you need to assign the task to someone (perhaps a ANONK2USER), and then have the smartform run under the context of that ANONK2USER.
There may well be other ways of achieving this, too, but that's the way I'm familiar with.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.