Skip to content

[FEATURE] Add Payout Report Generation Functionality #3787

@VenuMadhav2541

Description

@VenuMadhav2541

Feature Description

In my use-case, I need the ability to generate comprehensive reports for payout transactions to match the existing functionality available for payments and refunds. Currently, users can generate reports for payments and refunds through the GenerateReport component, but this capability is missing for payouts, creating an inconsistent user experience.

Current State:

  • Payment reports: Available
  • Refund reports: Available
  • Payout reports: Missing

The feature should follow the same architectural patterns and UI/UX design as existing payment and refund reports, ensuring seamless integration with the current dashboard workflow.

Possible Implementation

The implementation should leverage existing components and patterns already established in the codebase:

Technical Approach:

  • Integrate the existing GenerateReport component with PAYOUT_REPORT entity in src/screens/Payouts/PayoutsList.res
  • Add conditional rendering based on existing feature flags (generateReport and email)
  • Follow the same implementation pattern used in:
    • src/screens/Transaction/Order/Orders.res (payment reports)
    • src/screens/Transaction/Refunds/Refund.res (refund reports)

UI Implementation:

  • Position report generation button in the payouts list header section
  • Ensure button appears when generateReport && email && payoutData->Array.length > 0 conditions are met
  • Maintain consistent styling and interaction patterns with existing reports

Code Changes Required:

  1. Add <GenerateReport entityName={V1(PAYOUT_REPORT)} /> component to PayoutsList.res
  2. Wrap with appropriate conditional rendering (<RenderIf condition={...}>)
  3. Ensure proper integration with existing payout filters and data flow

This approach minimizes development effort by reusing existing components while maintaining consistency across the platform.

Have you spent some time checking if this feature request has been raised before?

  • I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

Are you willing to submit a PR?

None

Metadata

Metadata

Labels

C-featureCategory: Feature request or enhancement

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions