Issues and Feedback about Smart Assertions
Some issues and feedback about Smart Assertions after a day or so of using them. I would like to provide some hopefully helpful feedback on the newly introduced Smart Assertion. Please set the def...
Forum Discussion
Guess I was a little quick on the draw ... If you click Cancel after "reviewing" what was configured, what was originally configured will be displayed.
The one major issue i have with smart assist is the idea that writing a text trying to inform the user that data will be lost if you swap between the two types is just to me proof that this feature should never have been released in its current state
If it atleast would have been an annoying pop up confirm dialog so you are forced to read that your work will be deleted would be better and then can select cancel/continue
Smart insert simply needs to be split into two asserts one for each tab unless it can be changed so that you can effortless move between the two types without losing data
Metadata and message content assertions should be completely separate assertions because switching the type destroys all the data you have added. How can you modify previously added assertions when all the values are lost? It is the same as not having a modify smart assertion feature at all.
What we have started doing (yes its a "pain point") is to create 2 separate smart assertions, one for "Received Data" and one for "Received Metadata" and then naming them accordingly so users will know which smart assertion to update and / or check if an error is returned.
- Yes, I ended up doing the same 👍
