Whether you choose single or multiple report bursting, eventually you will want to deliver the results to your users, and if you are delivering a custom application solution, that means understanding the object model around publications.
A publication object appears in a BOE folder just like a report does, and like a report, it too has historical instances. But whereas a report instance represents a snapshot of the report with data, a publication instance is a container that further holds (you guessed it) the report instances themselves.
The great thing about BOE publication architecture is that the report instances held in a publication instance are automatically filtered to the report instances the currently logged in user has been “bursted.” In other words, it makes no difference if a user has rights to the folder in which the publication resides; he/she must have been named (or at least the user group to which he/she belongs must have been named) as a burst recipient in the publication.
Here is a snippet of the code that will work the same for all recipients of a publication, selecting the report instance specific for the recipient automatically:
//This gets the publication by name
String query = “Select SI_ID, SI_KIND From CI_INFOOBJECTS ” + “Where SI_NAME='” + publicationName + “‘”;
IInfoObjects ioPublications = iStore.query(query);
if(ioPublications.size()==0)
{
String errorMsg = “Sorry! There is no publication by the name configured (” + publicationName + “)”;
return;
}
Want to obtain the remainder of this code? Do you have more questions? Please visit McManus Consulting to obtain additional information or send us an email. Stay tuned for more tips and tricks!
