Suppress triggers in object approach, like %NOTRIGGER for sql

I had a similar problem on an old project.
Data could be entered as an object such as SQL.
In both cases there were exceptions for processing the business rules contained in the triggers. The most common was loading data imported from an external source where some mandatory values were missing. And normally this charge was done along with the normal functioning of the application.
To get around this we created control flags to be able to process this data.

Something like that:
Set ^Flag = $JOB_"|"_"Action:IgnoreBusinessRules"

On the %Library.Persistent extend class:
Class User.Sample Extends %Persistent
{

Method %OnBeforeSave(insert As %Boolean) As %Status [ Private, ServerOnly = 1 ]
{
    /// Abort business rules
    If $Get(^Flag)'="" & ($Piece($Get(^Flag),"|",1)=$JOB) & ($Piece($Get(^Flag),":",2)="IgnoreBusinessRules")  Quit $$$OK
    /// Before this point, follow normal business rules.
    Quit $$$OK
}

Trigger TrgBefInsert [ Event = INSERT, Time = AFTER ]
{
    /// Abort business rules
    If $Get(^Flag)'="" & ($Piece($Get(^Flag),"|",1)=$JOB) & ($Piece($Get(^Flag),":",2)="IgnoreBusinessRules")  Quit $$$OK
    /// Before this point, follow normal business rules.
    Quit $$$OK
}

Trigger TrgBefUpdate [ Event = UPDATE, Time = AFTER ]
{
    /// Abort business rules
    If $Get(^Flag)'="" & ($Piece($Get(^Flag),"|",1)=$JOB) & ($Piece($Get(^Flag),":",2)="IgnoreBusinessRules")  Quit $$$OK
    /// Before this point, follow normal business rules.
    Quit $$$OK
}

}