difference between script task and user input task? And why we use? And when we use?
Discussion posts and replies are publicly visible
Conceptually ALL steps/nodes/smart services in a Process Model are "tasks". But it's only a "User Input Task" that is used to present a form/user interface to a User for, you've guessed it, "input" from that User! All other "tasks" have either very concrete functionality (e.g. "Write to Datastore") or the more abstract "Script Task" (which can invoke a wide range of functionality in the rule!, fn! or a! domains)
Sir why do we configure only node outputs on script task ?
If i configure node inputs of a script task is it a mistake ?
No, because you have the option to derive a value for your "input" in the 'Value' property and then write that value to a process variable in the 'Save into' property:
What is the difference in node inputs and outputs ? I am unable to figure out
As per the documentation generally only node outputs are configured for script task and not node input ?
Basically the node input name is a activity class parameter confined to a node and the node output will provide us to map dynamic expression onto process variables ?
You can create node input as well as node output.