Which of the following tasks is NOT applicable to script tasks?

Script tasks in Appian are particularly designed for executing predefined logic or operations, often involving data manipulation, calculations, or decision evaluations. When considering this context, triggering external processes is not something that script tasks are specifically designed to handle.

Script tasks are typically coded to perform operations within the Appian environment, such as manipulating data or evaluating decisions based on given criteria. This means they can effectively execute functions that alter data structures or determine paths within a process based on conditional statements. For example, if the task involves calculating a total or reducing a dataset, this would fall perfectly within the scope of a script task.

Alternatively, assigning forms to users is generally done through user tasks, which are designed to interact with users and facilitate data input directly into the workflow. This differs fundamentally from the purpose of script tasks, which do not involve user interaction. Additionally, the act of triggering external processes often requires configurations or integrations defined outside of a script task, such as through service calls or integrations, rather than the in-process logic used in script tasks.

Thus, the option regarding triggering external processes is accurate in the context of what script tasks are designed to do. They focus on internal processing rather than managing interaction with external systems.