A little game inspired by the devshop game that I saw here a while ago. You will work as a manager to manage the projects, teams and try to survive in 60 days. Happy holidays!
Thanks. The project is built mainly to solve my own problem that I often receive requests from the business side that they wanna access the data in the production system (We use different RDMS and Elasticsearch) so they can generate some simple charts in Excel and display to the customers. The request is not difficult but we just don't have a system for that. Since then, I have been trying different BI solutions like Power BI, Kibana and some other open source tools. They are either too complicated to setup/use or the license/fee is not friendly enough to me. That's why I build Poli. I want it to be more focusing on easy to use, having an open license and the developer can use SQL to build reports easily for the end users or embed the reports in their systems.
The UI is not configurable at this moment. You can embed the full screen view in an <iframe> and then adjust URL parameters to select which report to load.
The main motivation behind the project is that I'd like to have an easy-to-use SQL to Dashboard web application that I can use to solve my own problem. I did try search and use existing BI tools first but found that they are either too complicated to setup/use or the license/fee is not friendly enough. I believe they are designed for more advanced user cases for a good reason and don't seem to suit my simpler needs. Thy's why I build Poli. Yes, I am the solo developer on this project.
Thanks. If you are talking about those three Slicers (User, Product, Year) in the Slicer & Charts screenshot, they are dynamic in a way that the values displayed are queried from the database but I don't think they do the same thing as jsonform.
Maybe I misunderstand your left side panel. I thought it's related to the object (e.g. a specific chart) that is selected but looking at it again it seems to be related to the entire dashboard.
I was not referring to the form values but to the structure of the form - I just thought the different object types (chart, table) don't have static forms behind but dynamic ones. In your case, as far as I can tell, dynamic forms wouldn't make much sense as your form objects are only textboxes, checkboxes and selection boxes - also you don't have too many different objects to configure. Doesn't matter - was just wondering.
But really a great application! I'm working on a similar platform but not open source and with focus on data generation/collection instead of reporting.
It will depend on the size of the grid, number of positions on one level and number of robots. For fast movers, autostore can prepare those products and bring them to a few of the top levels when users are not actively picking or doing putaway. When the picking starts, those robots can get accessed to fast movers more quickly.
For maintenance, there is an extra area outside the grid where you can move the robot out of the grid to do some maintenance work on it without affecting the rest of the system.