Development Diary - "cloudMAX" - Part 3 - with small steps on the way to a finished product

It's time again for a little update! The third part of the developer diary of our cloud application with the project name "cloudmax" will this time be about the crucial subtleties.

Short disclaimer: Of course, all of this is not quite finished and still in development! Therefore some visual and functional details of the application may differ from the final product.

Now that this is out of the way, let's move on to two features that could pass for a small detail, but are ultimately highly relevant.

Copies and duplicates

In the development process, this feature interestingly appeared quite late - which sounds kind of weird, I know. Something as standard as copying an entry? In the end the copy function found its way into the project and is partly already implemented.

Let's take a look at two examples on how this got implemented:

Copy from list view

Copy from list view
Copy from list view

The list view in cloudMAX is the overview of data in a tabular view. You can directly inspect important info from the overview without having to open a dataset. On the right side there are three buttons:

  • The pen, which opens the dataset for editing.
  • The copy icon, which opens a new form with the info from the selected dataset.
  • The trash can icon, which deletes the record (you will be asked if you really want to delete the record).

If you now click on the copy icon, a form opens to create a new record, which is already filled with the same information as the selected record.

This way, a lot of similar records can be created in a very short time - which on the one hand simplifies the initial configuration and on the other hand makes the creation of new records with similar data more efficient.

Copy data from open dataset for a new dataset

Copy from dataset
Copy from dataset

If you now have a dataset open that you have already worked on or that you want to create, you can click on Create and Copy or Save and Copy to create/save the dataset and open a new form with already filled out fields with the data from the previous dataset.

As you can see, this is not a reinvention of the wheel, but a convenient feature to allow the user to work efficiently and relaxed.

The global property filter - filter by location

This feature needs some introduction: Currently the hierarchy structure looks like this:

Organization => Property => Function Room => Display

Since the organization as the top entity is bound by your account, the properties are the next object in the hierarchy. Normally the property describes a building - but we don't want to tell you what a property is. You could just as well use the floors of a building as different properties - not a bad idea if you only have to manage one building anyway.

Well, since rooms are now subordinated to properties, we implemented a global filter located in the header. You always see the selected property and are also able to show all properties.

This helps users who have to administrate several of these units. And even if you have only one building, you could just use following divisions for choosing your properties:

  • Floors
  • Building wings
  • Cardinal Directions
  • Colors of the walls?
  • etc.

In the end, we simply offer you a possibility of subdivision. It should be mentioned that the rights management in your organization also depends on the properties. This means that if you use the properties smart, you can also have a smart user rights policy.

Concluding

That's it again with this entry. Even if it may come across a bit abstract and cryptic - who will blame you with all the abstraction here - it will be all the easier to use - I can promise you that already!

Next week, by the way, is also about places and buildings and that is: "The perfect place for your signage screen".

Thanks for tuning in!

Until then! Don't be a stranger!

Francesco Coenen

28.06.2021