Background

 Exporting data into Aspen Workflow's meta-data structure can be a tricky affair.  Thus, we break it down into the following broad steps:
  1. Mapping Data
  2. Inserting Clients
  3. Inserting Vendors
  4. Inserting Parent Lookup Tables
  5. Inserting Matters
  6. Inserting Processes
  7. Updating Matters
  8. Updating Processes
  9. Updating Tasks
  10. Updating Fields
  11. Inserting Child Lookup Tables
  12. Updating Child Lookup Tables

 
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 Export Column mapping tool (see Admin - Export) to "connect the dots".  This is a simple but tedious task, and crucial to the success of any data conversion.  Essentially, an Export routine will be created for EACH database (or even each table) in the original system.  For every column that should be exported, the precise column name must be mapped to an Aspen Workflow Export column.  Whether it maps to a Matter, Process, Task or Field level data element is irrelevent at this stage of conversion.

 
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