Report in IREPORT - STATUS

Question

Good morning , I need to change a report in IREPORT that works today as well:

Currently the field works like this:

    (Boolean)
    $F{documentoVigente} ? "VIGENTE" : "VENCIDO"

I have a text called $F{documentVigent} passing an Expression class (java String)

I need my report to be generated like this today:

        if $F{dataVencimento} = $F{CurrentDate} : "VIGENTE"
        if else $F{dataVencimento} < $F{CurrentDate} : "VENCIDO"
        else : "VENCENDO" > a data do dia 

I have a class that references this report:

public  class  RepDtoReport  implement Serizable {

private String nomeRepresentante;
private Integer cartaoAssinatura;
private String descricaoGrupo;
private String codigoPessoa;
private String descricaoCargo;
private String descricaoDocumento;
private Date dataAtualizacao;

private  Date   dataVencimento;

private boolean documentoVigente;


}getts e setters}

public boolean is documentoVigente() {
return documentoVigente;
}

public void setDocumentoVigente (final boolean documentoVigente){
this.documentoVigente = documentoVigente;
}

public  Date getDataVencimento() {
return dataVencimento;
}

public void setDocumentoVigente (final Date dataVencimento ){
this.dataVencimento = dataVencimento;
}

Today he’s like this:

I can only do it in the ireport ?

Answer 1

I have a practice that I love to use. In reporting, I like to separate data processing for the database and IO for the application. Thinking in this sense, when you make a query in the database and bring an N of records, when offering it to the application layer the same need to iterate in each of the records to apply the rule.

Example: A query that returns 100 records ends up processing these same 100 to get the desired result applying the rules of the report.

My tip for you is to analyze the feasibility of using a VIEW already with all the necessary rules for your report. Obviously, App rules have their burdens and bonuses, but there is a huge gain in processing that can be an advantage, not to mention the ease of implementing in any Report tool.