List of Exceptions in Litify Managed Package


This is a list of all exceptions you might come across while using the managed Litify package. This table includes the name of the exception, and the indications or actions that cause the exception. If you're not sure what caused an exception, look for the exception on this chart and identify the indications that caused it. 

 

Name Indications Product
AccountHandlerException Attempt to set account name to blank in AccountHandler.cls PM
CQCEvaluationException CQC criteria cannot be evaluated e.g. using Contains operator with an integer PM
CaseTypeHandlerMockException Used exclusively for unit tests PM
ContactHandlerException Attempt to create a 2nd contact for a Litify Individual account PM
CriteriaHandlerException Questionnaire criteria cannot be evaluated e.g. answer type is not supported PM
ParseCriteriaException Questionnaire criteria cannot be parsed. Criteria is expected to be stored as a JSON array with each element having a value_1, operator, & value_2. PM
ParseCQCModificationsException CQC Modifications cannot be parsed. Modifications are expected to be stored as a JSON array with each object having properties value, sobject_name, & field_name PM
CustomPermissionsException Attempt to use a custom permission that does not exist PM
DBException Attempted DB operation is not allowed. Could be because of permissions or update is attempted on object that is not updateable etc. PM
FirmHandlerMockException Used exclusively for unit tests PM
GenerateQuestionnaireException Not in use PM
HandlerUnableToConnectToLitifyException Refresh of data from Litify referrals failed due to connection issue PM
IntakeHandlerException Cannot retrieve questionnaire output and no default questionnaire exists PM
LitifyActionsMatterHandlerException Litify Action failed on matter. E.g. matter id doesn't exist, close reason doesn't exist, sub-status doesn't exist, etc PM
LitifyActionsHandlerException Failed to convert referral to intake PM
LitifyHandlerMockException Used exclusively for unit tests PM
HTTPException Generic HTTP error from LitifyServices PM
SessionTokenExpiredException Invalid session token encountered in LitifyServices PM
RefreshTokenExpiredException Invalid refresh token encountered in LitifyServices PM
LitifyServicesProxyException Refresh of data from Litify referrals failed due to connection issue PM
MatterHandlerException Attempt to create a Matter from an Intake with no client PM
NoOperatorException Criteria is missing operator or contains operator that is not valid for type e.g. "Contains" operator for "Date" field type PM
QuestionnaireHandlerException Questionnaire name is not unique PM
QuestionnaireNavigationHandlerException Attempted navigation on questionnaire is invalid e.g. attempt to go back when there are no previous questions or attempt to navigate to nonexistent question node PM
QuestionnaireOutputParserException Questionnaire Output cannot be parsed. Questionnaire Output is expected to be an array of Ids PM
QuestionnaireParserException Questionnaire questions cannot be parsed from JSON PM
SObjectModificationParserException Error occurred parsing SObjectModifications from JSON PM
ReferralHandlerException Error occurred handling referral action PM
ReferralOutboundHandlerInboundMockException Used exclusively for unit tests PM
ReferralOutboundHandlerException Never thrown. Logged if referral sync status is dead PM
ReferralOutboundHandlerMockException Used exclusively for unit tests PM
RuleDateEvaluatorException Attempt to evaluate date-based criteria errored out PM
RuleDatetimeEvaluatorException Attempt to evaluate date-time-based criteria errored out PM
RuleMultiSelectEvaluatorException Attempt to evaluate multiselect-based criteria errored out PM
RulePathHandlerException Exception occurred when attempting to evaluate criteria (hides CriteriaHandlerException, NoOperatorException, and any other exception thrown by criteria_handler.evaluate_criteria function) PM
SchemaHandlerException Error attempting to find class by name in SchemaHandler.cls PM
GenerateQuestionnaireException Not in use PM
Was this article helpful?
0 out of 0 found this helpful