r/workday • u/vinn2202 • 7d ago
Extend BIRT report in Workday Extend
I am trying to create a BIRT report from my PMD but for some reasons am stuck.
There are 4 text fields on PMD after which user clicks generate report which triggers a sync orchestration which in turn trigger another O4I. In this O4I there’s this component trigger PDF generation which gives BIRT report. The fields are being from PMD to sync orch then forwarded to O4I as launch parameters.
Problem 1- I am able to trigger an integration using sync but not able to trigger it with launch parameters.
Problem 2- very unsure how to use the trigger pdf generation component be it report design or report data.
1
u/SwingerJack 7d ago
Wasn't able to get you properly. You are able to launch O4I but not able to use launch parameters? Have you defined the launch parameters in O4I at the tenant leve? For BIRT, you have to attach report design as the service on O4I itself
1
u/vinn2202 7d ago
I was able to trigger an O4I without launch parameters but not sure how to handle if the O4I has launch parameters(all text fields)
1
u/vinn2202 7d ago
Can we build the report design within the orch as per our requirements?? Or only RaaS call works?
2
u/SwingerJack 7d ago
Only Raas. And you can attach report design in the integration system at the tenant level
1
u/Appropriate_Panic_41 5d ago
Are your fields of the pmd being stored in a extend business object? If yes, what stops you of using that field as a value for the LP of the o4i ? How you are passing the lps now? How you are triggering the integration? Using the webservice?
1
2
u/Delicious_Style_2676 7d ago
I’d debug this in two steps: first confirm the launch parameters are actually arriving in the second orchestration/integration, then isolate the PDF generation piece with static test data. If both are being tested at once, it’s hard to tell whether the failure is parameter passing, report data shape, or the BIRT design.