Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Custom Error

The Custom Error activity is used with Before Save workflow and Callback workflow types. It prevents invalid records from being saved by stopping the workflow and displaying a clear error message when conditions are met. Errors can be shown either as a popup on the record page or inline on the specific field.

Considerations and Limitations

  • Works only in Before Save and Callback workflows.
  • Each field can show only one error message.
  • Each Custom Error activity can display only one error message. Add more activities if you need more messages.
  • Error messages can be up to 255 characters long.
  • Some field types, like compound fields, are not supported. For example, BillingAddress is a compound field made up of subfields such as BillingStreet, BillingCity, BillingState, BillingPostalCode, and BillingCountry. You cannot apply a Custom Error on the entire BillingAddress field; instead, point the error to a specific subfield such as BillingCity or BillingPostalCode.
  • Global errors (page-level messages) cannot use field values such as Agreement.Name.
  • Some record types (like OpportunityTeamMember and CampaignMember) do not support custom errors when records are being deleted.
  • Errors cannot run in the background (asynchronously) and cannot be reused across workflows.

Example: Workflow checks whether the agreement type is valid before saving a record. If the agreement type is MSA, the workflow continues as normal. If it is not, the Custom Error activity shows a message such as "Contract type is not valid.". This message appears to the user and is also returned in the system response, helping the user fix the problem before saving the record.

Configuration

When you add this activity to a workflow, configure the following:

Field

Description

Details

Display NameA simple name for the activity.
Reference NameA unique identifier for the activity within the workflow. It is automatically generated from the Display Name if not specified manually.
DescriptionOptional text to explain the purpose of the activity.
Properties
Error Type Specifies how the error message appears to the user.
  • Popup on the record page: Displays the error at the top of the record page, useful for workflow-level or global issues.
  • Inline error on a field: This option is not yet supported. This functionality will be available in a future release.
Error MessageSpecify the text that appears when an error occurs. The message can be up to 255 characters long. Example: "Contract type is not valid. Please select an allowed value."
Note: This field is displayed only when the Error Type is set to Popup on Record Page.

You can also use variables and formulas in this field. However, formulas that depend on a context record are not supported.

  • Supported example: FN.CONCAT("Contract Start Date can't be greater than ", FN.ADDDAYS($Variables.DateVar, 10))

    This formula uses only variables, so it can be used in the Error Message field.

  • Not supported example: FN.CONCAT(Agreement.Name, " is invalid")

    This formula references a record field (Agreement.Name), so it cannot be used.