Background

Aspen Workflow is designed to grow with your business.  We allow you to design or modify parts of your system to mirror how you do business; this is referred to as business logic.  There are five different ways to implement business logic; each is discussed below.  It is important that you understand HOW business logic works, and how you can use it to make Aspen Workflow grow and change to fit your business

Business Logic vs. Programming Logic

Business logic can be cusomtized from office to office.  For example, one office may have a "Michigan Foreclosure" procedure consisting of 25 tasks designed for a non-judicial foreclosure.  Another office may have a "Chapter 13 Bankruptcy" procedure consisting of 22 tasks designed for bankruptcy.  Each office can choose to define its own procedures, tasks and fields.  Aspen Workflow does not need to be re-programmed for each of these offices; the Administration module is used by the office to define their own procedures, tasks and fields.

Programming logic is imbedded in Aspen Workflow, and is unchanging from installation to installation.  For example, a task is added to a file via programming logic; the programming logic does not care what the name of the task is or how is it used by the office.

Creating Business Logic

Business logic is creating in the following manner:

  1. Procedures, Tasks and Fields to fit your business
  2. Reporting (procedure and task-based reports)
  3. Actions (procedure-based business logic)
  4. Task triggers (task-based business logic)
  5. Javascript (field-based business logic)
  6. Document Logic

Examples

For the examples used in this tutorial, we will assume that our sample office is called "Aspen Law Offices", and that they specialize in foreclosures, bankruptcy and title work.  Aspen Law Offices is based in Boston, MA, and does work throughout New England.

Aspen Instant Messaging Welcome | Users | Business | Managers | Documents | Lookup | Administrators