hi,
My assumption is - for jasper printing we need
- process (runtime) - iD has for each window and report based printing 1 dedicated - ATM jasper call this process - there is a ticket for fix.
- print format is for me as placeholder - instead process right place jasper reference, attachment
- jasper itself define: data-source, layout - it represents the print format
changes
- add new window Tenant level Jasper processes - need help, how to set properly data access level - it is system now.
- we need to add jasperformat field to ad_printformat - allow upload tenant wide the jasper definition.
- we need to add toolbar button to allow upload jasper formats, which run java class validate jasper definition. can be custom each implementer would add own rules. (disallow insert, from only main table, etc.)
- change the code, support for printformat-less jasper printing and print format with jasper printing
- make some changes on print format when it is jasper based - eg no items, do not generate, remove them or hide, need serious proposal.
Our priorities are
A.don't define hundreds of processes, the fact process != print-format it is not legacy not being logical
B. move jasper definitions to print format itself system or tenant wide
C. allow print printformat-less jaspers printing and print format based
D. allow define tenant wide processes - then select them on format or in menu..
norbert