[Payables Agent] Fix HITL dialog for historical matching to show AI-generated message. #5366
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
…type - Remove overload that accepted E-Doc. Purchase Line History (no longer sets the draft's history id or telemetry). - Use a single UpdateMissingLineValuesFromHistory signature with an explicit ExplanationTxt parameter and stop merging with a default explanation. - Ensure Activity Log builder explicitly sets the Activity Log Type (AI).
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.
This pull request refactors the handling of explanation text and activity log entries in the
UpdateMissingLineValuesFromHistoryprocedures within thecodeunit 6120 "E-Doc. Purchase Hist. Mapping". The main focus is on simplifying the explanation text management and ensuring that activity logs are consistently marked as AI-generated. Below are the most important changes grouped by theme:Refactoring of Explanation Text Handling:
UpdateMissingLineValuesFromHistoryprocedure that accepted a history record, consolidating logic to use the version that works directly withPurchInvLine. This reduces redundancy and simplifies the update process.CustomExplanationTxtparameter toExplanationTxtand removed the logic for selecting between a default and custom explanation, making the explanation text usage more straightforward.Activity Log Improvements:
SetActivityLogto use the unifiedExplanationTxtparameter, ensuring consistent logging of explanations for field updates. [1] [2].SetType(Enum::"Activity Log Type"::"AI")to activity log creation, explicitly marking these logs as AI-generated for better traceability.Fixes AB#611426