Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Beberapa aplikasi dapat mengirim masukan ke EMM dalam bentuk aplikasi yang dilengkapi kunci
negara bagian. Status aplikasi yang terkunci terdiri dari
ID unik (kunci),
pesan yang sesuai (opsional), data yang dapat dibaca mesin (opsional), tingkat keparahan
status, dan stempel waktu. Untuk mengirimkannya, aplikasi perlu berintegrasi dengan
Library Jetpack Enterprise.
Aplikasi hanya dapat mengirim masukan langsung pertama satu kali setiap menit. Masukan yang dihasilkan selama periode tunggu akan dimasukkan ke dalam antrean dan akan dikirimkan sepenuhnya saat periode tunggu berakhir. Misalnya, ketika umpan balik dihasilkan 3 kali pada [t=0 s; 10 s; 15 s] dengan periode tunggu 1 menit: umpan balik langsung pertama akan dikirim pada [t=0 s], umpan balik kedua dan ketiga pada [t=60 s].
Sebagai EMM, Anda dapat menggunakan data dari status aplikasi yang terkunci untuk menjaga admin IT
selalu mendapatkan update terbaru terkait aplikasi yang diinstal di profil dan perangkat terkelola. Contoh
tentang cara kerjanya dijelaskan dalam Menampilkan masukan kepada
perusahaan.
Aktifkan laporan perangkat
Aplikasi mengirim status aplikasi dengan kunci per perangkat. Negara bagian termasuk dalam
laporan perangkat. Untuk mengaktifkan pelaporan perangkat:
Melihat status aplikasi dengan kunci di laporan perangkat
Laporan perangkat tersedia dalam bentuk resource perangkat.
Status aplikasi dengan kunci dikelompokkan menurut nama paket di bagian laporan aplikasi, seperti yang ditunjukkan dalam contoh di bawah:
Tingkat keparahan status: INFO menunjukkan pesan yang informatif. Misalnya, jika konfigurasi terkelola berhasil disetel. ERROR menunjukkan bahwa perusahaan perlu mengambil tindakan untuk memperbaiki masalah. Misalnya, jika konfigurasi terkelola gagal ditetapkan.
message
String opsional yang memberikan detail tentang status aplikasi. Developer aplikasi disarankan untuk memperlakukan kolom ini sebagai pesan yang ditampilkan kepada pengguna.
data
String opsional yang memberikan detail yang dapat dibaca komputer ke EMM tentang status aplikasi. Misalnya, nilai yang dapat dikueri oleh admin IT di konsol Anda, seperti "beri tahu saya jika data baterai_peringatan < 10 inci.
createTime
Stempel waktu yang menunjukkan kapan status aplikasi dibuat di perangkat.
lastUpdateTime
Stempel waktu yang menunjukkan kapan status aplikasi terakhir diperbarui di perangkat.
Menampilkan masukan tentang aplikasi ke perusahaan
Aplikasi dapat mengirim masukan karena berbagai alasan. Namun, penggunaan yang paling umum
kasus pengiriman status aplikasi dengan kunci adalah
memberikan masukan tentang status aplikasi
konfigurasi standar. Contoh:
Pada backend, Anda menggunakan ApplicationPolicy
untuk mengirim konfigurasi ke aplikasi.
Aplikasi akan mencoba menerapkan konfigurasi. Untuk setiap konfigurasi, aplikasi
mengirimkan status aplikasi berkunci yang menunjukkan statusnya (misalnya,
pesan atau notifikasi error).
Untuk melihat status aplikasi dengan kunci ini, Anda mengambil laporan perangkat.
Dengan menggunakan informasi dari status aplikasi yang terkunci, konsol EMM akan menampilkan
konfigurasi terkelola yang mudah digunakan.
Memberi tahu admin IT tentang error
Status aplikasi terkunci dengan tingkat keparahan ERROR menunjukkan bahwa organisasi perlu melakukan
tindakan untuk memperbaiki masalah. EMM harus selalu memberi tahu organisasi
terhadap error, baik melalui konsol EMM atau cara lainnya. Misalnya,
Konsol EMM dapat menampilkan dasbor error yang menautkan ke masukan untuk
perangkat tertentu yang {i>error<i}.
Jika status error diperbaiki, aplikasi akan mengirimkan status tindak lanjut dengan
kunci yang sama dengan status error asli dan tingkat keparahan INFO yang diperbarui. EMM
harus selalu memberi tahu organisasi segera setelah error diperbaiki. Sebagai
misalnya, hapus error dari dasbor error konsol Anda atau tandai sebagai
diselesaikan.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2024-09-11 UTC."],[[["\u003cp\u003eKeyed app states provide feedback from apps to EMMs, encompassing an identifier, optional message and data, severity, and timestamps.\u003c/p\u003e\n"],["\u003cp\u003eApps utilize the Enterprise Jetpack library to send keyed app states, adhering to a cooldown period for immediate feedback.\u003c/p\u003e\n"],["\u003cp\u003eEMMs leverage keyed app states to monitor app status on managed devices, accessible via device reports requiring enabled Pub/Sub notifications and application reports.\u003c/p\u003e\n"],["\u003cp\u003eDevice reports contain keyed app states categorized by package name, revealing app status details like severity, messages, and timestamps.\u003c/p\u003e\n"],["\u003cp\u003eEMMs should display app feedback to IT admins, especially highlighting errors and resolutions, potentially through dashboards and alerts.\u003c/p\u003e\n"]]],["Apps use keyed app states to send feedback to EMMs, comprising a unique key, message, data, severity, and timestamp. Apps integrate via the Enterprise Jetpack library and are limited to sending immediate feedback once per minute. EMMs can access this data in device reports by enabling `STATUS_REPORT` notifications and setting `applicationReportsEnabled`. Device reports contain keyed app states grouped by package, allowing IT admins to monitor app status and managed configurations. EMMs must alert admins to `ERROR` states and inform them when errors are resolved.\n"],null,["# Retrieve feedback from apps\n\nSome apps are capable of sending feedback to EMMs in the form of **keyed app\nstates** . A keyed app state is made up of a unique identifier (key),\ncorresponding message (optional), machine-readable data (optional), severity\nstatus, and timestamp. To send them, an app needs to integrate with the\n[Enterprise Jetpack library](https://developer.android.com/reference/androidx/enterprise/feedback/package-summary).\n\nAn app can only send the first [immediate feedback](https://developer.android.com/reference/androidx/enterprise/feedback/KeyedAppStatesReporter#setStatesImmediate(java.util.Collection%3Candroidx.enterprise.feedback.KeyedAppState%3E,androidx.enterprise.feedback.KeyedAppStatesCallback)) once every minute. Feedback generated during the cooldown period will be queued and sent altogether when the cooldown period ends. For example, when feedback is generated 3 times at \\[t=0s;10s;15s\\] with a cooldown period of 1 minute: the first immediate feedback will be sent at \\[t=0s\\], the second and third feedback at \\[t=60s\\].\n\nAs an EMM, you can use the data from keyed app states to keep IT admins\nup-to-date with the apps installed on managed devices and profiles. An example\nof how this might work is described in [Display feedback to\nenterprises](#display_app_feedback_to_enterprises).\n\nEnable device reports\n---------------------\n\nApps send keyed app states on a per-device basis. The states are included in\ndevice reports. To enable reporting for a device:\n\n1. Follow the instructions for setting up [Pub/Sub notifications](/android/management/notifications) for an enterprise. In [Step 5](/android/management/notifications#5_update_enterprise_to_support_notifications), include [`STATUS_REPORT`](/android/management/reference/rest/v1/enterprises#NotificationType) in `enabledNotificationTypes`.\n2. For each device, update the device policy: set [`StatusReportingSettings.applicationReportsEnabled`](/android/management/reference/rest/v1/enterprises.policies#statusreportingsettings) to `true`.\n\nYou can now [use the Pub/Sub API to get device report notifications](/android/management/notifications#6_use_the_pubsub_api_to_get_notifications).\nOr, to review a device's latest report at any time, call [`devices.get()`](/android/management/reference/rest/v1/enterprises.devices/get).\n\nView keyed app states in device reports\n---------------------------------------\n\nDevice reports are available in the form of [device resources](/android/management/reference/rest/v1/enterprises.devices).\nKeyed app states are grouped by package name in the [application report](/android/management/reference/rest/v1/enterprises.devices#applicationreport) section, as shown in the example below: \n\n {\n \"applicationReports\":[\n {\n \"packageName\": \"pkg1\",\n \"versionCode\": 101,\n \"keyedAppStates\":[\n {\n \"key\": \"key1\",\n \"severity\": INFO,\n \"message\": \"message1\",\n \"data\": \"data1\",\n \"createTime\": \"2018-10-01T15:01:22.027623745Z\",\n \"lastUpdateTime\": \"2018-10-02T15:01:23.045123456Z\"\n }\n ]\n }\n ]\n }\n\nEach [keyed app state](/android/management/reference/rest/v1/enterprises.devices#KeyedAppState)\ncontains the following:\n\n| Field | Description |\n|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `key` | The unique key identifying the state. |\n| `severity` | The severity of the state: `INFO` indicates an informative message. For example if a managed configuration is set successfully. `ERROR` indicates the enterprise needs to take action to correct a problem. For example, if a managed configuration failed to set. |\n| `message` | An optional string providing details about the app state. App developers are advised to treat this field as a user-facing message. |\n| `data` | An optional string providing computer-readable details to EMMs about the app state. For example, a value that an IT admin could query against in your console, such as \"notify me if the battery_warning data \\\u003c 10\". |\n| `createTime` | The timestamp indicating when the app state was created on the device. |\n| `lastUpdateTime` | Timestamp indicating when the app state was last updated on the device. |\n\nDisplay app feedback to enterprises\n-----------------------------------\n\nApps can send feedback for a variety of reasons. However, the most common use\ncase for sending keyed app states is to provide feedback about managed\nconfigurations. For example:\n\n1. An IT admin uses your EMM console to [set managed configurations](/android/management/managed-configurations-iframe) for an app.\n2. In the backend, you use [ApplicationPolicy](/android/management/reference/rest/v1/enterprises.policies#ApplicationPolicy) to send the configurations to the app.\n3. The app attempts to apply the configurations. For each configuration, the app sends a keyed app state indicating its status (for example, a confirmation message or error notification).\n4. To view these keyed app states, you retrieve a device report.\n5. Using information from the keyed app states, your EMM console displays the status of the managed configurations in a user-friendly way.\n\n### Alert IT admins to errors\n\nA keyed app state with severity `ERROR` indicates the organization needs to take\naction in order to correct a problem. EMMs should **always** alert organizations\nto errors, either through their EMM console or other means. For example, your\nEMM console could display an error dashboard that links to the feedback for a\ngiven device with errors.\n\nIf an error state is corrected, the app will send a follow-up state with the\nsame key as the original error state and an updated severity of `INFO`. EMMs\nshould **always** inform organizations as soon as an error is corrected. For\nexample, remove the error from your console's error dashboard or mark it as\nresolved.\n| **Tip:** Add support for IT admins to mute a specific error in case an app fails to correctly update an error state after the error is resolved."]]
