[16.0][IMP] ai_oca_bridge: support server_action result_type and field-based trigger for ai_thread_update #52
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
thienvh332
force-pushed
the
16.0-imp-ai_oca_bridge_2
branch
from
03049fb to
8d1e49b
Compare
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.
Summary
This PR extends the AI flow by adding a new generic
server_actionoption to theresult_typefield and introducing a field-based trigger condition specifically for theai_thread_updateusage.Changes
server_actionas a new selection value for theresult_typefield (generic, shared across usages).ai_thread_updateusage.examples/directory to contain usage examples for the module.Motivation
The new server_action result type allows reusing standard Odoo server actions to process the output of the workflow.
The field-based trigger condition enables more precise control over when the
ai_thread_updateflow is triggered, reducing unnecessary executions and aligning better with real update scenarios.Approach
The workflow directly calls the webhook with the LLM execution result, avoiding n8n data transformation, which keeps the implementation simple and consumer-agnostic while preserving full traceability in Odoo.