Background

 There are two types of data import to Aspen Workflow's meta-data structure:
  1. Subscription Imports from another Aspen Workflow database, primarily Aspen ipWorkflow; and
  2. Data imported from a non-Aspen Workflow database.

For information on updating Subscriptions for Aspen ipWorkflow, go to http://ipworkflow.com/help/adminIPsubscription.asp.  

For all other data import instructions, see below.

 

Mapping Data

Because Aspen Workflow is a meta-data structure, we cannot know in advance which Aspen task or field will represent a column from a table in another system.  The processes, tasks and fields for the Aspen Workflow installation must be created first.

Once created, a business expert familiar with the field names and meanings in both databases should use the Import Column mapping tool (see Admin - Import) to "connect the dots".  This is a simple but tedious task, and crucial to the success of any data conversion.  Essentially, an Import routine will be created for EACH database (or even each table) in the original system.  For every column that should be imported, the precise column name must be mapped to an Aspen Workflow Import column.  Whether it maps to a Matter, Process, Task or Field level data element is irrelevent at this stage of conversion.

When Mapping Data is complete, the following steps should be followed in order:

  1. Inserting Clients
  2. Inserting Vendors
  3. Inserting Parent Lookup Tables
  4. Inserting Matters
  5. Inserting Processes
  6. Updating Matters
  7. Updating Processes
  8. Updating Tasks
  9. Updating Fields
  10. Inserting Child Lookup Tables
  11. Updating Child Lookup Tables

Inserting Clients

Inserting Vendors

Inserting Parent Lookup Tables

Inserting Matters

Inserting Processes

Updating Matters

Updating Processes

Updating Tasks

Updating Fields

Inserting Lookup Tables

Updating Lookup Tables

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