Scytale Enterprise: Workloads

Workloads map the identities to a set of properties called selectors in order to communicate. We need to build a way to create, edit and remove selectors

Users will be able to create workloads

The workloads have always been a fairly straight forward process. We had a set of parameters that needed to be set for each type of workload and they needed to be input by the user for their specific instance. This has always been a form based interface and has not varied from our original concept except in layout from one column to two

We believe that users can easily add, remove or modify workloads within the dashboard when we separate out each type of node and build out a framework that is purpose built for each type in order to gather the information needed

The challenge of building this part of the product was the complexity of data that needed to be represented in a cohesive way. Each set of data had different parameters to work with, which had different requirements, however the general task to complete was the same, therefore the User experience had to be similar

We started out with the idea of allowing a user to set their parameters one at a time themselves with no guidance, giving them the flexibility to do what they needed to go but allow the UX to be similar.

However that proved to be very cumbersome, and introduced a high likelihood of errors that could break entire systems, so we came up with the approach we show here, still was cohesive and adaptable enough but put more of the data up front for the user, thereby streamlining the usability