Background

A task is a collection of fields which appear together on the same screen.  Just as commonly grouped fields constitute a task, commonly groups tasks constitute a process.  Fields may be used by more than one task, and a task may appear in more than one procedure.

Summary

Basic information for a task includes the following:
  • Task: name of the task as it appears on screen and in documents.
  • Label:  
  • Description:
  • Instructions:  end-user instruction which appear at the top of the task screen.
  • Help URL:  the help page displayed when the user clicks on the Help icon from this task.
  • Custom URL:  redirection to a custom-built URL, rather than a standard Aspen task.  See Custom Task pages below for more information.
  • Repeatability:  how often this task may be added to a process.
  • Key Task:  makes this task appear on the Matter Summary screen.
  • Auto Complete:  the stop actual date will automatically be filled in on the projected stop date.
  • Add Wizard:  (not currently implemented).
  • Default Team:  team assigned to this task by default whenever this task is added to a file.
  • Default Person:  person assigned to this task by default whenever this task is added to a file.

Accounting information for a task includes the following:

  • Client Type:   the drop-down list of clients provided for this task.  This is a list of all stored procedures beginning with 'lClient'.  See Categories for creating additional lookup stored procedures.
  • Price:  the default price assigned to this task when added to a file.
  • Bill Request:
  • Receivable Code:
  • Vendor Type:  the drop-down list of vendors provided for this task.  This is a list of all stored procedures beginning with 'lVendor'.  See Categories for creating additional lookup stored procedures.
  • Cost: the default cost assigned to this task when added to a matter process.
  • Check Request:
  • Payable Code:

Triggering Information includes:

  • Start Trigger: default start date is calculated by the field or task assigned in this trigger.
  • Stop Trigger:  default stop date is calculated by the field or task assigned in this trigger.

Business Logic events include:

  • On Load:
  • On Unload:
  • On Change:
  • On Save
  • On Cancel:

Fields

Each task can use an unlimited number of fields.  Fields may be used in one or more tasks.  If a field is added to a task after files exist in the system, this field must be added to the existing matters.  This can be done clicking on the Synchronize button at the top of the Task - Fields page..

Processes

A list of the processes that include this task.

Documents

A list of the documents that can be generated from this task.

Client Pricing

Client-tiered pricing for this task.

Vendor Pricing

Vendor-tiered costing for this task.

See Also