CT SOP Integration Administration (DRAFT)

The following administrative information provides references for getting started, understanding API utilization and specific data definitions for the fields used in the integration.

Pilot Release
This integration is currently in pilot release. During the pilot period a subset of our customers will have an opportunity to try the integration prior to being released to our broader customer base. It's a great time for us to receive your feedback prior to the formal release. If your organization is interested in participating in the pilot, please contact your AdvoLogix account executive.

1. Administrative Quick Facts

Quick Start Overview

Review the integration's introduction article then follow the steps outlined in the getting started article.

Package Distribution

The AdvoLogix integration for CT SOP is distributed as an add-on managed package. The package consists of custom data objects, apex classes, page layouts, record pages, lightning components, lightning actions. 

2. SOP Log (object)

Within the AdvoLogix integration, SOP Log is the platform data object which contains SOP meta-data (provided by CT) and workflow information (provided by the integration) . 

The SOP Log is a standard custom object and can be added to application menus or Lightning pages. The SOP Log object also supports the full range of platform capabilities such as workflow, reporting and collaboration.

Data Fields
General Information

The fields in this area uniquely identify the SOP Log and provide relevant details of the SOP's workflow status.

  • Log ID: Unique identifier for the underlying SOP. *
  • Log Status: Values can be Initial or Amended.  Identifies the status of the log within the integration.  All logs are defaulted to Initial, the first time they are added to the integration. Logs are updated to Amended if a change is subsequently submitted (through CT). This field is read-only and managed by the integration. 
  • Disposition: Values can be Pending, Routed Elsewhere, Matter Created, Matter Linked. Represents the current end result of the business processes. The default value is Pending. Users update this value as the workflow process evolves. Disposition values of Matter Created and Matter Linked should require an entry in the Matter lookup.
  • Assigned To: The internal user responsible for facilitating the SOP's business process. This field is optional. We suggest organizations use an automated business process to facilitate this assignment. This user may also play an active role in the notification and collaboration process.
  • Routed To: Account lookup for use when routing SOP's elsewhere.
  • Matter: Represents the Matter related to the underlying SOP. See this article for more information on creating a new Matter from an underlying SOP Log.
  • Stage: Values can be Pending, In Review, Closed. Represents the current stage of the business processes. The default value is Pending. Users update this value as the workflow process evolves.
  • Comments: Used at the user's discretion for internal comments. 
Case Details

The following case details represent the values defined by and provided to the integration from the CT Service of Process. For this reason, these fields would not typically be modified.

  • Plaintiff: Provided in the CT SOP Log*
  • Defendant: Provided in the CT SOP Log*
  • Lawsuit Type: Provided in the CT SOP Log*
  • Lawsuit Sub Type: Provided in the CT SOP Log*
  • Served Jurisdiction: Provided in the CT SOP Log*
  • Served Name: Provided in the CT SOP Log*
  • Case Type: Provided in the CT SOP Log*
  • Case Number: Provided in the CT SOP Log* 
Key Dates

This area contains relevant date details for the underlying SOP. With the exception of Scan Date, these dates are managed by the CT Service of Process. 

  • Created: Provided in the CT SOP Log. Identifies the timestamp when the SOP was created within CT.
  • Receipt Date: Provided in the CT SOP Log
  • Last Update: Provided in the CT SOP Log
  • Stage Date: Updated when the SOP Log Stage changes. This value is managed by the AdvoLogix integration.
  • Scan Date: Represents the date and time when the log was scanned or updated by the integrations log scanning process. This value is managed by the AdvoLogix integration.
  • Last Acknowledged: Indicates the date of the last acknowledgement for the underlying matter. This value is managed by the integration and is derived from the Acknowledgments related to the underlying matter.
Triggers

Stage Date is set to the current date/time when the value of the Stage field changes.

Validation Rules

Validates the Disposition value is not Pending when the Stage is set to Closed. The validation rule can be deactivated If this is not desired.

3. SOP Acknowledgement (object)

SOP Acknowledgements are related to a specific SOP Log and contain the current status of each SOP Acknowledgement submitted for the underlying SOP Log.  The ability to submit Acknowledgements is "opt-in" option at the organizational level.  

Supplemental Pilot Release Note 
SOP Acknowledgements are not available during this pilot.