The critical step in passing information from a form back to a process model is to configure inputs on the Data tab of a User Input Task. When you create a User Input Task, it includes a form for users to interact with. The data entered into this form can be mapped to process variables via the Data tab configuration. This ensures that the information collected in the form is available to the process for further use.

The most efficient method to access data for a pie chart in a child interface is to create a rule input on the child interface and pass the local variable data from the parent interface. This method avoids redundant data queries and takes advantage of Appian ' s pass-by-reference mechanism, which does not duplicate data in memory when passing it to the child interface.

Robotic Process Automation (RPA) is the Appian feature designed to automate repetitive manual tasks, especially in scenarios where interacting with systems without APIs is necessary. RPA bots can mimic human actions, such as navigating through system interfaces, extracting data, and entering information, effectively bridging the gap between digital processes and systems that lack API integrations. This capability is particularly useful for integrating legacy systems into modern workflows, streamlining operations that would otherwise require manual intervention.

When an error occurs on an unattended node in a running process instance:

The process is not paused, allowing other parallel paths to continue.

An alert is typically sent to appropriate recipients, such as administrators, to notify them of the issue.

These nodes are not counted in the num_problem_tasks process metric, which is used in process reports to track problematic tasks.

This behavior ensures that the rest of the process can continue as intended while alerting administrators to intervene and address the error.

References

Appian Documentation: Error Handling in Processes