Setup
In order to use the Litify integration, a system admin will need to complete a handful of setup steps both in Supio and also in Litify
Supio Setup
These steps are completed in Supio admin settings, access via the cog by clicking on your user name in the top right corner of Supio Portal.
In Settings > Apps, if your connector is not already configured, click to install the Salesforce (Litify) connector app
As part of this setup, you will be asked to use your Litify Salesforce login to provide authentication to Supio’s system
Define Case Name and Case Type mapping
Case Name: admins are able to choose which field on the Litify side they would like the Supio case to use when constructing the case name in Supio
This will be used to pre-populate the case name, but the name can be changed by a user at any time after the case is created or during the setup process
Case Type: admins are also able to define a field value mapping for case type to a field in Litify. This is useful as sometimes there is not a 1:1 match for Case Type in Supio and Litify. An example is MVA in Supio vs Automobile Collision in Litify. Admins should use a Salesforce picklist type field.
Determine Automatic File Sync Settings
At the bottom of the settings page for the Litify Connector there is a toggle for automatic file sync. Firms can determine whether they would like to enable the feature or not. Below are some guidelines to make the decision thats right for you
Automatic File Sync Enabled
All files in Docrio related to the synced case will attempt to be added to Supio
Firms should use this selection when they do not have specific folders they want added, and they want no user decision making
Automatic File Sync Disabled
You will still be able to use the frame to create the Supio case, but files will only be uploaded manually.
Better for firms who still want to control which files get into Supio, but this will require user intervention to update cases from the frame
Determine Data Pushback Settings
If the Litify integration package is installed, you will have options to enable data pushback
You can choose to enable pushback for
Overview & Insights
Timeline Events
You can choose to not use this feature and have both toggles off
Pushback is triggered whenever a case update is processed
Note that Mass Tort pushback data is not yet supported
Litify Setup
The following steps describe actions that need to be taken by a system admin inside of Litify directly.
Install the Supio Litify integration package into the Salesforce instance. Reach out to your customer success representative for access to the links
When prompted, install for All Users
Assign Supio Permission Sets
Supio Admin
Admin level access to Supio objects and Supio Admin App and iFrame.
Supio End User
En user level access to Supio object and iframe.
Launch the Supio Admin app
The user will be prompted to configure Trusted URLs via a button, click this to complete the step
Note: only users with Supio Admin permission set assigned will have access to this app from the launcher
Optional: Firms Not Using Okta for SSO
If you are not using Okta as your SSO manager, but some other service, you will need to change a custom setting so that it points to the proper URL. If you are unsure what service you are using, contact your IT department
Update the Supio_IdP_URL Trusted URL setting in Setup to match the url path required by your identify provider
Navigate to Setup > Trusted URLS > Supio_IdP_URL and replace https://supio.okta.com to the desired URL path
Add Supio component to the Matter page layout
Edit the page layout on a matter, and add a tab with the desired name to host the Supio iFrame experience
Once the tab is created, drag the Supio component into the tab and save the layout changes
Optional: Add Supio Case & Timeline Event Related Lists to Matter
If you are making use of the data pushback feature, you can choose to also add the 2 objects made by Supio as a related list to the matter. This gives you the advantage of being able to see the record page for the data from Supio when viewing a matter
Log In to Supio via the Matter tab window
Users will use their existing Supio logins to log into the Supio window from on the matter
When a user is already logged in on their browser, this will be detected by the Supio window on the matter to make the login process easier
Note: If any Supio users are sharing computers and logging into Supio from within Salesforce, we recommend either clearing their browser cookies when they are done or go directly to https://portal.supio.com and logging out. There currently is not a logout button within the Supio component in the Salesforce managed package and following this recommendation will help prevent a user from performing actions on behalf of another user.
Some key things to know about how v1 of the integration works:
Only cases created through the integration iframe on a matter are eligible for automatic file sync
Automatic file sync runs 2x a day and will ingest all eligible files into Supio
If you do not want all files to be pulled into Supio, it is possible to turn automatic file sync off, and still be able to use the iframe on a matter to create and access cases
Viewing Supio Case on a Matter
V1 of the integration has all case creation and initial file sync to performed through the Supio iFrame on a matter. End users will the proper permissions and Supio logins, will log into the frame, and create the case manually as well as select the folders/files for the initial file sync. Once the matter is synced to a Supio case, files will automatically sync into Supio.
When viewing the Supio window on a matter, depending on whether the matter is already a case in Supio or not, users will either see a Get Started screen, or the overview tab of the Supio case.
Case does not yet exist in Supio:
Case already exists in Supio:
Creating a New Case & Initial File Upload
If the case does not exist yet, and the user wishes to upload matter and files, they can do so by clicking Create Case and moving through the case creation flow. This flow is very similar to the one in Supio currently, and supports choosing deliverables, folders from Docrio, and filling out demand intake information.
Since file upload happens completely in the background, it is possible to begin upload and leave the matter page while the rest of the files upload. Once files are uploaded, your case will begin processing and you will be updated when the timeline or demand has been published.
Automatic File Sync
Once a matter is synced via the integration, and automatic file sync is enabled for the case, any new files which are uploaded to Docrio will automatically be added to Supio for processing. These files are treated as an update and will enter the queue for updating chronologies or case economics.
File types supported via automatic file sync: Pdf, doc, docx, jpeg, jpg, png, tiff
Note: only cases synced through the matter frame are eligible for automatic file sync
We’ve added some tools into Supio to help manage and gain visibility into the integration.
Connector Settings for Automatic File Sync
A new feature has been added to the file list, which will only be exposed to cases which have been created through the integration. When viewing a case which has automatic file sync enabled, in the File List, there is an additional button for File Sync.
Opening this will reveal a set of controls for the file sync feature, including a toggle to turn it on or off for the specific case, as well a button to force the sync from Litify. This can be used if you urgently need to get some files in the system.
Should any files fail to upload, a button will display here which can be used to get to a list of files and their file paths to either retry or to upload manually.
Data Push Back
The new data pushback feature will give firms the option of creating records in their Litify org for 2 types of data
Case Overview & Insights
Timeline Events
Both of these are completely optional, you can determine which, both, or neither of these data types you would like added to your Litify org.
Note: only new cases created through the integration after the release of v2 are eligible for data pushback.
As part of this integration, 2 new objects were created in the Integration package to hold this data. You can review the schema for each of the objects below:
Supio Case
Object API Name: supio__Supio_Case__c
The purpose of the Supio Case object is to house the main case information for the corresponding matter. It has a lookup to matter, as well as fields which hold data for details such as:
Case Information
Supio case id, case name, related matter
Patient Information
High level information such as name, DOB, state of residence, and gender
Patient Medical History
This includes things like the medical history, allergies, social history, and family history of the patient
Incident Details
This includes data extracted from the police report, and any details associated with the incident itself such as the date, location, and summary
There should only be 1 of these records per matter, and it will be updated any time that the overview information is updated with new data. You can also use this as a way to report on which case in Supio have data pushback enabled.
In order to view this information on a matter, you may want to add this to the matter page layout either as its own tab or in an existing tab by exposing the record form.
Note that Supio only has a single page layout for the Suio Case object, but you can add your own if you would like certain fields exposed in certain contexts.
Supio Timeline Event
Object API Name: supio__Supio_Timeline_Event__c
The Supio Timeline Event object houses each of the timeline events as its own record. You can consider this the Litify version of the timeline. When viewing the related timeline events on a matter, you can sort them by Date to arrive at a chronology of your client.
These timeline events contain the following information:
Date
Date of the event
Type
The specifics of what is included for each timeline event is governed by the type of event it is.
For example, a chiro visit may have different types of information associated with it than a police report
ICD Codes
If applicable to the event type
Summary
A high level summary of what the event was for
Details
Any additional details about the event which are not captured in the summary
Note that there is a field on the Supio Timeline Event object for Deleted in Supio. When this is set to true, it means that the timeline event has been removed from Supio. We recommend all reports or list views of Supio Timeline Events to exclude those records where Deleted in Supio is true