Although ISimlAdapter interface is marked experimental, it shouldn't be much of a concern for now as internally all official SIML Modern adapters implement the same interface. It's just a matter of time as the team removes the "experimental" tag from future documentations.
Majority of the developers, including us, go by a mixed model of SIML Modern + C# Code as it helps a lot in decoupling projects, increasing modularity and lowering project maintenance. SIML Modern was designed around Oscova and not the other way around. So basically when an SIML document is loaded t...
We've already started receiving developer feedback and are going to add a few more features. Indeed, a mechanism to add and remove domain values is going to be available. Actually the feature was supposed to make it in RC1 but due to time constraints we decided to introduce it in RC2 which is schedu...
The sole purpose of OSCOVA is to understand the semantics and syntactics of Human Natural Language. It has nothing to do with how the front-end application UI generates or displays responses. Adaptive cards are nothing but a way to display content across devices so I would consider that something to...
Which platform are you using the framework in? Also could you shed some light on which version of .NET framework are you targeting in your project or application. This is really hard to produce on our end as the code wouldn't compile however I am certain its probably DLL file version conflict that m...
This behavior is expected in certain request types as @sys.text uses character level parsing. This is one of the many reasons why we recommend creating entity types wherever possible. Does the behavior persist if you use " Search for DISPLAY_NAME who works in DEPARTMENT_NAME " ? Current solution wou...
I was indeed able to reproduce this in Bot Studio, that runs 2.6.0 version of Syn.Bot framework, but it seems to be working just fine in a Console application that references Syn.Bot 2.9.4. Although I understand that your actual SIML code would be slightly more complex, could you firstly, confirm th...
Well, when you specify an entity type using @ in an Expression. The intent is only invoked if and only if that entity is present in user input. Insights on why your intent isn't working. //You are extracting @myentity [Expression("Who is @myentity")] public void EmployeeName(Context context, Result ...