[27.0] Add AL support for OCV feedback API (#4903)#5117
Draft
edwardUL99 wants to merge 1 commit intoreleases/27.0from
Draft
[27.0] Add AL support for OCV feedback API (#4903)#5117edwardUL99 wants to merge 1 commit intoreleases/27.0from
edwardUL99 wants to merge 1 commit intoreleases/27.0from
Conversation
#### Summary <!-- Provide a general summary of your changes --> This PR adds the following API to allow AL code request submission of feedback to OCV: - **RequestFeedback**: Request general feedback for a feature, (or copilot feature). Also allows specifying an OCV sub-area (featureArea parameter). Allows the user to select if it is like, dislike, or a suggestion - **RequestLikeFeedback**: Requests feedback for a feature, (or copilot feature) when the user likes the feature. Also allows specifying an OCV sub-area (featureArea parameter). **RequestDislikeFeedback**: Requests feedback for a feature, (or copilot feature) when the user dislikes the feature. Also allows specifying an OCV sub-area (featureArea parameter). **SurveyTimerActivity**: OCV provides a concept surrounding usage time, for example if a user has used a feature for 300 seconds. They provide a trigger name associated with the survey as the activityName parameter, and start whether to start or end the timer **SurveyTriggerActivity**: OCV also provides a non-timer based trigger, which could be for example, a signal that a user pressed a button. This takes the activityName parameter for the trigger associated with the OCV survey. #### Work Item(s) <!-- Add the issue number here after the #. The issue needs to be open and approved. Submitting PRs with no linked issues or unapproved issues is highly discouraged. --> Fixes [AB#609310](https://dynamicssmb2.visualstudio.com/1fcb79e7-ab07-432a-a3c6-6cf5a88ba4a5/_workitems/edit/609310) --------- Co-authored-by: Eddy Lynch <eddylynch@microsoft.com>
onbuyuka
requested changes
Oct 10, 2025
Contributor
onbuyuka
left a comment
onbuyuka
left a comment
There was a problem hiding this comment.
This PR will not trigger a hotfix pipeline because the work item is not a bug and is not attached to an ICM. I don't see any reason this should be hotfixed too, no urgency imo. 27.x PR should be enough, then it will be available with 27.1
aholstrup1
reviewed
Oct 20, 2025
| "id": "f7964d32-7685-400f-8297-4bc17d0aab0e", | ||
| "name": "Microsoft User Feedback", | ||
| "publisher": "Microsoft", | ||
| "version": "28.0.0.0", |
| "dependencies": [ | ||
| ], | ||
| "screenshots": [], | ||
| "platform": "28.0.0.0", |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary This PR adds the following API to allow AL code request submission of feedback to OCV:
RequestDislikeFeedback: Requests feedback for a feature, (or copilot feature) when the user dislikes the feature. Also allows specifying an OCV sub-area (featureArea parameter).
SurveyTimerActivity: OCV provides a concept surrounding usage time, for example if a user has used a feature for 300 seconds. They provide a trigger name associated with the survey as the activityName parameter, and start whether to start or end the timer
SurveyTriggerActivity: OCV also provides a non-timer based trigger, which could be for example, a signal that a user pressed a button. This takes the activityName parameter for the trigger associated with the OCV survey.
Work Item(s)
Fixes
AB#609310
Summary
Work Item(s)
Fixes #