Most Powerful Open Source ERP

Guideline Define Document Actions As Global Actions

Global actions will automatically be present.
  • Last Update:2019-07-15
  • Version:001
  • Language:en

Define Document Actions As Global Actions

Other actions are defined as global actions, they will automatically be present. If actions already exists on the portal type, you should remove them. Actions added for a document are:

  • Print: permission View, category object_print, id print and action string:${object_url}/Base_printPdf
  • History: permission View, category object_view, id history and action string:${object_url}/Base_viewHistory
  • Metadata: permission Manage properties, category object_view, id metadata and action string:${object_url}/Base_viewMetadata

The order of the actions of category object_view (which are defining tabs in the user interface) has to be the following : view, other views (example : details), history, metadata. For the ZMI view, the order goes from top to bottom. You should define the priority of actions according to that order (this is also valid for the modules portal types).