Skip to main content

"Smiling Hill" Employee Web

😊⛰ Smiling Hill is the codename for a proposed project to centralize several key in-house employee-facing web apps into one single modern web app. Although Oregon is the primary customer, it serves all jurisdictions alike.

I (black@pndlm.com) currently consider some form of this application a pre-requisite for 3rd Fork/Iowa and for Oregon Account Status.

Benefits​

  • Modern: built on still-in-support technologies
  • Centralized: Significantly reduced maintenance footprint vs. many separate apps
  • Multi-tenant: separate jurisdictions do not need separate apps

Features​

  • Allow SAML integrations to OBRC AD and potentially for other jurisdictions
  • Utilize 3rd Fork Role Catalog to simplify permissions and grants
  • Passkey/WebAuthn support?

Propose subsuming all functionality into Smiling Hill and dropping the following apps. Research what functionality of these is still useful and how it actually should work.

  • This documentation site
  • BMS 1 Configurator
  • BMS 2
  • Oregon Green System
  • SF Purple System
  • SF Management

Proposing tie-ins to or further research on the following apps.

  • OOMS
  • Dropbox
  • Paypal Hyperwallet Portal — currently connected from SF Purple only
  • SalesForce — currently only Oregon, except for SF support emails
  • ADP Portal — time clock for employees, may not be connected to anything

Backstory​

I’ve been talking a lot with Dilan and others and I propose that we write one single web app from scratch to replace all of BMS Configurator, BMS 2, Green system, Purple system and SF Manager, and obviate the need for any specific Iowa systems in the process.

The bad news is that BMS 2, which Dilan’s team and the redemption centers appear to use for most of their jobs at OBRC, is based on very old tech (Angular 1) and is out of security support, and Google offers no path forward to any modern technology… we kind of need to do something. Beyond that, we can improve the efficiency for Dilan’s team by fixing a few really silly things that exist in the current systems. Finally, this work is a pre-requisite for proper implementation of Oregon Account Status, in order to provide customer service the views they need into the status changes and the ability to change those statuses when necessary.