DevUI does not render chatmessage input with declarative workflows #4567
Replies: 2 comments
|
From my point of view, this looks like a schema-to-UI contract gap more than a rendering bug. If declarative workflows and in-memory workflows describe equivalent input concepts, the DevUI should not require a different mental model to render the same chat-style interaction. A small canonical example that shows the YAML fields required for ChatMessage-style input would probably clarify very quickly whether the limitation is documentation, schema support, or the DevUI itself. |
|
Some additional findings to share... I've been debugging the DevUI while it loads the declarative workflow. Again, the reference docs for how to properly define input schema seems a bit thin. But, no matter what I've tried, the workflow seems to always have an input type of 'Any'. Since that isn't one of the input types that the DevUI is checking for in the |
Uh oh!
There was an error while loading. Please reload this page.
I have not been able to find a working example, nor been able to figure out how to get the DevUI tool to render the ChatMessage input user experience with declarative workflows.

Example of in-memory workflow with the UI I want:
Example of declarative workflow experience:

Is this possible to do? Is there better documentation for the YAML input schema that can show me this?
All reactions