lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] tasks 2007: bug 105595: Print group roster with some calculati


From: Greg Chicares
Subject: Re: [lmi] tasks 2007: bug 105595: Print group roster with some calculation results
Date: Wed, 21 Feb 2007 18:29:05 +0000
User-agent: Thunderbird 1.5.0.4 (Windows/20060516)

On 2007-2-16 12:24 UTC, Evgeniy Tarassov wrote:
> Print group roster with some calculation results
> http://savannah.nongnu.org/support/?105595
>    Print summary of census input, and selected calculation results,
>    with one line per life. Brokers want a roster showing everyone's
>    specified amount or premium when those amounts are determined by a
>    strategy ( e.g., seven-pay) or by a solve (e.g., level premium
>    through retirement to fund some income objective). This useful
>    summary information isn't readily available by other means. It's
>    not part of the illustration proper: it could be many pages for a
>    thousand-life group, so a separate, optional report on the side is
>    better. Typically, it would show age and gender, but other columns
>    may be needed, and ideally they should be configurable.
> 
> If i understand this task correctly it would consist of a part that
> will generate a report data and will be able to export it (in a form
> of XML file?). Plus an xsl template (or a family, exactly as for
> calculation summary) to generate output suitable for different media,
> like html (for presenting it to the user in a separate window and for
> printing), tab delimited (for exporting into a spreadsheet), and maybe
> xsl-fo for pdf generation. Please correct me if i'm getting a wrong
> picture. :)

You've got the right picture. It's just another type of report, and
I think we were wise to choose xslt as our preferred technology for
reports. Using xslt, we easily get all the flexibility you mention.
I see no reason to treat this report otherwise.

This is different from other reports in a few ways:

(1) It would be run at the "case" level. To our salespeople, a
"case" is a set of individuals who have similar insurance policies
and are related to each other in some way--typically, they'd be
employees of the same employer. In lmi, a '.cns' file embodies a
"case". It would make no sense to produce this report for a single
individual. The command to produce it would appear on the "Census"
menu that's available when a '.cns' file is loaded.

(2) It is not required by law or regulation, and therefore it
wouldn't need xsl-fo.

(3) It may use some data that are not currently available in our
largest "master" data set, which therefore may need to be expanded.
We'll have to study the problem more to know that for sure. That's
not a serious obstacle: the "ledger" objects that provide the data
we use for all reports already contain most of what we'd need, and
any new data that we might need to add would be similar to what
we've already got.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]