| Info | ||||
|---|---|---|---|---|
The objectactions was introduced after the objectdata domain in order to be more precise regarding the actions the user can perform.It is disabled by default.in
When the domain "objectactions" is not activated then the system uses "objectdata" rules to decide if the buttons “create” / “delete” / “order” will be shown to the user. |
The domain "objectactions" is there to complement the domain "objectdata" when the instance does not exist yet, or the action is not run yet. This is oriented to showing or not the UI buttons that lead to the future actions.
For example, to decide if the user will have a “new” button the “objectactions/create” rules will be run.
When the user actually save the new instance, the “objectdata/insert” rules will be run.
For example, to decide if the button “bulk update” will be shown to the user, the “objectactions/multiupdate” will be run.
When the user execute the bulk actions, the system check against the “objectdata/update” rules before actually updating the data.
In this domain, the new security rules available are :
create: can a new instance of this object be created ?
delete: can an instance of this object be deleted ?
order: can the instances of this object be ordered ?
multiupdate: si the bulk update function available ?
datavaluespicker: is it possible to pick some content to past on new instance or during multi-update ?
damimport: is it possible to bulk import via damimport ?
massimport: is it possible to bulk import directly in the object ?
i18nFieldsTranslate (since
): is it possible to open the i18n translation screen ?Status title 2022.5.0