(Optional) The actions that are associated with the invocation
target.
Parent elements:
<filter>
Description:
The <action> element specifies
the actions that are associated with the invocation target. Actions are strings that
identify the operations that your application is registered to handle. Actions can
be discoverable actions or menu actions. Menu actions always have label and icon
associated with them, while discoverable actions do not.
Content:
A PCDATA value representing the actions that are available that can be queried. These
actions do not have graphics or labels represented on the user interface but can be
queried. The following predefined discoverable actions are examples of actions that
are available:
- bb.action.VIEW
- Describes the request to open a card or viewer based on the
given MIME type, URI, or file name extension. This action should be used
in cases where you register a card or viewer as a default handler.
- bb.action.NOTIFY
- Describes the act of notification which can be associated with
different types, such as the BlackBerry
Push Service.
The following fixed menu actions are examples of actions that are available.
These actions are represented in the OS using graphics or labels and can differ
based on the locale and regions settings:
- bb.action.OPEN
- Describes the request to open associated content in a different
application. You can use this action in cases where you want a
full-context switch from one application to another. Use this action in
scenarios where a full application is registering as a default handler.
- bb.action.SET
- Describes the request to set the associated content in a given
context. For example, wallpaper, images of contacts, BlackBerry Messenger avatars, ring-tones, and so on.
- bb.action.SHARE
- Describes the request to share associated content. For
example, you can share an image to Bluetooth target, which would transfer the image to another device via Bluetooth.
Example:
<qnx>
...
...
<invoke-target id="com.mycompany.pdf.viewer">
<invoke-target-type>viewer</invoke-target-type>
<filter>
<action>bb.action.VIEW</action>
<action>bb.action.EDIT</action>
<mime-type>application/pdf</mime-type>
<mime-type>application/x-pdf</mime-type>
</filter>
</invoke-target>
...
...
</qnx>