Hack! 2022

35 Registered Allowed team size: 1 - 5
35 Registered Allowed team size: 1 - 5

This campaign is over.

Idea Submission Phase
Online
starts on:
Apr 01, 2022, 04:00 AM ()
ends on:
May 17, 2022, 04:59 PM ()
Prototype Submission Phase
Online
starts on:
May 23, 2022, 04:00 AM ()
ends on:
Jul 11, 2022, 03:59 AM ()

Crowdsourced Ideas

You can use these crowdsourced Ideas for your projects.

1. Speech-to-text 
This is purely based on a real-time use case need that we have out in the field for Carman, crew - engineers/conductors, Mangers, and supervisors wherein they should be able to speak to the pooled device (Zebra) and the application (e.g. MoBI - Mobile Billing and Inspection) should be able to parse it out and take the necessary actions. This is beyond using a simple microphone on a Gboard.

2. Global User Security Profiles for Production Support and Testing (go/security profile)

Problem Statement: There is currently no unified or accepted process to allow production support personnel to easily emulate a users set up to address production support issues.

  • When customers call in saying they have an issue with a system, it is cumbersome or impossible to verify what the user is seeing in production without a lengthy setup process.
  • To properly test customer-facing applications, our teams spend a lot of time setting up users id's with appropriate primary and secondary business groups, roles, role locations, role custom attributes, authorized locations, and other security attributes.

Proposition

  • Augment the User Association cache (go/userAssoc) to encompass the entirety of a users Security Profile: Locations, Roles, Roles with Custom Attributes, Roles with locations
  • Update existing security services (authorized locations, expanded authorized locations, roles, AZM policies, CPT services, etc) to point to the services provided by the User Association cache
  • Create a way for specific users, identified via AZM rules, to change the Security Profile that is returned for their user-id to allow the logged-in user to have the same security set up as the user with an issue.
  • Create services that allow developers to specify that a user ID has a specific Security profile for the duration of a test case.  This would allow easily repeatable integration testing.

Social Share

Notifications
View All Notifications

?