feat: PrintVis Support Ticket Classifier — AI-powered PromptDialog (objects 50110–50112)#14
Draft
MBPrintVis with Copilot wants to merge 3 commits into
Draft
feat: PrintVis Support Ticket Classifier — AI-powered PromptDialog (objects 50110–50112)#14MBPrintVis with Copilot wants to merge 3 commits into
MBPrintVis with Copilot wants to merge 3 commits into
Conversation
Copilot
AI
changed the title
[WIP] Add PrintVis support ticket classifier prototype
feat: PrintVis Support Ticket Classifier — AI-powered PromptDialog (objects 50110–50112)
Jun 23, 2026
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
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.
Adds a Copilot-assisted support ticket classifier to the Prototyping app. A support agent pastes raw ticket text; Azure OpenAI classifies it into one of nine standard categories with a confidence score, rationale, and suggested next action.
New objects
PVS Ticket Category— Issue, HowTo, EventRequest, Idea, License, BCRelated, TechnicalQuestion, ResourceRequest, OtherPVS Ticket Classification— log (Blob ticket text, category, confidence, rationale, suggested action, timestamp, user)PVS Ticket Classifier AI— Azure OpenAI via BC Copilot toolkitPVS Ticket Classifier—PromptDialogPVS Ticket Classification Log— list view"Copilot Capability"with"PVS Ticket Classifier"(value 50110)PVS Ticket Classifier Install— registers capability on installPVS Ticket Classifier— RIMD on Table 50110, Execute on Codeunit/Pages 50110–50111PVS Support Tools— standalone Card entry pointAI codeunit
[TryFunction]on the publicClassifymethod; caller checks the Boolean return and callsGetLastErrorText()on failure. Category parsing is case-insensitive (LowerCase()) to guard against AI response variation. Category → StyleExpr mapping is centralised inGetCategoryStyleand reused by both pages.No setup table — relies on BC's managed Copilot resource (
IsEnabled+SetCopilotCapability); endpoint is expected configured at the BC environment level.PromptDialog UX
Promptmode; switches toContentafter successful classification.StyleExpr: Issue =Unfavorable, EventRequest/Idea =Favorable, all others =Ambiguous.Messageif AI response text exceeds field storage limits before truncating.