Filtering
Last updated
Last updated
Managing the access and use of sensitive data is a key pillar of enterprise security. Role-based access control (RBAC) enables complex network environments to meet privacy and confidentiality regulations while securing business processes. Launcher's session application are based on RBAC to simplify granting data only to relevant users. Intent filtering applies this same principle to the intents that can be triggered to automatically run on devices at various triggers.
Filtered intents allows IT administrators to determine what intents will run on specific Android enterprise devices based on the logged-in user's session, device, or extended attribute information.
Intents can be filtered to match any session, device, or extended attribute (for example: session.groups, session.location, session.userId, device.MODEL, device.BRAND, config.ex.deviceId, config.ex.siteId).
Use the documented to build an intent
Include a "filter"
object where:
The replacement variable key is paired with a string
The string lists one or more values to include in the filter
Use a pipe ( | ) symbol when listing multiple values
Alternatively, filtering can be accomplished with and/or and regular expressions (regex).