End user report inheritance?
Hi all,
Have you ever thought about end user report inheritance?
I mean a centralized way for a user to modify common part of his/her
reports.
Suppose that a user has an hundred of reports which all show some
information like address, company name and logo and so on.
But it can be also a company "look and feel" or layout.
If one of this information/layout changes she/he has to go on each
report to fix it.
In a OO language this would be solved with a properly designed class
hierarchy (and then modifying an ancestor class and rebuild the
application), but what about end-user reports?
It should be something like a common enterprise(or maybe user?)-level
template, don't you think so?
Thanks in advance
Bye
Nicola
Have you ever thought about end user report inheritance?
I mean a centralized way for a user to modify common part of his/her
reports.
Suppose that a user has an hundred of reports which all show some
information like address, company name and logo and so on.
But it can be also a company "look and feel" or layout.
If one of this information/layout changes she/he has to go on each
report to fix it.
In a OO language this would be solved with a properly designed class
hierarchy (and then modifying an ancestor class and rebuild the
application), but what about end-user reports?
It should be something like a common enterprise(or maybe user?)-level
template, don't you think so?
Thanks in advance
Bye
Nicola
This discussion has been closed.
Comments
Template inheritance is something we have been thinking about for some time
now. Thanks for the suggestion.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com