There is a limit in the dashboard object size due to certain performance issues. Sometimes users need a very big and rich dasboard visualization, which may lead to excceding this limit.

In this cases, some optimization trick maybe used. Following are the examples of such extensive dashboard graphics:

Along the raw of ~60 furnaces, a process state needed to be shown in the furnace place, from both sides, which means ~120 graphical objects.

There is an array of burners inside the furnace, each of the burner requires a set of binary indicators, which require a huge amount of visualization elements.

The solution was to pack all the elements into one string object, with each character reflecting the state of the respective process object.