TransactionFinalizers compatibility updates with SFDC 230 release #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… release with finalizers having move to open beta and no longer requiring an opt-in. Removing from scratch old def accordingly
Were using an older variant of the pilot from before two method names were changed to be more future-proof.
capeterson
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since the feature has gone to open beta and no longer requires any explicit opt-in like the pilot did.
You might want to wait for the 230 release to be on more pods (currently only on gs0) before you merge this.
There were also two FinalizerContext methods that had their names changed during the pilot that needed correction to deploy against 228/230 salesforce versions.