RootCause

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Overview

What It Does

The RootCause action creates a new RootCause record and associates it with a parent record (specified by domainName and domainKey). A RootCause captures why something happened - the underlying reason for a claim, incident, or loss.

Core Workflow

  1. Creates RootCause Record: A new RootCause is created and linked to the parent record
  2. Applies Field Mappings (optional): If autoFillMappingSetName is provided, copies field values from the parent record to the new RootCause
  3. Sends Email Notification (optional): If sendEmail: true, notifies the parent record's owner using the specified emailTemplateId
  4. Creates External Access (optional): If createExternalAccess: true, generates a secure link for external viewing

External Access - To Whom?

When createExternalAccess: true, the external access is created for the RootCause record itself, but the question of "to whom" depends on how the ExternalAccessType is configured.

The recipient is determined by the ExternalAccessType configuration, not by parameters on this action. The ExternalAccessType (specified by externalAccessTypeId) defines:

  • Who receives the access link (configured user, role, or external party)
  • What email template is used for the notification
  • What permissions the external user has
  • Whether a landing page is used

Common Use Cases:

ScenarioExternalAccessType Configuration
Send to claimant for reviewExternalAccessType configured to email the Claimant association on the parent Claim
Send to vendor for inputExternalAccessType configured to email the assigned Vendor
Send to adjusterExternalAccessType configured to email the Claim's Adjuster

Example: Complete Workflow

Scenario: A claim closes and you want to:

  1. Create a root cause record
  2. Copy relevant claim data to the root cause
  3. Notify the claim owner internally
  4. Send external access to the claimant for review

   {
     "actionType": "RootCause",
     "domainName": "Claim",
     "domainKey": 12345,
     "rootCauseTypeId": "15",
     "autoFillMappingSetName": "ClaimToRootCause",
     "sendEmail": true,
     "emailTemplateId": "42",
     "createExternalAccess": true,
     "externalAccessTypeId": "8",
     "revokeDate": "+30d"
   }

Result:

  • RootCause record created, linked to Claim #12345
  • Fields populated from claim via "ClaimToRootCause" mapping
  • Email sent to Claim #12345's owner (internal notification)
  • External access link created using ExternalAccessType #8 (recipient defined by that configuration)
  • External access expires in 30 days

Summary

FeatureControlled By
Root cause type/categoryrootCauseTypeId
Field populationautoFillMappingSetName
Internal email notificationsendEmail + emailTemplateId → sent to parent record owner
External accesscreateExternalAccess + externalAccessTypeId → recipient defined by ExternalAccessType config
Access expirationrevokeDate + relativeToDate
Path Params
string
required
Defaults to Claim

The RootCause action can operate on any domain that supports root cause analysis. The most common domain is Claim (for tracking root causes of claims/losses), but it can technically be executed on any domain where root cause tracking is configured and meaningful.

Consider using /OrigamiApi/api/RootCauseType/Query?filter=Domain.Name:eq:Claim to validate if the domain is enabled for RootCause associations.

integer
required

This is the ID of the record you are attaching the RootCause to.

Body Params
parameters
object
required
Response

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json