Free cookie consent management tool by TermsFeed

User Input Task

On This Page

The User Input Task activity is used to assign a task to a user 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.

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 enable additional actions for the form.

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.

Additional user input actions

Beyond the standard node configuration, you can enable extra user actions on the task form, as described in the following sections.

Save a draft of a task

To add a Save Draft button to the task form, select the Allow users to save a draft of in-progress tasks checkbox on the Forms tab of the User Input Task node.

This checkbox is selected by default when you add a new User Input Task node. Keep it selected if you've configured the interface object to save user inputs into Activity Class Parameters, so users can save their progress before submitting the form.

Saving a draft is supported in both standard and autoscaled processes.

To save a draft, users must:

  1. Complete all required fields in the task form first.
  2. Remove any files or documents you have uploaded via the form but not yet submitted.
  3. Click Save Draft or press Ctrl+S (Windows and Linux) or Cmd+S (Mac).

    Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to closeA task form with the SAVE DRAFT button highlighted in the top-left corner, next to the REASSIGN link

    The following occurs:

    • If you have not removed files or documents uploaded via the form but not yet submitted, you are blocked from saving by the following dialog:

      Error dialog titled "An Error Has Occurred" with the message "Saving a form containing uploaded files is not supported. Please remove them and try again." and an OK button.

    • If the save is successful, a temporary Form saved successfully banner confirms the save. The user stays on the form, and the task's status and assignment do not change.

When the user saves a draft, Appian:

  • Stores the form's values in the activity class parameters, so the user can close their browser and return to the task later without losing their entries. When the user reopens the task, the saved values repopulate the form's rule inputs, and the form applies all validation, conditional logic, and dependent-field behavior to the restored values, just as if the user had entered them.
  • Keeps the saved draft even if the task is reassigned to a specific user or returned to the assignee pool, so the next owner can continue from the previous user's progress. Appian clears the saved draft if the task is canceled or the parent process completes.

Capture task submission location in Appian Mobile

If users will be submitting tasks in an Appian Mobile application, select Capture location on submission (only supported in Appian Mobile) in the Forms tab of the User Input Task node.

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 fields

The Submission Location result captured in Appian Mobile 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 the 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 Admin Console.

Map the submission location to a process variable

To reference the submission location elsewhere in the process model, map the Submission Location result 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.

Enable 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.

Capabilities in autoscaled processes

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 continues 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 can be reassigned when the assignee has reassignment privileges, but they cannot be rejected. Reassignment is not available on subsequent task forms in an active activity chain.
  • 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.

Feedback