Hi @Igor Barboza, this was changed for version 3.4.0 in PR #1681. You can view that and the linked issue for more detailed reasoning for the change, but in short we had reports of files being synced to the server automatically with incorrectly generated names. We decided that it would be preferable to avoid that at the cost of the user having to add the class name manually. The cursor will be automatically placed in the correct position in the document though.

A REST implementation method can do anything, including Dynamic SQL queries. Do you need to allow arbitrary SQL execution though? If all you need to expose is the data in one table with some filtering you can have an endpoint like GET /epic/master (path is arbitrary) and have query parameters for filtering. The implementation can use SQL to popular the results under the hood without needing the end user to write SQL.