Skip to main content

Release 1.7.0

Features:

  • WICORE-309 - Analytics MS
    Introduced a dedicated Analytics Microservice to handle reporting and data analysis tasks across the system.
    • WICORE-310 - Main architecture
      Established the core architectural framework for the analytics solution, setting the stage for all related components.
    • WICORE-417 - Frontend. Buckets analytics tab implementation on MFE
      Developed and integrated a Buckets analytics tab in the micro-frontend environment, enabling users to view bucket-related metrics.
    • WICORE-416 - Frontend. Transactions by PS - Completed (Diagram) Days + Month
      Created a visual diagram to display completed transactions by Payment Service over both daily and monthly periods.
    • WICORE-414 - Frontend. Average deposit by FTD and STD monthly
      Implemented a component that displays the average deposit amounts by FTD and STD on a monthly basis.
    • WICORE-413 - Frontend. Total by Month (All PS) - Completed / Declined / Pending - Daily / Monthly
      Developed charts that show total transactions per month, broken down by status (Completed, Declined, Pending) for both daily and monthly views.
    • WICORE-412 - Frontend. Withdrawal (Daily / Monthly)
      Implemented analytics views for withdrawal data, allowing users to switch between daily and monthly intervals.
    • WICORE-411 - Frontend. Buckets (Diagram) Month! Registration
      Designed a monthly diagram for bucket analytics specifically tailored for the registration context.
    • WICORE-410 - Frontend. Clients (Diagram) Month! Registration
      Created a monthly diagram view for client analytics within the registration module to enhance data visualization.
    • WICORE-406 - Backend. Move resolveBucketAnalytics to analytics service
      Refactored the code by moving the resolveBucketAnalytics function into the Analytics service for improved modularity.
    • WICORE-404 - Backend. Move Bucket Analytics by source to MS analytics
      Shifted the Bucket Analytics by source functionality into the Analytics Microservice to centralize analytics processing.
    • WICORE-399 - MFE architecture
      Established the micro-frontend (MFE) architecture necessary to support the new analytics modules and ensure scalability.
    • WICORE-392 - Backend. Monthly turnover by all completed transactions - widget
      Developed a backend widget that calculates and displays monthly turnover based on all completed transactions.
    • WICORE-391 - Backend. Average deposit by FTD and STD monthly
      Implemented backend logic to compute and deliver average deposit values by FTD and STD on a monthly basis.
    • WICORE-316 - Backend. Total by Month (All PS) - Completed / Declined / Pending - Daily / Monthly
      Developed endpoints that aggregate transaction data by month, categorized by status, for both daily and monthly views.
    • WICORE-315 - Backend. Withdrawal (Daily / Monthly)
      Implemented backend support to process and provide withdrawal data for daily and monthly intervals.
    • WICORE-314 - Backend. Transactions by PS - Completed (Diagram) Days + Month
      Created backend logic to fetch and format transaction data by Payment Service for diagram representations over daily and monthly periods.
    • WICORE-313 - Backend. Buckets (Diagram) Month! Registration
      Implemented functionality to generate monthly bucket diagrams in the registration context on the backend.
    • WICORE-311 - Backend. Clients (Diagram) Month! Registration
      Developed backend support for generating monthly client diagrams within the registration module, enhancing reporting capabilities.
  • WICORE-390 - Translations solution

    • This update introduces an essential Translations service that streamlines the management of translations and texts across the entire system. Key highlights include:

      • Central CRM Manager:

        • A primary CRM Manager now serves as the main hub for translations.
        • Users can add, edit, or delete translations and texts that are used throughout the system and on various websites.
        • For the Client Area, translations and texts are organized into groups, ensuring that each group of websites receives the appropriate localized content.

      • Client CRM Capabilities:
        Client CRMs function as consumers of the central Translations service and include the following features:

        1. Sync:

          • A dedicated "Sync" button allows client CRM users to synchronize translations and texts from the central CRM Manager.
          • In the Client Area, if a client CRM is set up with a specific group at launch, all translations and texts for that group are automatically synchronized.
          • If no group is specified, no translations will be synced automatically, giving users the option to manually add the necessary content.

        2. Redefine:

          • Although client CRMs do not allow direct addition or deletion of translations, users can override existing translations with custom ones.
          • When a custom translation is provided, it takes precedence over the default version.
          • If the "Sync" button is used while custom (redefined) translations exist, the main translations are updated, but the custom overrides remain intact. Removal of these custom translations is controlled solely by the client CRM user.

      This solution ensures that translations are centrally managed yet flexible enough to accommodate custom requirements for client-specific deployments.

Back to top