User Input Task

The User Input Task activity is used to assign a task to a user and/or group. Interfaces are associated within a User Input Task to capture data from a form into a process.

User Input Task node

The User Input Task node has the following properties:

• Category: Human Tasks.
• Icon:

• Assignment options: Attended.

• Compatible with autoscale: Yes

Configure the User Input Task node

To configure the User Input Task node, double-click the node on the process model canvas. The Configure User Input Task dialog displays.

In the Configure User Input Task dialog, you can configure the following properties:

Tab	Action
General	Provide the node name and description, and set the activity as a Quick Task if appropriate.
Data	Create process variables for storing your node input data.
Forms	Select an interface to use as the input form. You can also do the following: Allow in-progress save: If you are saving user inputs into Activity Class Parameters, leave the Allow users to save a draft of in-progress tasks checkbox selected, so users can save a draft of the task before submitting the form. Capture user location: If users will be submitting tasks in an Appian Mobile application, select Capture location on submission (only supported in Appian Mobile). Learn more about the information captured when the user submits the form. Form-based approvals: You can configure the task form with approve or deny buttons that store a value when the form is submitted. To do this, use the Button component to store a value when the user submits your form. For example, true for Approve or false for Deny.
Scheduling	Configure the task to start and repeat on a schedule as appropriate.
Assignment	Assign the task to a user or group.
Escalations	Configure an escalation for the task. If a user is editing the task form when the escalation occurs, a default error message displays to the user, indicating that the task is no longer assigned to them. You cannot customize this message.
Exceptions	Create alternative workflows from the task based on configured conditions.
Other	Configure multiple instances, set deadlines for node completion, and manage node execution options as appropriate.

Using the User Input Task node

The following considerations apply when using the User Input Task node.

Use the User Input Task node in an autoscaled process

A User Input Task in an autoscaled process can be used to display an Appian interface in a site, Tempo, or Appian Mobile. As with standard processes, users can accept tasks assigned to a group or multiple users and submit the task using developer-defined buttons. Submitting the task will continue an activity chain if one is configured in the process.

Tasks in autoscaled processes differ from those in standard processes:

• Locales: Tasks can be only configured for the environment's primary locale. You can use translation sets to create localized content for your form interface and reference that form in your user input task.
• Task actions: Autoscale tasks cannot be reassigned or rejected.
• Task types: Autoscale does not support Quick Tasks.
• Appian Mobile: Users can view and submit task forms in Appian Mobile. Autoscale tasks do not support a native mobile task list, offline tasks, or location capture.
• Tempo: Autoscale tasks do not appear in the Tempo Tasks list, but users can open them using Tempo task URLs.
• Monitoring: Autoscale process monitoring does not have a View Form action for a User Input Task.

Capture task submission location in Appian Mobile

In the Forms tab of the User Input Task node, you can enable the Capture location on submission option. This option is only supported in Appian Mobile and only with standard processes.

If this option is enabled, Submission Location result data is available in the Outputs section of the Data tab.

Submission Location can contain the following fields:

Field	Description
location	The geographical location from where the task is submitted. This is only available when the task is submitted from Appian Mobile application. This field contains the following values: latitude: The latitude, measured in degrees. longitude: The longitude, measured in degrees. altitude: The altitude, measured in meters. horizontalAccuracy: The radius of uncertainty for the location, expressed in meters. verticalAccuracy: The uncertainty in the altitude value of the location, expressed in meters.
isAvailable	Indicates whether location is captured for the submitted task. Returns true if location is captured, false otherwise.
errorStatus	Indicates the reason for missing location. This field is only populated if isAvailable is false. It can have one of the following values: NOT_AUTHORIZED: Indicates that access to location services was denied by the user from the mobile application. NOT_AVAILABLE: Indicates that the location could not be obtained. NOT_SUPPORTED: Indicates that the task was submitted from web or from an older version of the mobile application. DISABLED_BY_ADMINISTRATOR: Indicates that the system administrator has disabled the 'Enable Location Capture' option from the Appian Administrator Console.

To reference the submission location elsewhere in the process model, the Submission Location result must be mapped to a process variable:

1. In the Data tab, select the Outputs section.
2. In the Results list, select the Submission Location output.
3. In the Result Properties section, save the output in a process variable of type LocationResult. You can also create a new process variable to store the submission location by clicking on the New process variable button.

Feedback