Added views for the "translations" table funapp.translations
All userview names, field captions, procedure invocation buttons, and argument filters in the argument editor now support translation in English, Spanish and Russian. Views from the admin schema use the language selected by the user as the language in Ozma.
Added documentation links for quick access to useful information directly from the views in Ozma:
On the user view edit form, directories have been added to the right of the query editor:
On the trigger and action edit form, a directory has been added to the right of the code editor:
When creating a new user view, a template-placeholder with a FunQL query for a form, table, or kanban board is automatically created. You need to choose one of the queries, uncomment it, replace entity names in it, add fields, and links to other views.
When creating a trigger or action, a template-placeholder with a JavaScript function is created, and you need to write the implementation depending on the automation purpose.
When creating an iframe code, a template-placeholder with simple HTML code is created, with the necessary scripts and d3.js (optional) included. The body contains a script that processes data received from the view.
When creating an embedded page, a template-placeholder with simple HTML code is created, with the necessary scripts and Bootstrap (optional) included. The body contains an event necessary for the correct functioning of links and a simple example page with three elements that can be modified.
Added automation that allows generating:
The menu is displayed to the user immediately after creation and is always available in the list of views.
Generating views from templates eliminates the need to manually create views for each new entity at the beginning of development. From the created views, you can assemble a new menu or modify the existing one. Created views can be worked with just like regular views: renaming, adding attributes, changing links and columns, adding and modifying nested views.
Note that the generated views are interconnected (tables and kanban boards have links to forms), so when renaming a view, it needs to be renamed in multiple places.