adminadmin schema - a set of views for more convenient interaction with system tables from the public schema - entities, schemas, table fields, triggers, constraints and others.
admin is not a system schema, i.e. it isn't added to instances by default. So after loading this schema into your solution, you can edit its views just like any other custom user views.
You will need to pick up the current version of the admin schema from the admin template. To do this, follow the link
Type admin in the left "Save Schema" field and click Save. Zip-archive with the schema will be saved to your device.
Next, go to the schema upload interface on your instance:
https://<your-instance>.ozma.org/save_restore
Select the zip-archive with the admin schema in the right "Restore Schema" field and click Restore. If the download is successful, a Success message will appear.
If an error occurs instead of a success message, you will have to manually fix the problems using the message in the error message.
You can also set the flag "Mark invalid objects as allow_broken", and schema will be forced to load, but after that you will have to manually resolve conflicts in all views marked with allow_broken = true
Please note that the schema will be completely overwritten. If you had edited views from the
adminschema or created new ones, they will be overwritten after the update.
When creating a new solution, specify admin as a template
An instance will be created for you, including the current version of the admin schema
You can deploy a neww instance with an admin schema by one button through onboarding: click here
You can also choose any of our other templates. We try to keep the admin panel version up to date in our template solutions, but if for some reason the chosen template hasn't been updated for a long time, and the admin panel in it is outdated, follow the steps from the subsection "Add or update the schema in your instance" above.
If you are using your own admin schema, you should modify it to reflect the changes below
public.events has been changed. The fields schema_name, entity_name, row_id have been removed. All information about the event is now contained in the new fields request and response. A details field of type JSON has been added, which contains the id of the inserted/modified/deleted record. Details herepublic.events has been modified.schema_name, entity_name, row_id, and details are no longer supported (they will be deprecated soon). All event-related information is now encapsulated within the new request and response fields. For more information, refer to this link.funapp.translations configures and stores translationsfunapp.user_settings stores user settingspublic.events the entity_id field has been renamed to row_iduser_view_generator_script and user_view_generator_allow_broken fields are moved from the public.schemas field to a separate table public.user_view_generators;parents field from public.roles is removed - it is no longer used;change field from public.role_column_fields is divided into insert, update and check, which allows you to more flexibly manage access rights (prohibit updates for specific fields and allow insertion, for example);schema_id field added to funnapp.iframe_markups and funapp.embedded_pages tables;save_restore_key field added to public.entities table;is_alternate_key field added to public.unique_constraints table.admin schema