Encompass Integration - Additional Information

Additional information regarding the functionalities detailed in the Ocrolus Encompass integration can be found below.

Retry Policy for Attachment Ingestion

Ocrolus APIs interactions with Encompass subscribe to a standard, exponential retry policy. When a loan is locked by a user in Encompass Ocrolus will be unable to ingest any attachments that do not meet the criteria for upload. When this occurs Ocrolus will attempt to enter the loan again as per the below retry policy.

Retry Attempt

Duration

First

10 minutes after first attempt

Second

20 minutes after first attempt

Third

40 minutes after first attempt

Fourth

80 minutes after first attempt

Fifth

160 minutes after first attempt

Sixth

320 minutes after first attempt

After the sixth retry an Ocrolus Customer Success team member will reach out to your company's point of contact to raise the issue.

Retry Policy for Attachment Reindexing and Capture

Ocrolus APIs interactions with Encompass subscribe to a standard, exponential retry policy for results return. In the event that Ocrolus has completed classifying and capturing data from an attachment or a set of attachments and cannot access the loan because it is locked, Ocrolus will attempt to reenter the loan again as per the below retry policy.

Retry Attempt

Duration

First

1 hour after first attempt

Second

2 hours after first attempt

Third

4 hours after first attempt

Fourth

8 hours after first attempt

Fifth

16 hours after first attempt

Sixth

32 hours after first attempt

After the sixth retry, an Ocrolus Customer Success team member will reach out to your company's point of contact to raise the issue.

Notifications

A client can be enabled for notifications from Ocrolus when attachments have completed processing. In order to have alerts enabled a client must provide Ocrolus with a maximum of three role IDs from Encompass. Once subscribed, any Encompass user with one of the role IDs specified will be able to view alerts pushed by Ocrolus in the 'Alerts' column on the pipeline view.

Ocrolus currently sends alerts for the following scenarios:

Scenario

Alert Message

Attachment Upload

Follow Up (Ocrolus pulled attachments at MM/DD/YY HH:MM)

Data Return

Follow Up (Ocrolus finished attachments at MM/DD/YY HH:MM)

Duplicate Attachment

Follow Up (Ocrolus detected a duplicate attachment at MM/DD/YY HH:MM)

These alerts can also be viewed from within the loan itself in the Alerts and Messages tab of the loan.

Offboarding

If a client wants to discontinue Ocrolus services , the below order of operations must be followed so that neither the client nor Ocrolus do see any unexpected performance from any client subscriptions.

The onboarding process is as follows:

  1. Client notifies Ocrolus of a request to discontinue its service
  2. Ocrolus unsubscribes the client from webhooks
  3. Client removes or disables the ocrolus-api account from within Encompass instance

Removing or disabling the ocrolus-api account without the Ocrolus unsubscribe action may cause your Encompass instance to behave differently than expected.


Did this page help you?