Replies: 3 comments
-
I found a similar unsolved discussion that might be relevant to your issue: In chat-messages, the dialog "inputs:{} cannot be passed in the second time, which was last updated on October 31, 2024 [1]. Regarding your issue with the 'inputs' field in the embedded app, the 'inputs' field is intended to allow the configuration of input variables that can be passed to the Dify chatbot. These inputs are processed, compressed using GZIP, and encoded in base64 before being appended to the URL used by the chatbot [2][3]. The processing of the 'inputs' field in the embedded app is handled by the If the 'inputs' field is not interacting as expected, it might be worth checking the implementation of these functions to ensure they are correctly processing and updating the input values. Additionally, ensure that the input types and values conform to the expected formats and constraints as defined in the documentation [2][3]. |
Beta Was this translation helpful? Give feedback.
-
What I want to discuss is that within the EmbeddedChatbot method of the chatbot, no further operations are done on the inputs field. |
Beta Was this translation helpful? Give feedback.
-
Self Checks
Dify version
0.11.2
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
When I use the Inputs field in difyChatbotConfig in the embedded app, I find that it only generates a request link in the chatbot that generates the iframe, but does not do any further operations in the background code. I wonder if the role of this field should be related to the inputs field of the user-defined chat application.
✔️ Expected Behavior
I hope that the inputs field can interact with the message inputs request and be changeable, rather than being hard-coded in the conversation table.
❌ Actual Behavior
No further action is taken on the inputs field.
Beta Was this translation helpful? Give feedback.
All reactions