Trying to not create a task but display an interface

You can't use that highlighted button on this task because it's for defining that Appian itself perform that action and not a human being.

You can configure it as a Quick Task, and this will prevent it from appearing in the Tasks tab, if that's what you want to do. When the process flow arrives at that Quick Task, it will spawn one copy and give that to the first user that arrives, and then spool up another empty one on top of that. Whenever a user arrives at that part of the process, that user takes up the next empty one and a new empty one is created until the process is terminated. The only way to get to it is to be activity chained in, and if the user leaves the process they will never be able to get back to it, so you have to define a timeout to kill the process some time after the quick task is assigned if it isn't completed.

You can also configure the interface as the Start Form of a process. That won't generate a Task, but the form will instead be loaded first when the user starts an Action. This, by the way, is the only way to create an Action on a Site. There won't be a Task unless there's other forms inside the process model. The process model associated with the Start Form won't even start until after the Start Form is submitted. If you only want a form, you can make a process model that does absolutely nothing. It only contains a Start event and an End Event and has a Start Form configured. Now that you can write to datastore and kick off other processes and other things from SAIL, that's a growing design approach. There are some in Appian circles moving toward process model-less applications.

You can't use that highlighted button on this task because it's for defining that Appian itself perform that action and not a human being.

You can configure it as a Quick Task, and this will prevent it from appearing in the Tasks tab, if that's what you want to do. When the process flow arrives at that Quick Task, it will spawn one copy and give that to the first user that arrives, and then spool up another empty one on top of that. Whenever a user arrives at that part of the process, that user takes up the next empty one and a new empty one is created until the process is terminated. The only way to get to it is to be activity chained in, and if the user leaves the process they will never be able to get back to it, so you have to define a timeout to kill the process some time after the quick task is assigned if it isn't completed.

You can also configure the interface as the Start Form of a process. That won't generate a Task, but the form will instead be loaded first when the user starts an Action. This, by the way, is the only way to create an Action on a Site. There won't be a Task unless there's other forms inside the process model. The process model associated with the Start Form won't even start until after the Start Form is submitted. If you only want a form, you can make a process model that does absolutely nothing. It only contains a Start event and an End Event and has a Start Form configured. Now that you can write to datastore and kick off other processes and other things from SAIL, that's a growing design approach. There are some in Appian circles moving toward process model-less applications.