How to use .Net dll in PEGA
We have a requirement to show a Excel report with multiple sheets and graphs incorporated in it which requires Macros to be enabled. legacy system is built on .net and it generates Excel with multiple sheets with graphs in it by using .dll. my requirement is to implement that excel in PEGA. Can we do it in PEGA? if not how can we integrate with it to use the .net dll file.
As per my understanding you want to parse the generate Excel in Pega.
Have you tried using OOB MSOParseExcelFile method? This take in parameter:
FSFFileName : Name and Location of the uploaded excel file.
TemplateRFB: Name of the uploaded binary file, it should follow <Directory name>!<Rule Name>!<extension>
MSOParseExcelFile method only reads .xls files.
https://collaborate.pega.com/question/unable-read-data-excel-sheet-when-file-type-xls-pega-86
MSOPaseExcelFile method is implemented using Apache POI jar, you want to check if there is any API to suffice your use case to parse multiple tabs/sheet:
Pfizer
IN
Hi Aditya,
Many thanks for the inputs but I want to generate excel with multiple tabs in PEGA.
I am aware of export to excel with 1 sheet but not sure how we can do it for multiple sheets.
In current system they are using .net dll to generate the excel, can we make use of it to generate the excel from PEGA?
Regards,
Vinay
Updated: 10 Feb 2016 0:23 EST
Process 360
IN
Hi Vinay,
You can generate an excel file using MSOGenerateExcelFile activity (the data from pega can be populated in to multiple tabs). Look at the references to this activity to understand on building the template excel file.
Pegasystems Inc.
US
Hi Vinay,
I understand that you want to reuse the .Net dll because the coding is already done and if integrated will produce the same end results. That is good reuse.
Couple of questions for you.
Where does the .NET DLL get the contents for the output of the excel content? Are the inputs provided to public functions defined in the DLL? Will the inputs have to come from contents in PRPC now?
Is this DLL actually running in macro code within the Excel document?
How do users access this Excel file now? Are they accessing via a browser to a .NET web application?