apex-trigger-actions-framework

apex-trigger-actions-framework copied to clipboard

Fixes #153 Fixes an issue where including trigger action framework in a namespaced package makes custom permission checks fail if the permission is not in the same namespace. This requires...

yippie

## Expected Behavior Bypass permission should work for any custom permission ## Actual Behavior Bypass permission is only honored if the permission shares the namespace with the apex-trigger-action-framework package. ##...

yippie

Type.forName not namespace safe

1

If packaged, Actions and Finalizers use an API that cannot access classes outside of the same package. Salesforce Documentation on the Type.forName warns of this and suggests using an alternative...

yippie

Add telemetry logging support to Trigger Actions Framework

1

## Summary Implements a pluggable telemetry logging system for the Trigger Actions Framework to track Salesforce limits and performance metrics during trigger action execution. This feature addresses issue #176 by...

ssk42

Fix custom permissions namespace safety

1

## Summary - Fixed issue #153 where custom permissions were not namespace safe - Implemented namespace-aware permission checking in `MetadataTriggerHandler` and `FinalizerHandler` - Added comprehensive test coverage for the new...

ssk42

Add Bypass_Execution__c field to Trigger Action related lists

1

## Summary - Added `Bypass_Execution__c` field to all 7 Trigger Action related lists in the sObject Trigger Setting layout - Improves visibility of active/inactive trigger actions in the Automation Studio...

ssk42

cosmetic changes

5

1. Prettier updates 2. Clean workflow files 3. Remove unnecessary node modules - [ ] Tests pass - [ ] Appropriate changes to README are included in PR

dschach

Discussion: Show Limits feature

6

I'd like to develop a feature that could be activated per object, per handler, or (possibly) globally that would: At the start of a handler, output some limits to the...

dschach

I'm trying to mimic the way scheduled paths work in record triggered flows. Is there a way to do that using the trigger actions framework and an autolaunched flow instead?

gannaelsayed