Configuration Viewer R4: Demo

I’ve been talking about demoing the application to my head of department for a while now, but hadn’t found the time until now. Work is busy, and I’m a procrastinator.

The demo went pretty well, with the overall feedback being the application will be useful and is heading in the right direction already, with plenty of encouragement to finish the planned features.

There were specific bits of feedback around…

Form grouping and order

Filters that show form information are currently displayed in the order that they are defined in the underlying data (yaml/json). In order for testers to more easily validate form orders, the filters should show them in the grouping and order they will be displayed in the application.

This could add a reasonable amount of complexity to the app, with different orders being necessary on a per filter basis, but I’m hoping it shouldn’t be too bad.

Extra filters

This is one that I pre-emptively mentioned as the demo started. The old Java based configuration viewer (that has no interface outside of a Java project) has more filters than appear in the new configuration viewer, so I need to add those additional filters in. Things like which fields appear in data that we send back to the client in various different ways.

This isn’t going to be a complex thing to do, but it may be monotonous and time consuming.

I’ll need to figure out how many filters are currently missing, and whether any of them need behaviour outside of what I’ve already implemented.

So that’s where I’m at right now. Demoed and moving beyond the prototype phase into a fully functional tool that the team can use to make life easier.

Feature image: Photo by Nicolas Tissot on Unsplash

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Blog at

Up ↑

%d bloggers like this: