Products

View Products Overview

Collect information to use in contracts and agreements.

Create contracts swiftly through templates, AI, or create and edit your own.

Route contracts seamlessly for editing, review, and approval.

Easily work with internal and external participants to edit and redline contracts in real-time

Capture secure, compliant, and legally binding signatures on any device.

Connect to the systems you use daily, or build into your application with our APIs.

Use a View File Task

A view file task can be used to route a document for review and approval. You can choose to upload a file, or can select a file that the user uploaded in a previous web form task with a “File Upload” field. You can optionally choose to allow a user to download the file from the viewer.

Before You Begin

Before you can create a view file task, you need to create a workflow template.

Create a View File Task

  1. In the workflow builder, click “Insert First Task” or click the + above or below an existing step.
  2. Choose “User Task”, then “View File”.
  3. In the right panel, you can modify the default task name, “View File”. It’s a good idea to make your task names descriptive and meaningful so that it’s easy to distinguish the current workflow step.
  4. From the assigned-to dropdown, select the task assignee. The workflow originator (the person who ran the workflow) will be available for selection, and in addition, there may be other participants available if they’ve been invited to the workflow or referenced as a property.
  5. Click the “Edit” button in the builder, or from the task actions dropdown, select “Edit”.
  6. Choose to upload a file, or select a file that was uploaded in a previous web form task with a file upload field (using the property associated with that file upload field).
  7. You can optionally do the following:
    • Allow a user to download the file from the viewer.
    • Add action buttons, which will allow the workflow to progress to the next step, and optionally provide multiple paths (branches) of completion of the workflow (for example, if a request is accepted it would take one path forward, and if rejected would take a different path).
  8. Once you’ve configured the task, click <.