Hi,
I previously posted a message with questions about schemas. Now, I'd like to discuss some problems I'm encountering.
Bugs or Issues
1- Currently, creating a schema and assigning it to a variable works. However, modifying the schema is not straightforward. If you change the schema by adding a new property and then use the chat to start the conversation, the AI Task Card, which is the first action I do to initialize the schema with empty data, does not consider the changes. At that moment, the All Variables area in the Studio interface displays the variable and its content according to the old properties, without the modifications.
To fix this refresh issue, the only option that sometimes works is to change the name of the schema or the variable. In both cases, these are not solutions but workarounds. There seems to be a memory notion that remains in place with the AI or other. During development, it's normal for schemas to evolve, and the AI should consider this.
Any idea to solve this problem?
2- Another issue is accessing properties in the editing interface.
Initially, without initializing the variable with empty data by an AI Task Card at the beginning of execution, the issue was that the variable was null. That said, once initialized with the AI, it is possible to access the property and see if data is saved or not. However, in the studio interface, it's as if these properties do not exist. For example, if we use a Person Name Card, we can access the first and last properties in Execute Code Card or in Text Cards. When using workflow.myVarName.first, it displays in green to show possible property access. With a variable of a schema type, we can access the variable, workflow.mySchemaVar, but access to the properties is not immediately possible; it displays in red. It's as if the properties do not exist. Yet, if I declare a variable with the type "MySchemaX," I should be able to access the properties in my editing interface.
Any solution for that?