Rukovoditel Support Forum

What is not being highlighted here is that if you are currently using Ruko 2.7.2, you will need to install EACH intermediate release/update (along with EACH corresponding Extension, if you are using the Extension) in incremental steps, to bring you up to the latest version of Ruko. You can't simply ...

Would this additional reporting facility also require a purchased licence for the Jasper reporting software?

Even if the item page could be set replicate the edit page (and tabs) layout, that would be a great advancement.

I was also disappointed in what I thought was going to appear in Ruko 3.2. A wysiwyg report designer would have been a game-changer, although I can appreciate the complexity involved in creating such a beast. Reporting/output appears to be a somewhat weak spot in all web-based software, which is a s...

What are you exporting to, Edin?
Most data exports are un-paginated, but having the ability to "massage" the data using SQL will be very useful.

That makes sense. The way you have set it up certainly gives the experienced user more power and flexibility, but not something the average "super user" or manager could use ... unless they have a few examples to clone and adapt new reports from.

Hi Sergey. For some reason, I thought the report designer module was going to be an interface to the open-source iReport software?

Sadly, there is no way to clone a complete entity/table, in one easy step. Cloning has to be done at field-level, AFTER a new entity has been created. As you are probably already aware, Ruko tables and individual fields are referenced internally by a simple number ... which is why you can user-label...

It is important to understand the purpose of Rukovoditel. Ruko gives you a box of tools ... a box of very flexible tools. But that's it! It's then up to the user to create their own custom application. Sergey and his team are not here to do that work, gratis. You might look at the various templates ...

The screen shot below will best explain, but simply allow an entity's info page to mimic the edit page format. Obviously the blue field edit boxes shown would not be there ... just the data.

(Please note: my edit page format has been heavily customized, to my preference).