DevTools

Abishek, • tri

This was built as a workaround to save lots of time and that's about it.

The DevTools was a shortcut to some of the features offered by the admin console in TRIRIGA. I built a set of classes that did a part of the functions available on the admin console. Put them into a classloader, built some workflows, took help (a lot, actually!) from a UX Developer and published it as a perceptive app.

The current version of DevTools can -

  1. Clear cache
  2. Download any type of logs
  3. Download Data and Label translation files (after they've been exported from TRIRIGA's globalization manager)
  4. Download large OM Packages
  5. Generate an excel report of all items in an OM Package, with the type of object their names
  6. Unlock users who've been locked out of TRIRIGA
  7. Get some system stats like Workflow events pending and Workflow instances recorded

I really wanted to build a workflow instance management toolset into it but never worked out.

Usage

So, for most customers, the servers are handled by a specific team called an SRE team. And some times - they handle the admin console too, just so that the developers don't mess things up.

DevTools was going to fly over this team to allow server safe functions present in the admin console to be performed by the developers themselves. This saved a lot of effort and time for both the developers and the SRE teams.