Action Attributes
Details about these parameters can also be found in codebase/config/actions/actionsmodels.dtd.
|
Parameter
|
Default Value
|
Possible Values
|
Req?
|
Description
|
|
name
|
|
Name of any action defined in an actions.xml file
|
Yes
|
This is the name of an action defined in an actions.xml file
|
|
type
|
|
Name of any objecttype defined in an aactions.xml file
|
Yes
|
This is the name of an object type defined in an actions.xml file.
|
|
shortcut
|
|
true
false
|
No
|
This determines whether an action is displayed as a shortcut icon in the toolbar.
|
Naming conventions for the name of an action model can be any combination of alpha-numeric characters. Most action models are names include the component that they are used in. Your action models should have a prefix specific to your company to prevent collisions with other action models delivered with the product.
|
|
The action service is designed to hide the icons in the actions menu (or menu bar menus) for any icon which is not contained in a toolbar somewhere else in the system. The StandardNmActionService builds and keeps a list of all known toolbar icons on server startup.
The StandardNmActionService is relying on the name of the model to know whether it is a toolbar. Therefore, the name of a model used as a toolbar should contain “toolbar.”
If the toolbar model naming convention is not followed, then the action service cannot show icons as designed. However, no functionality breaks if the naming convention is not followed.
|
"
Commonly used shortcut actions (recommended maximum up to five) can be configured to appear on a toolbar shortcut area using a shortcut attribute. Example configuration for folder browser table:
An action is a shortcut action only in the context of that specific model. Note that icons for actions in the menus are be displayed for actions that also display in the toolbar.
