(Optional) The actions that are associated with the invocation target.

Parent elements


Child elements



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.


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:

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.
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:

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.
Describes the request to set the associated content in a given context. For example, wallpaper, images of contacts, BlackBerry Messenger avatars, ringtones, and so on.
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 using Bluetooth.




   <invoke-target id="com.mycompany.pdf.viewer">

Last modified: 2015-07-24

Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus