Free cookie consent management tool by TermsFeed

User Input Task

On This Page

Overview

The User Input Task is an activity that assigns a task to be completed (using a form) to a user or a group.

Properties

  • Category: Human Tasks
  • Icon:

  • Assignment Options: Attended

  • Compatible with autoscale: No

Configure the activity

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

Tip:  To jumpstart activity configuration, search for your interface object in the Smart Service search bar, then drag and drop the interface object to the process model canvas. The User Input Task node is automatically created in the process model and configured to reference that interface object. Open the process node's properties to further configure its behavior.

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.

Capture task submission location (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.

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