what is the difference between process start form in process model properties and Form in input task configuration

Question

I'm still in the practice stage of Appian tool and running through the Instructions of Vehicle Fleet management system given by Appian. Though while doing this I have faced Process start form and Input Form. What are the difference between these two and If possible please provide an example scenario to use either of the forms.

Robert Shankin · Answer

In order to configure a site page as an action , your process must use a start form. So that's one case where the decision gets made for you. 
 The neat thing about start forms is that a process is not actually started until the start form is submitted. This is especially convenient if your process is of the type that people sometimes start, but don't finish, (essentially, they walk away, or abandon the process) then a start form saves you the trouble of configuring automatic expiration into your process. 
 On the other hand, if the first interface in your process is configured after process start, then, you're process is started. Yes, that last statement sounded redundant. But, it's an important consideration. Processes that start should eventually end. Consider, for example, if you have a policy requirement that requires that you capture when someone starts your process, (whether they finish or not), then maybe a start form isn't the best choice, because you need to start that process to capture the initiator details. 
 Starting out, you might like to use script task nodes in process to map out some evaluations that need to occur with/before the load of your form. As you advance, and become more comfortable with SAIL, I expect you'll find you can do quite a bit in SAIL, enabling you to reduce the number of nodes in your process models

what is the difference between process start form in process model properties and Form in input task configuration

Top Replies