Use this table to look up the new intent names. The second activity, the release of Knox version 3.0 in January 2018, we started using a new namespace for Knox SDK intents. Selecting a particular person to view would result in a new intent is similar to the pick action, but allows the caller to specify the kind of data they want back so that the system can find the appropriate activity to pick something of that data type. This example is a typical top-level entry into the Contacts application, showing you the list of people. Note how the VIEW action does what is considered the most reasonable thing for a particular URI.ĪCTION_DIAL tel:123 - Display the phone dialer with the given number filled in.ĪCTION_EDIT content://contacts/people/1 - Edit information about the person whose identifier is '1'.ĪCTION_VIEW content://contacts/people/ - Display a list of people, which the user can browse through. The primary pieces of information in an intent are:Īction - The general action to be performed, such as ACTION_VIEW, ACTION_EDIT, ACTION_MAIN, etc.ĭata - The data to operate on, such as a person record in the contacts database, expressed as a Uri.ĪCTION_VIEW content://contacts/people/1 - Display information about the person whose identifier is '1'.ĪCTION_DIAL content://contacts/people/1 - Display the phone dialer with the person filled in.ĪCTION_VIEW tel:123 - Display the phone dialer with the given number filled in.

For information about how to create and resolve intents, read the Intents and Intent Filters developer guide.

Android studio intent set action