TAP/TeamConnect Integration

Tech Specs 

TAP now has the ability to integrate workflows into the follwing TeamConnect versions:

• TeamConnect 4.2 through TeamConnect 7.X
•  TeamConnect Essentials
• See the TAP 3rd party matrix for a full, detailed list of 3rd party products and the features that TAP supports.

 

Troubleshooting

See this page for Tips, Tricks, and Troubleshooting help related to the TAP TeamConnect Integration. 

 

Introduction and Installation

Establishing Connections

TAP Form Elements

TC_TAP Workflow Actions

Launching the Workflow

Setting Up a TeamConnect Key

Note: Users must have a TeamConnect login/password created. It is recommended that it is not linked to a individual user's account, instead a TeamConnect service account with corresponding permissions.

1. Log into TAP.
2. Go to the Administration tab.
3. Locate TeamConnect Keys link on the list located on the left side of the screen and click on it:
   
   Note: You cannot delete TeamConnect keys once added, you can only edit them.
    
4. Select the New TeamConnect key button on the right:
   
    
5. Add the required information in all the fields. Click Save when finished. 
   Note: The label should be called what the instance being connected to is for easier identification

     Note: The TeamConnect URL must be "https" and should not include the "login". 

Creating a Workflow with the TeamConnect Integration

1. Click Designer under the Business Automation tab (located in the top global menu).
   
    
2. Select the Create button.
   
    
3. In the Form tab, you can select the TeamConnect Records or TeamConnect Categories option on the left column:
   
    
   • From there, you can select "TeamConnect Setup" on the right side and a pop up will show to select the TeamConnect Key and set various field information:
     
      
   • Configure the respective TeamConnect record options you want to appear in the Form/Workflow in this pop-up:
     
      
4. From the Workflow Tab, users will need to have at least 2 stages (more stages can be used, but at least 2 stages are required): 
   
    
5. Click on the Relationship for the stages and then click on the TeamConnect support button on the top menu. 
   
   Using the example in step 4, you would click on the box that says Relationship 1, then click the TeamConnect Support button on the top menu. 
   
    
6. Click Add when this TeamConnect Support pop-up appears.
   
    
7. A new window will appear. Select the following options for the 3 dropdown menus at the top of the screen:
   
   Dropdown 1: TeamConnect key must be selected. Dropdown 2: select an Object type. Dropdown 3: select a Primary Category (if there is one).
   
   Note: Depending on the type of Object type selected, further form fields may appear:
   
   Required TeamConnect Objects will have a red bar next to them.
   
   

Any documents you wish to send to TeamConnect from TAP must be configured in the option tab of the TeamConnect Support pop-up.

Overwrite Information:

If you wish to overwrite previous information sent to TeamConnect in one workflow, select the the "Replace Previously Selected Categories" option under the Categories update drop down. 

1. You can then add various other Options and Trigger Conditions if desired using the other tabs. Once done, click the Save button on the bottom.
2. The TAP form fields will map to TeamConnect based on your form selections listed above. Always remember to save your workflow.

Please see the screenshot below.

 

 

Using the TeamConnect Categories Field

The TeamConnect Categories field can be used in order to set record categories based on a user's selection in a TAP Form.  In order to do this, you must first add and configure a TeamConnect Categories Field in your TAP Form.  The TeamConnect Categories field is located directly below the TeamConnect Record Search field on the Form Builder sidebar:

Simply drag and drop the TeamConnect Categories field to the section of your form that you would like to add it to.  Once added, you will need to configure the field.  This can be done by clicking the TeamConnect Setup button located under Additional Settings in the Field Properties sidebar.  The following popup will then display:

In the First dropdown, select the TeamConnect key that you would like to integrate with.  In the Second dropdown, select the TeamConnect Object Type for the matter that you will be creating. The Third dropdown has 5 possible selections:

1. Multi Select - Allows the user to select multiple categories/sub categories to be assigned to the matter. Any combination of category/sub category can be selected.
2. Multi Select single child value - Allows user to select both a category and sub category, but not multiple of either. NOTE: If either multi select options are selected, the category will display as two dropdowns, one where the user can select multiple categories to assign to the object, and another where the user can only select a single category to be assigned as the Primary Category
3. Single Select - Allows user to select a single category or sub category
4. Essentials Parent - More Info TBA
5. Essentials Child - More Info TBA

The Fourth dropdown is used to decide which category and sub category options you would like to display.  There are two options to choose from:

1. All Categories - Displays all category and sub categories for the selected Object Type.
2. Predefined Categories - Allows you to select which Category and Sub Categories you would like to make selectableainin

Once the TeamConnect Categories field has been configured, you can use it to set the category of the matter you are creating through TAP.  To do this, simply select the Categories field that you created in the Primary Category dropdown when configuring TeamConnect Support in the workflow section.  When the workflow runs and creates a TeamConnect Matter, the category should be set to the value(s) chosen in the categories field. 

Send Files from TAP to TeamConnect

To transfer files from TAP to TeamConnect, follow the steps outlined below:

1. Begin by creating or loading a workflow.
2. Navigate to the "Workflow" tab, then click on TeamConnect Support, followed by Add.
3. Under the "Attributes" tab, select the relevant TeamConnect Key associated with the TeamConnect environment.
4. Choose the Object type and Primary Category accordingly.
5. Fill in all required information as prompted.
6. Navigate to the "Options" tab and assign a name for the Label.
7. Utilize the "Add new Attachment" option to include an attachment or file.  

8. From the "Please select attachment" dropdown, opt for "File upload".
9. Next, choose "Document" from the "Please Select Category" dropdown and proceed to select a description.
10. Moving on to the workflow, access the Properties and then select a stage, followed by Form Access. Ensure that the File Upload option is set to "Show".

11. Save the workflow once all necessary modifications have been made. 
12. Input text into the Text box and select a file for upload, then click the Submit button.
13. To verify the upload, navigate to TeamConnect, then the Documents tab and select Recently Uploaded. Here, the file uploaded in TAP will be visible and accessible for download.

14. Hovering the mouse over the document name will display the file path. 

Pre-Populate TAP Forms with TeamConnect Matter Fields

Form designers can configure forms to enable users to search for Matter Name, Matter ID and see matter information pre-populated in the search. Pre-population works for text fields and a drop-down that uses "Use TeamConnect Table As Option".

Admin or workflow designer: create a TAP workflow with TeamConnect Pre-population. When admin clicks the pre-population options, the admin has the ability to pre-populate all of the fields that are created or updated within the TC Support modal.

End user: When end user searches for a matter name or matter ID in a TAP workflow, the information related to the matter pre-populates within the TAP form. As a user, I want to search for a matter name or matter ID, and see matter information pre-populated after this search, so that I can make further edits or add information while referencing previously submitted matter details. 

TeamConnect Pre-Population Setup

The instructions below detail how to set up TeamConnect Pre-population in a TAP form. The first few steps cover how to set up the correct form fields, then the next section covers how to configure each form field accordingly for your TeamConnect needs, and the last section covers the workflow configuration.

Begin by creating a new form.

Creating Involved Parties on Records in TeamConnect via TAP

Prerequisite: To add an involved party in TeamConnect via TAP, the TeamConnect design must have a corresponding custom field of Involved Party type.

1. Add “TeamConnect Records Search” form field to TAP form
2. In “TeamConnect setup” for that form field, map to the proper key and map to the contact object
3. Set up desired form access for the “TeamConnect Records Search” form field
4. On the “Workflow” tab add “TeamConnect” support. The TeamConnect destination field in this example is “Agency1”. The name of the field in TAP is “agency 1 test”.

 

Prerequisites

Before you begin, review the following requirements to avoid errors during workflow execution:

• TeamConnect version 7.1 or above. 
• The workflow must include TeamConnect Support.
• Parent and child objects must already exist in TeamConnect.
• When configuring TeamConnect Support in a workflow, parent–child selection follows the predefined TeamConnect object hierarchy. If a parent object is selected first in the TeamConnect setup, only its valid child objects are available for selection in the TeamConnect Support stage. Conversely, if a child object is selected, the corresponding parent object is automatically displayed and available in the parent field dropdown.
• This ensures that parent–child relationships always respect the configured hierarchy (for example, a Matter Child can only link to a Matter parent; see the image below). If the Parent Project field is marked as required in the TeamConnect Support configuration, users must select a valid parent record during form submission.
• System objects are not supported.

 

Map a Parent Record Using TeamConnect Support Pushes

Follow the steps to map a parent record created or updated within a workflow.

Step 1: Open the Workflow Configuration

1. Open the workflow in edit mode.
2. Navigate to the stage or relationship where the child record is created or updated.
3. Open the TeamConnect Support configuration.

 

Step 2: Configure Record Creation or Update

1. Select whether the action will:

• Create a new TeamConnect record, or
• Update an existing TeamConnect record.

2. Select the TeamConnect Key. 
3. Select the child custom object.
4. Select a category.

When creating a new record: 

For updating an existing record

 

 

Step 3: Map the Parent Record Field

1. Locate the parent custom object field named “Parent Project” in the mapping section.
2. In the mapping dropdown, select one of the following: 

• A TeamConnect Support push , or
• A TeamConnect Record Search field .

You can create both the parent and child records from a single form submission by configuring separate TeamConnect Support pushes within the same stage or relationship.

3. If the parent record is created in the same form submission:

• The parent Support push must execute before the child Support push.
• Execution follows a top-to-bottom sequence, and incorrect ordering may require deleting and recreating the configuration.

Mapping automatically filters available options so that only valid parent object types are displayed, based on the child object’s hierarchy.

​​​​

Step 4: Map Additional Custom Object Fields (Optional)

• Admins can map the TeamConnect custom object field, not just parent fields.
• Supported field values include:
  • TeamConnect Support push outputs
  • TeamConnect Record Search selections

All supported TeamConnect field types can be mapped, provided the custom object field is configured with a specific project type (for example, Matter). Custom fields configured with the project type ALL are not currently supported.

Step 5: Save and Validate the Configuration

1. Save the TeamConnect Support configuration.
2. Validate that:

• Mandatory parent fields are mapped.
• The correct parent source (push or record search) is selected.
• The execution order is correct when parent and child are created together. 

Map a Parent Record Using TeamConnect Record Search

Use this approach when end users must select an existing parent record during form submission.

Step 1: Add a TeamConnect Record Search Field

1. Add a TeamConnect Record Search field to the form.
2. Select the TeamConnect key.
3. Select the object type and select the primary category.
4. Configure it to search the appropriate parent object.

Step 2: Map the Record Search to the Parent Field

1. In TeamConnect Support, locate the parent custom object field.
2. Map it to the TeamConnect Record Search field.
3. Save the configuration.

Behavior When Updating Existing Records

• If a child record already has a parent:
  • The existing parent relationship is retained unless explicitly overridden.
• If no parent value is mapped during an update:
  • The current parent record remains linked.
• Parent mapping works consistently for:
  • New record creation
  • Existing record updates

 

Error Handling and Validation

When parent mapping fails, the system displays clear error messages, such as:

• Record is not a valid parent
• Parent Project is required
• Parent record failed to map

When the mandatory fields are not entered during form submission, the drop-down fields appear as below 

When the configuration fails, the following screen is displayed.

Audit Trail and UI Consistency

Audit logging remains unchanged and continues to capture:

• • Submitted form values
  • Mapped record values
  • Record search selections
• The mapping dropdown UI is consistent with the TeamConnect Support module.

 

Example Use Cases

1. Create Parent and Child Together

A workflow creates a parent custom object record in one stage and a child record in the same or a later stage. The child record is automatically linked using the Parent Project field mapped to the parent Support push.

Example: Creating a Matter and its associated Task or Sub-Matter in a single request.

2. Link Child to Existing Parent

An end user selects an existing parent record using a TeamConnect Record Search, submits the form, and a new child record is created and linked to that parent.

Example: Adding a new Contract Amendment to an existing Matter.

3. Update Parent Relationship

An admin configures a workflow that updates an existing child record and reassigns it to a different parent by mapping a new Record Search value.

Example: Reassigning an Expense, or Sub-Project from one Matter to another due to a case reorganization.

4. Add Multiple Child Records

A workflow allows repeated creation of child records linked to the same parent by referencing the original parent Support push, enabling one-to-many relationships without predefined limits. This is achieved by configuring TeamConnect Support at the stage relationship level, where a form button is assigned as the trigger for creating additional child records. After each record is created, the form fields must be refilled to create the next record. So there’s no need to restart the workflow each time.

Example: Adding multiple Vendors, Outside Counsel, or Related Agreements to a single Matter without restarting the workflow.

Overview

Dependent (cascading) dropdown lists allow admins to configure form fields where the available values in a dropdown are dynamically filtered based on a user’s selection in another dropdown.

The dropdown values are sourced in real time from TeamConnect lookup tables (including the ones with multi-level lists), and the dynamic filtering of dropdowns follows the hierarchy in the TeamConnect lookup table.

Dependent dropdowns support:

• Multi-level hierarchies
• Skipping intermediate levels
• Show one level per dropdown from a multi-level TeamConnect list
• Show all levels at once in a single dropdown
• Mapping selected values back to TeamConnect records using TeamConnect Support

Prerequisites

Before you begin, review the following requirements to avoid errors during workflow execution:

• TeamConnect version 7.1 or above is required.
• The workflow must include TeamConnect Support.
• Parent and child objects must already exist in TeamConnect.
• Dropdown fields must use TeamConnect List fields as their data source.
• Parent–child drop-down behavior must follow the hierarchy defined in the TeamConnect lookup table.
• System lookup tables are not supported. 
• A custom lookup table mapped to a custom field on a system object (for example, Contact) will function correctly.

Follow these steps to configure a dependent (cascading) dropdown using TeamConnect list fields.

Step 1: Add or Edit a Dropdown Field

1. Open the TAP form in edit mode.
2. Add a new Dropdown field, or select an existing dropdown field to edit.
3. Navigate to the Dropdown field → Options.

Step 2: Select TeamConnect List as the Data Source

1. In Data Source, select Use TeamConnect List Field.

2. Configure the TeamConnect list using the following selections:

• TC Key
• Object
• Category
• Select TC List

 

Step 3: Choose the Level to Display

1. Under Level to Display, select the hierarchy level of the TeamConnect list to show in the dropdown or choose to display all levels at once:

• Level 0 – Root level (selected by default)
• Level 1+ – Nested levels
• All Levels – Displays values from all hierarchy levels in a single dropdown

2. Review the preview of sample list values shown for each selection.
3. Select the level that best fits the form requirement.

This option is always available and does not depend on enabling Dependent Lists.

 

Step 4: Enable Dependent Lists

1. Select the Dependent Lists checkbox.

   • This option appears only when a TeamConnect list field is used as the data source.

2. Once enabled, the Parent Dropdown field becomes available.

 

Step 5: Select the Parent Dropdown

1. In the Parent Dropdown, select the existing dropdown field that will act as the parent.
2. Ensure the selected parent dropdown:

• Is placed earlier in the form.
• Uses a compatible TeamConnect list.

3. It is supported to use different TeamConnect lists for the parent and child dropdowns, as long as their Tree Positions match.

(Tree Positions are four-character codes that uniquely identify values within TeamConnect lookup tables. See Glossary for details.)

Step 6: Validate Parent–Child Matching

1. Verify that the parent and child TeamConnect lists share matching Tree Position values (four-character codes).
2. Ensure the hierarchy levels selected for display align correctly.
3. If no matching values exist, the system displays the following error:
   “No matching values with parent. Check that the parent dropdown’s source list is configured correctly.”

Step 7: Configure Additional Dependent Levels (Optional)

1. Repeat Steps 1–6 to add more dropdowns in the sequence.
2. Each additional dropdown should:
   • Use a deeper hierarchy level.
   • Reference the previous dropdown as its parent.

Step 8: Save and Test the Configuration

1. Save the form configuration.
2. Preview the form behavior:
   • Child dropdowns remain blank until a parent value is selected.
   • Changing a parent value updates the child options.
   • Clearing a parent value resets the child dropdown.

The dependent dropdowns are now configured. End users will see dynamically filtered dropdown options based on their selections, with values dynamically pulled from TeamConnect lookup tables at the time the form is loaded, ensuring accurate and guided data entry.

Mapping Dependent List Values to TeamConnect Records

Values selected from dependent dropdowns can be mapped to TeamConnect records using TeamConnect Support.

• Selected values are passed from the form to TeamConnect custom object fields.
• When a workflow is submitted:
  • A new TeamConnect record can be created, or
  • An existing record can be updated
• All mapped values are persisted exactly as selected by the user.

 

Display Entire Hierarchy in a Single Dropdown (Optional)

Admins can configure a dropdown to display the entire TeamConnect list hierarchy in a single dropdown.

Important limitation:

• When the full hierarchy is displayed in one dropdown, dependent (cascading) dropdowns cannot be configured.
• Admins must choose either:
  • Cascading dependent dropdowns, where each dropdown displays only one hierarchy level at a time, or
  • A single dropdown with the full hierarchy

Example Use Cases (End User Perspective)

1. Geographic Selection
   • Country → State → City
   • Users see only cities relevant to the selected state, even if intermediate levels are skipped.
      
2. Product Selection
   • Manufacturer → Model → Year
   • Selecting a manufacturer dynamically filters available models and years.

3. Team Selection
   • Division → Department → Team
   • Users can only select teams relevant to their chosen department.
      
4. Workflow Integration
   • Selected dropdown values are automatically mapped and stored in TeamConnect records upon form submission.

Limitations and Known Issues (Dependent Dropdowns)