The Bulk Updater Automation uses different Project Type templates in Filevine. This includes case projects, setup/configuration projects, and the projects to trigger/use the automation. Below are the Project Types used by the automation explained.
Project Type: Case Types
A Case Type is a Project Type that defines the structure for specific cases in the Filevine user environment (e.g., Mass Tort, Personal Injury, Immigration). These Project Types are the Bulk Updater automation target. The following table exemplifies Case Types visually:
Project Type: Config
A Config is a Project Type dedicated to automation setup. It contains the Bulk Update — Config section. Each target Project Type must have a unique Config. This template is also used to create a Config Project — Admin for each Admin Project Type. The Config Project — Admin contains the Bulk Update — Config section, where the Bulk Updater Automation settings for each target Project Type are defined. The following table exemplifies Config Project Types visually:
Project Type: Admin
An Admin is a Project Type that defines the structure of Bulk Import projects. Field codes required for automation setup are obtained In this Project Type. The following table exemplifies Admin Project Types visually:
Import Projects
The Bulk Update Import section is where users execute the Bulk Updater Automation. This section’s structure is defined by Collection Items, which import the information to Import Projects.
Therefore, Import Projects serve as a bridge between Collection Items and the Bulk Update Import section. There are two different configuration options for this import projects:
Option 1: Import Project Per Target Template
The first configuration option has the following characteristics:
- Each target Project Type (Mass Tort, Personal Injury, etc.) has a unique Import Project.
- A single trigger button handles imports for all target Project Types.
- The Collection Item for each Project Type must point to its corresponding Import Project (unique Project IDs for each setup). Therefore, the automation is triggered by the Import Csv button button.
For example: If the target Project Types to automate are Mass Tort, Personal Injury, and Immigration, then three import projects for each target Project Type must exist. These projects are:
- Import Project — Mass Tort,
- Import Project — Personal Injury, and
- Import Project — Immigration.
This setup only requires one Import Csv button button; each Collection Item must point to the same trigger button.
Option 2: Different Button Per Target Template
The second configuration option has the following characteristics:
- A single Import Project must have individual trigger buttons for each target Project Type.
- The Collection Item for each target Project Type must point to a single Import Project. This Import Project contains a unique Import Csv button button for each Project Type.
For example: If the target Project Types to automate are Mass Tort, Personal Injury, and Immigration, there should be one Bulk Import Project with 3 trigger buttons (one for each target Project Type):
- CSV import button — Mass Tort,
- CSV import button — Immigration, and
- CSV import button — Personal Injury,
In this case, the automation setup for each target Project Type must point to its corresponding button.