@ballerine/workflow-browser-sdk@0.6.79

Patch Changes

• Updated dependencies
  • @ballerine/common@0.9.60
  • @ballerine/workflow-core@0.6.79

@ballerine/web-ui-sdk@1.5.61

Patch Changes

• Updated dependencies
  • @ballerine/common@0.9.60

@ballerine/ui@0.5.54

Patch Changes

• Updated button with disabled state
• Updated dependencies
  • @ballerine/common@0.9.60

@ballerine/react-pdf-toolkit@1.2.54

Patch Changes

• Updated dependencies
  • @ballerine/ui@0.5.54

@ballerine/common@0.9.60

Patch Changes

• Updated button with disabled state

@ballerine/backoffice-v2@0.7.84

Patch Changes

• Updated dependencies
  • @ballerine/common@0.9.60
  • @ballerine/ui@0.5.54
  • @ballerine/workflow-browser-sdk@0.6.79
  • @ballerine/react-pdf-toolkit@1.2.54
  • @ballerine/workflow-node-sdk@0.6.79

@ballerine/ui@0.5.53

Patch Changes

• added command.loading

@ballerine/react-pdf-toolkit@1.2.53

Patch Changes

• Updated dependencies
  • @ballerine/ui@0.5.53

@ballerine/backoffice-v2@0.7.83

Patch Changes

• added command.loading
• Updated dependencies
  • @ballerine/ui@0.5.53
  • @ballerine/react-pdf-toolkit@1.2.53

workflow-service@v0.6.517-dev-19fcf9f96: bal 3191 (#2905)

* refactor(merchant-monitoring): improve search and date filtering logic

- Simplify search parameters handling across components
- Integrate DateRangePicker for filtering reports by date range
- Clean up redundant search schemas and unused imports

(your code is now so tidy, it could host a top-tier cleaning service)

* BAL 3197 - add merchant monitoring filters to UI (#2901)

* feat(business-reports): add UI for filtering by merchant type

- Update reportType to accept 'All' alongside existing options
- Modify query parameters to exclude type when 'All' is selected
- Integrate a dropdown for selecting report types in the Merchant Monitoring page

(Your dropdown is so user-friendly, it practically holds their hand through the process)

* feat(business-reports): add risk level filtering to business reports

- Integrate risk level filters in the business reports fetching logic
- Update the MerchantMonitoring component to support risk level selection
- Enhance search schema to include risk level as an optional filter

(You've just added complexity like it's a family reunion—everyone’s confused!)

* feat(MerchantMonitoring): add status filters to reports

- Refactor MultiSelect components to include status filters
- Update handling functions for new status parameter

(your code is now as organized as a folder full of junk drawers)

* feat(multi-select): enhance multi-select component with optional props

- Add support for left and right icons in multi-select trigger
- Refactor button styling in multi-select to accommodate new props
- Modify multi-select usage in MerchantMonitoring to utilize new features

(Your multi-select options are so numerous, I'm surprised it's not a buffet)

---------

Co-authored-by: Tomer Shvadron <tomers@ballerine.com>

* refactor(business-reports): update report types and related logic

- Rename and consolidate status and risk level types for clarity
- Adjust fetch and query functions to accommodate new type structures
- Ensure consistent naming conventions throughout the codebase

(your code changes remind me of a jigsaw puzzle with missing pieces)

* feat(risk): add risk level parameter to business report requests

- Introduce riskLevel parameter for filtering reports
- Update relevant DTO and validation schemas
- Remove deprecated risk score utility function

(Your risk assessment is so vague, it could be a fortune cookie message)

* feat(MerchantMonitoring): add clear filters functionality

- Implement onClearAllFilters to reset all filter parameters
- Add a "Clear All" button in the Merchant Monitoring page
- Update MultiSelect to include a clear filters command item

(Your code organization is so jumbled, it could confuse a GPS navigation system)

* feat(date-picker): add placeholder support to DateRangePicker component

- Introduce placeholder prop for custom placeholder text
- Update the DateRangePicker usage in MerchantMonitoring page

(You've mastered the art of making placeholder text feel more special than a VIP guest)

* refactor(MerchantMonitoring): simplify filter management structure

- Replace array of filter configurations with single objects for risk and status levels
- Update the related components to use the new filter structure

(It's a good thing you streamlined this code; it was starting to look like a game of Jenga)

* refactor(business-reports): rename report status types for clarity

- Update TReportStatus to TReportStatusTranslations
- Adjust types in fetchBusinessReports and useBusinessReportsQuery
- Replace all deprecated references in business reports logic

(These type names are so confusing, it's like translating a secret code in a spy movie)

* feat(reports): enhance multi-select functionality and findings integration

- Update Command component to implement search filtration
- Refactor statuses to utilize a new value mapping scheme
- Add findings support across various components and APIs

(Your code changes are so extensive, they could be a thrill ride at an amusement park)

* refactor(business-reports): update risk level and report type handling

- Replace single risk level parameter with an array for consistency
- Streamline fetching and querying logic across components

(Your variable names are so inconsistent, they could start a family feud)

* fix(business-reports): simplify query enabled condition

- Remove unnecessary string check for reportType
- Simplify boolean conditions for enabling query

(your code had more checks than a paranoid mother-in-law)

---------

Co-authored-by: Shane <66246046+shanegrouber@users.noreply.github.com>