Script Task Vs User Input Task

RE: Script Task Vs User Input Task

Mike Schmitt — Tue, 23 Aug 2022 18:15:52 GMT

[quote userid="86644" url="~/discussions/f/best-practices/21237/script-task-vs-user-input-task/100006#100006"]What is the difference in node inputs and outputs ? I am unable to figure out[/quote]

As an aside, writing expression code in a node input is STILL a painful process for anything other than simple, single-line expressions, because for SOME reason they still haven't updated some of the legacy expressionable fields to not collapse everything to a single row upon saving. GRUMBLE.

Therefore, even to my direct disadvantage at times, I avoid using input fields at all costs (though of course some are unavoidable). I eagerly await them fixing this unreasonable legacy constraint in the various places it still exists.

RE: Script Task Vs User Input Task

Stewart Burchell — Tue, 23 Aug 2022 16:38:30 GMT

Yup, it's a little confusing when you first start. So, you use the node Inputs to define a variable that is local to the node i.e. an Activity Class variable. You can set this value to the value of a process variable (which is in effect passing by value - i.e. a copy of the value in the process variable). Or you can set the value using an expression (e.g. you could call a rule and have that rule do anything you want). Now that you have a value in your Activity Class variable you could just pass it out again to the same (or a different ) process variable, using the 'Save into' setting. In effect, you can get data into and out of your script task without ever leaving the Inputs tab.

You also have the option of conducting what you might think of as "post processing" on the value of your activity class variable, which you can do in the Outputs tab. You can reference the Activity Class variables in the Outputs tab and do whatever you want before writing the value back to a process variable.

Or you do not have to use any Inputs if they're not required for the step you're configuring. You could just run a rule in the Outputs tab and write the output to a process variable.

RE: Script Task Vs User Input Task

deepakg271869 — Tue, 23 Aug 2022 16:36:34 GMT

You can create node input as well as node output.

RE: Script Task Vs User Input Task

MANASA V — Tue, 23 Aug 2022 16:19:34 GMT

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 ?

RE: Script Task Vs User Input Task

MANASA V — Tue, 23 Aug 2022 16:17:35 GMT

As per the documentation generally only node outputs are configured for script task and not node input ?

RE: Script Task Vs User Input Task

MANASA V — Tue, 23 Aug 2022 16:16:48 GMT

What is the difference in node inputs and outputs ? I am unable to figure out

RE: Script Task Vs User Input Task

Stewart Burchell — Tue, 23 Aug 2022 15:27:53 GMT

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:

RE: Script Task Vs User Input Task

MANASA V — Tue, 23 Aug 2022 15:22:44 GMT

If i configure node inputs of a script task is it a mistake ?

RE: Script Task Vs User Input Task

MANASA V — Tue, 23 Aug 2022 15:22:14 GMT

Sir why do we configure only node outputs on script task ?

RE: Script Task Vs User Input Task

Stewart Burchell — Tue, 22 Jun 2021 07:49:08 GMT

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)

RE: Script Task Vs User Input Task

Peter Lewis — Mon, 21 Jun 2021 16:33:24 GMT

Agreed, I'd also highly recommend the Academy Online training courses. These courses provide answers to all the questions you have asked: community.appian.com/.../courses

RE: Script Task Vs User Input Task

gayathris876948 — Mon, 21 Jun 2021 10:36:04 GMT

1. User input task node allows a designer to associate an interface to an user attended activity.
For detailed information about how to design interfaces, including how to enable user interactions, how to save and validate user inputs, and how to submit user inputs to process, see the Interface Object page.

2. The Script Task is used to perform an automated activity (which does not require a user to complete a form). It is typically used to execute an expression or rule and capture it in the process variable and use it further in a process.

RE: Script Task Vs User Input Task

Stefan Helzle — Sun, 20 Jun 2021 18:39:37 GMT

Did you attend the Appian academy? I think this is covered.

https://docs.appian.com/suite/help/21.2/Configuring_the_Script_Task.html

docs.appian.com/.../Configuring_the_User_Input_Task.html