In Workday, the following report types can be exposed and called as web services for integrations:
1) Report-as-a-Service (RaaS) Reports
Purpose: Designed for API-based consumption.
Usage: Scheduled or on-demand data delivery (e.g., nightly payroll feeds).
Methods:
Launch_Report (SOAP/REST)
Supports XML, JSON, CSV outputs.
2) Advanced Reports
Includes:
Matrix Reports (flattened to XML).
Composite Reports (combined datasets).
Trending Reports (historical data).
Method: Get_Report (SOAP).
3) Search Reports
Simple tabular data (e.g., employee lists).
Methods:
Composite Reports (combined datasets).
Trending Reports (historical data).
Method: Get_Report (SOAP).
3) Search Reports
Simple tabular data (e.g., employee lists).
Methods:
Get_Report (SOAP).
RaaS (Launch_Report) if enabled.
4) BIRT Reports
Purpose: Formatted documents (PDF/HTML).
Method: Get_BIRT_Report (SOAP).
Example: Pay stubs, tax forms.
5) Analytics/Embedded Reports
RaaS (Launch_Report) if enabled.
4) BIRT Reports
Purpose: Formatted documents (PDF/HTML).
Method: Get_BIRT_Report (SOAP).
Example: Pay stubs, tax forms.
5) Analytics/Embedded Reports
Purpose: Visual/tabular analytics.
Method: Analytics REST API.
Method: Analytics REST API.
Key Validation Points (Interviewer Expects)
✅ "Available as Web Service" must be enabled in report properties.
✅ Integration user needs "Report Web Service" permissions.
✅ Matrix Reports work but output flattened XML (not native hierarchy).
Example Use Case (Bonus Points)
"In my project, I used RaaS to sync an Advanced Report (Employee Compensation) to SAP via Launch_Report. The report was scheduled nightly in XML format, filtered by active employees only."
Common Pitfalls to Avoid
❌ Saying "All reports can be web services" (only enabled ones).
❌ Forgetting BIRT requires Get_BIRT_Report, not Get_Report.
Final Tip:
"Always verify the report’s ‘Available as Web Service’ checkbox and test in the Web Services Test Form before integration."
✅ Integration user needs "Report Web Service" permissions.
✅ Matrix Reports work but output flattened XML (not native hierarchy).
Example Use Case (Bonus Points)
"In my project, I used RaaS to sync an Advanced Report (Employee Compensation) to SAP via Launch_Report. The report was scheduled nightly in XML format, filtered by active employees only."
Common Pitfalls to Avoid
❌ Saying "All reports can be web services" (only enabled ones).
❌ Forgetting BIRT requires Get_BIRT_Report, not Get_Report.
Final Tip:
"Always verify the report’s ‘Available as Web Service’ checkbox and test in the Web Services Test Form before integration."
No comments:
Post a Comment