Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENHANCEMENT: Automate trigger file creation, base dummy trigger action and trigger action base test #133

Open
ctcforce opened this issue Jan 10, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@ctcforce
Copy link

This is not an issue, the following is a feature request.

Needing to create the actual trigger file for an object along with creating the SObject Settings MDT record for and object is something that would benefit from being automated.

By means of the metadata api(?) could the TAF automatically make a generic Trigger file for an object at the click of a button on that Object's SObject Settings MDT record's page layout, via a url field on the MDT record?

This would remove a manual setup step for enabling the TAF for new objects in the future.

It could also generate a base trigger action for that object.

Then there could be a "Test your Trigger Action" button on the SObject Settings MDT record that verifies that the apex in the dummy action's apex code was successful executed by the framework.

We're considering implementing all of these on our client projects that use TAF to increase client confidence in this technology and subsequent adoption.

Additionally, a nice quality of life feature would be a validation rule that prevents you from making any Trigger Action MDT records for an object if the TAF detects that there doesn't exist a TAF enabled Trigger file for that object.

@mitchspano mitchspano added the enhancement New feature or request label Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants