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.
Post Deployment:-Please Assign the Permission set "NPS Integration Permission" to user.
Limitations:- we can't have a return type for apex class in this solution because of record triggered flow since salesforce doesn't allow Callout operation after DML operation in Same transaction and since as per order of execution in salesforce the salesforce doesn't commit all the changes to org unless it has run all the before and after transaction so the callout is done asynchronously in this solution. Since Salesforce carry asynchronous apex after committing all changes to org and if we try to do the callout after DML operation in synchronous apex we will get the error of "you have uncommitted work pending" so asynchronous solution is suitable with record-triggered flow .
I have created a custom object to track all the error encountered during NPS Callout operation. This will help Admin to know the issue encountered during callout operation.