Breezz Trigger Configuration


To configure Breezz trigger we need to go Breezz Setup → Triggers → New or simple Configure Trigger from Dashboard.

After clicking New we can see the form to create configuration.

Configure New Trigger Configure New Trigger

Fields Details:

  • Name - Name of the configuration.
  • Order - Determines Order of execution trigger.
  • Is Active - Determines if handler is active.
  • Feature Availability - This is special metadata that tells us when the functionality is active. In this field you must enter the name of the created Breezz Feature Toogle.
  • Entry Criteria:
    • Object Name - Object API name which will be handled by trigger.
    • Trigger Event - Before Insert, After Insert, etc. See Recursion Prevention Configuration below.
    • Records Split Strategy - Record Split Strategies allows to filter out Trigger Context and run Steps only for specific records. For more details, refer to the section below.
  • Create Default Step Group: - Enables the selection of whether the trigger should be linked with the newly formed default step group or any other pre-existing group.
    • Yes - Default step group will be created automatically. For more details, refer to the section below.
    • No - Advanced Trigger Configuration card will appear. For more details, refer to the section below.

Records Split Strategy

Record Split Strategies allows to filter out Trigger Context and run Steps only for specific records. Available options:

  • All - Trigger will process all the records.
  • Record Type - Trigger will process only records with selected Record Type.
  • Custom - Trigger will process only records based on the results of TriggerRecordsSplitStrategy interface implementation.
  • Condition - Trigger will process only records meeting conditions Records Split Strategy - Condition Records Split Strategy - Condition
    • supported operators: Equals, Does Not Equal, Less Than, Less Than or Equal, Greater Than, Greater Than or Equal, In, Not In, Is Set, Is Not Set, Like, Not Like, Starts With, Ends With, Does Not Start With, Does Not End With, Is New, Is Changed, Is New Or Changed
    • supported value types: Value, $Record, $User, $UserRole, $Profile, $Organization, $System, $RecordType, $CustomPermission, $Label, custom settings

Default Step Group Configuration

Default Step Group Configuration Default Step Group Configuration

Default Step Group Configuration

This card is accessible when Create Default Step Group is set to Yes.

Default Step Group Configuration provides control over the following settings:

  • Record Level Security - Determines Steps group Record Level Security used in DMLs.
  • All Or None - Determines whether Change Handler will apply ‘all or none’ or ‘partial success’ strategy during related objects modification.

Advanced Trigger Configuration

Advanced Trigger Configuration Advanced Trigger Configuration

Advanced Trigger Configuration

This card is accessible when Create Default Step Group is set to No.

Advanced Trigger Configuration provides control over the following settings:

  • Steps Groups 1-4 - The trigger executes these groups sequentially to ensure proper segregation of functions. Each group operates within its own isolated execution context, including DataStore and ModificationContext.
    Notice

    Running logic across multiple groups is highly inefficient. It’s recommended to consolidate the logic into a single group whenever possible.

  • Trigger PRE-process Hook - Defines additional logic to be executed before the Steps. Provide the class name of the class that implements the TriggerProcessHook interface.
  • Trigger POST-process Hook - Defines additional logic to be executed after the Steps. Provide the class name of the class that implements the TriggerProcessHook interface.

Recursion Prevention Configuration

Recursion Prevention Configuration - None Recursion Prevention Configuration - None

Recursion Prevention Strategy

This card is accessible when Trigger Event is set to either Before Update or After Update.

Recursion Prevention Strategy determines the approach used to mitigate the risks and negative consequences of recursive trigger execution. Depending on the business processes involved, recursion might be desired or not.

Recursion Prevention Strategy can be set to:

  • None or
  • Skip Repeated Records for which one more field is required:
    • Total Number of Recurrences - maximum depth of recursion Recursion Prevention Configuration - Skip Recursion Prevention Configuration - Skip