v6.1.1
StreamSync Hotfix v6.1.1
StreamSync Hotfix v6.1.1 fixes an issue in the API reconnection process after network instability.Reconnection Fix
In certain situations, StreamSync could not automatically restore the connection to the API after an interruption.With this fix, the service now:- Detects loss of communication;
- Attempts to restore the connection automatically;
- Resumes operation after temporary instability;
- Reduces the need for manual restarts.
Hotfix Benefits
- Greater stability in API communication;
- Automatic recovery after temporary network failures;
- Fewer synchronization interruptions;
- Greater continuity in data processing.
Hotfix Summary
StreamSync v6.1.1 improves the API reconnection mechanism, ensuring greater synchronization stability and continuity after network fluctuations.v6.2.1
API Hotfix v6.2.1
API Hotfix v6.2.1 fixes the behavior when editing the merchandising month in the Budget routine.Budget Fix
The API processing performed when editing the merchandising month of an existing budget has been adjusted.With this fix:- The period can be changed correctly;
- The update is saved and retained after a new query;
- Updated data is made available correctly to integrations;
- The budget editing process is more stable and reliable.
Hotfix Benefits
- Correct operation when editing the merchandising month;
- Proper persistence of changes;
- Greater consistency in Budget data;
- Continuity for integrations that consume the API.
Hotfix Summary
API v6.2.1 restores the correct operation of merchandising month editing, ensuring that changes made to the Budget are processed and stored correctly.v6.2.1
Portal Hotfix v6.2.1
Portal Hotfix v6.2.1 was released to fix the Live feature located in the Real-Time module of the Controller 360 Portal.The update improves the behavior of the “Start” button, ensures that the Live screen is displayed correctly at the end of the configured time, and prevents old information from remaining in the progress grid after the page is refreshed.Fixed Issue
An issue was identified in the Live initialization flow. When the specified time ended, the “Start” button did not correctly transition to the Live screen, interrupting the expected behavior of the feature.In addition, the progress grid could continue displaying information from a previous operation after the screen was refreshed.Adjustments Made
- Fixed the behavior of the “Start” button.
- Adjusted the opening of the Live screen after the configured time ends.
- Implemented clearing of the progress grid after the page is refreshed.
- Fixed the transition between the processing state and the Live display.
- Improved the visual and functional consistency of the routine.
Impact on Users
Users now have a more stable and predictable flow when using Live. When the configured time ends, the screen is displayed correctly and the progress grid does not retain data from previous operations.Recommended Validations
- Start an operation in Real-Time and wait for the configured time to end.
- Confirm that the Live screen opens correctly.
- Check the “Start” button before, during, and after processing.
- Refresh the page and confirm that the progress grid is cleared.
- Perform consecutive operations to verify that previous information does not remain.
- Perform a general validation in Real-Time to identify possible regressions.
Benefits
- Greater stability when using Live.
- Better visual feedback during state changes.
- Removal of outdated information from the progress grid.
- Fewer failures during feature initialization.
- A clearer and more reliable real-time monitoring experience.
v6.3.2
Mobile Hotfix v6.3.2
Mobile Hotfix v6.3.2 includes 2 fixes, focusing on the internationalization of monetary values and the accuracy of Purchase Limit calculations.Monetary Value Formatting
The display of monetary values was fixed according to the language selected in the application.With this adjustment, values now correctly follow the configured regional format, including:- Currency symbol;
- Decimal separators;
- Thousands separators;
- Formatting corresponding to the selected language.
Purchase Limit
The calculations for adjustments and value distribution at merchandising level 2 were fixed.The fix ensures:- Proper distribution of values;
- Correct application of adjustments;
- Greater calculation accuracy;
- Consistency of the information displayed in the application.
Hotfix Benefits
- Monetary values displayed in the correct format;
- A better experience for users of different languages;
- Greater accuracy in the Purchase Limit;
- Greater reliability in distribution by merchandising level.
Hotfix Summary
Mobile v6.3.2 fixes monetary value formatting according to the selected language and improves Purchase Limit adjustment and distribution calculations for merchandising level 2.v6.1.5
Portal Hotfix v6.1.5
Portal Hotfix v6.1.5 includes 4 fixes, focusing on information reliability and the proper operation of Portal filters.Real-Time — Sales by Hour
The values displayed in the Sales by Hour chart tooltip, which were shown in reverse, have been fixed.With this adjustment, each time slot now displays the corresponding information correctly.
Statement Filter
The store filter in the Statements, which displayed an inactive store and duplicated one of the available stores, has been fixed.The filter now displays only active stores, without duplicate records.
Data Entry
The information relating to the date type, which was displayed in reverse in the Data Entry routine, has been fixed.Purchase Limit
The Purchase Limit screen filter update was adjusted, ensuring that information is reloaded correctly after parameters are changed.Hotfix Benefits
- Greater reliability of Real-Time information;
- Correct display of stores in Statements;
- Correct information in Data Entry;
- Better operation of Purchase Limit filters;
- Fewer inconsistencies during analyses.
Hotfix Summary
Portal v6.1.5 fixes inconsistencies in data presentation and filters in the Real-Time, Statements, Data Entry, and Purchase Limit routines, providing a more reliable and stable experience.v6.1.4
Portal Hotfix v6.1.4
Portal Hotfix v6.1.4 includes 2 fixes, focusing on occurrence display and the stability of the Portal’s real-time communication.Occurrence Display
The display of occurrences in the Verify function has been fixed, ensuring that information is loaded and displayed correctly for the user.With this adjustment:- Occurrences are visible again;
- Information verification is clearer;
- The routine displays complete and reliable data.
Connection Stability
A behavior that kept the real-time connection active indefinitely has been removed.The fix improves connection termination and management, avoiding unnecessary resource consumption and possible impacts on Portal performance.Hotfix Benefits
- Correct display of occurrences;
- Greater reliability during verification;
- Better connection management;
- Reduced unnecessary resource consumption;
- Greater Portal stability and performance.
Hotfix Summary
Portal v6.1.4 fixes occurrence display in the Verify function and improves real-time connection management, providing a more stable and reliable experience.v6.1.5
API Hotfix v6.1.5
API Hotfix v6.1.5 fixes an issue in Merchandising Sector records, ensuring that the hierarchical structure is preserved when the status is changed.Merchandising Sector
Previously, when the status of a merchandising sector was changed, its hierarchy was reset, affecting the organization and relationships of the registered structure.With this fix:- The hierarchy remains preserved after the status is changed;
- Merchandising levels retain their relationships;
- The registered structure remains correctly organized;
- Routines that use merchandising sectors receive consistent information.
Benefits of the Fix
- Preservation of the merchandising hierarchy;
- Greater safety when updating records;
- Fewer inconsistencies between levels;
- Continuity of analyses by merchandising sector.
Hotfix Summary
API v6.1.5 prevents the Merchandising Sector hierarchy from being reset when its status is changed, ensuring the integrity of the registered structure and relationships.v6.1.4
API Hotfix v6.1.4
API Hotfix v6.1.4 fixes the submission of the Contribution Margin when exporting the Budget.Budget Export
An issue in which the margin was not sent with the other information during export has been fixed.After this adjustment, the export now:- Sends the calculated margin correctly;
- Maintains consistency with Budget data;
- Displays complete information at the export destination;
- Prevents incomplete or inconsistent analyses.
Benefits of the Fix
- Complete information export;
- Greater data reliability;
- Consistency between the Budget and exported data;
- Greater confidence when analyzing the Contribution Margin.
Hotfix Summary
API v6.1.4 restores margin submission in the Budget export, ensuring complete and consistent information for analysis.v6.1.3
API Hotfix v6.1.3
API Hotfix v6.1.3 includes 6 fixes, focusing on indicator consistency, Budget calculations, and the accuracy of commercial analyses.Contribution Margin
The discrepancy in the Contribution Margin percentage displayed between the following routines has been fixed:- Budget;
- Metrics;
- Commercial Monitoring.
Expense Limit
The basis used to calculate the Expense Limit has been corrected, ensuring greater accuracy in the displayed values and financial planning monitoring.Analysis by Buyer and Merchandising Category
The sales amount displayed in the details by Buyer and Merchandising Category has been corrected for clients configured at level 2.The analysis now correctly considers the merchandising structure defined for the client.Margin and Cost by Store
Budget margin and cost calculations were adjusted to correctly respect the relationship between the store and merchandising sector.Calculation with Zero COGS
The margin adjustment calculation has been fixed for situations in which COGS is zero, preventing incorrect results or inconsistencies during Budget processing.Calculation by Store Group
The Budget calculation by store group has been fixed to process each store’s information individually, ensuring that values are calculated in the correct context.Hotfix Benefits
- Greater consistency between indicators;
- More accurate budget calculations;
- Correct analyses by store and merchandising category;
- Reliable results in scenarios with zero COGS;
- Better calculations for store groups.
Release Summary
API v6.1.3 improves the reliability of calculations and indicators used by Platform360, correcting discrepancies in margin, expense limits, and Budget processing across different store and merchandising sector configurations.v6.1.3
Portal Hotfix v6.1.3
Portal Hotfix v6.1.3 fixes the behavior of the filter used to create and calculate the Budget.Budget Fix
An inconsistency in the Budget routine filter that could prevent or compromise information creation and calculation has been fixed.After this adjustment, the Portal now:- Applies the selected filters correctly;
- Considers the correct context during calculation;
- Generates the Budget using the information corresponding to the selection;
- Maintains greater consistency in the displayed values.
Benefits of the Fix
- Greater reliability in Budget calculations;
- Fewer inconsistencies in values;
- Correct filter operation;
- Continuity of the budget planning process.
Hotfix Summary
Portal v6.1.3 restores the correct operation of filters when creating and calculating the Budget, ensuring greater accuracy and reliability in the generated information.v6.1.2
Portal Hotfix v6.1.2
This release includes 5 fixes, focusing on exporting reports to Excel and making imports from previous periods more flexible.Excel Export Improvements
Exported Reports
Formulas and technical information that should not have been displayed in exported files have been removed.With this adjustment, spreadsheets are clearer, better organized, and more suitable for analysis and sharing.Financial Flow
The export of the Detail Outflows option has been fixed, ensuring that the information is generated correctly in the Excel file.Product Analysis
The Product Analysis export received fixes to:- Report name;
- Information identification;
- Displayed totals;
- Organization of exported data.
Inventory — Loss and Breakage
The totals in the Inventory Analysis — Loss and Breakage export have been fixed, ensuring greater consistency between the data displayed in the Portal and Excel.Importing Previous Periods
Information from previous months can now be imported even when later periods have already been closed.This improvement provides greater flexibility for making retroactive corrections, adjustments, or imports without reopening later accounting periods.Release Benefits
- Clearer and more reliable Excel files;
- Correctly displayed totals;
- Greater consistency between the Portal and exported files;
- Correct details for financial outflows;
- Greater flexibility for retroactive imports.
Release Summary
This release improves the quality of Excel exports across different Portal reports and allows previous months to be imported even when later periods have been closed.v6.3.1
Mobile Hotfix v6.3.1
This fix restores the Generate button in the Purchase Limit routine, allowing planned limits to be calculated and displayed correctly in the application.v6.1.2
API Hotfix v6.1.2
API Hotfix v6.1.2 improves communication stability between the API and the ERP database, reducing failures caused by response timeouts.Improved Communication with the ERP
The timeout for responses from the ERP database has been increased from 5 to 60 seconds.This change allows the API to wait for longer-running operations before interrupting processing, especially in high-volume scenarios or when the integration is slow.Benefits of the Fix
- Fewer response timeout errors;
- Greater stability in ERP-integrated operations;
- Better tolerance for performance fluctuations;
- Lower risk of premature interruptions;
- Greater continuity in information processing.
Note
When the ERP is unavailable or slow, some requests may wait longer before returning an error. This behavior is expected after the adjustment.Hotfix Summary
API v6.1.2 increases the timeout for ERP responses, providing a more stable integration and reducing failures caused by slow communication.v6.1.1
Portal Hotfix v6.1.1
Portal Hotfix v6.1.1 fixes column display issues in Commercial Monitoring, ensuring a more complete and reliable reading of the information.Commercial Monitoring Fix
With some filter combinations, certain important columns were not displayed on the screen.With this fix, the following columns:- Loss;
- Breakage;
- Consumption.
Benefits of the Fix
- Complete view of indicators;
- Greater reliability when reading data;
- Fewer questions about apparently missing information;
- Greater confidence during operational analyses;
- Retention of the context selected in the filters.
Hotfix Summary
Portal v6.1.1 restores the display of the loss, breakage, and consumption columns in Commercial Monitoring, preventing incomplete analyses and improving the reliability of the information presented.v6.1.1
API Hotfix v6.1.1
API Hotfix v6.1.1 fixes a critical issue in cost center allocation in the Managerial Data Entry routine.Cost Center Allocation Fix
The query and formula used to calculate the allocation have been adjusted.The fix ensures:- Correct distribution of values between cost centers;
- Consistent results in Managerial Data Entry;
- Greater reliability of information used in Results Calculation.
Deliveries Completed in the Same Cycle
In addition to the hotfix, the API received the following improvements:- Batch synchronization for large data volumes;
- Support for comparative Managerial and Financial Income Statement reports;
- Improvements to error monitoring and handling;
- New validations in user records;
- Optimization of Budget queries.
Hotfix Summary
API v6.1.1 increases the accuracy of cost center allocation and improves the reliability of managerial data.v6.1.0
API Hotfix v6.1.0
API Release v6.1.0 strengthens technical monitoring, improves the performance of high-volume integrations, and supports the new comparative Results Calculation reports.Monitoring and Traceability
Global exception handling has been implemented to centralize and standardize API error responses.Improvements include:- Integration with Azure Application Insights through OpenTelemetry;
- Generation of a unique
errorIdfor each failure; - Easier location of errors in internal logs;
- Removal of technical information from responses displayed to users;
- Greater security and faster support response.
Batch Synchronization
Integrations for the following records can now be performed in batches:- People;
- Movement Types;
- Merchandising Sectors.
User Validation
New validation rules have been added for usernames, ensuring greater integrity of stored information and preventing invalid records.Support for Comparative Reports
The API has been updated to support the new horizontal reports:- Comparative Managerial Income Statement;
- Comparative Financial Income Statement.
- Between months;
- Between years;
- Between different stores;
- Using combinations of periods and stores.
Budget Query Optimization
The merchandising sector level has been removed from Budget queries, simplifying the returned information and improving loading speed.Integration Ecosystem Improvements
Improvements related to the Archon APIs have also been completed.CNPJ Query
Handling of the429 — Too Many Requests error has been implemented for Brasil API queries, reducing failures and preventing information loss during registration.Municipality Autofill
In project creation routines, the municipality can now be filled in automatically based on the entered postal code, speeding up registration and reducing typing errors.Release Summary
API v6.1.0 provides greater stability, security, and traceability for the Platform360 ecosystem. The release also improves high-volume integrations, optimizes queries, and provides the structure required for the Portal’s new comparative reports.v6.0.14
API Hotfix v6.0.14
API Hotfix – Budget
- Previous Period Calculation: the number of days considered in the budget calculation has been fixed. The Previous Period now uses exactly the same number of days as the selected period, preventing calculations with excess days and ensuring more accurate results.
v6.0.10
Portal Hotfix v6.0.10
Portal Stability: an intermittent failure that could prevent or delay Portal loading has been fixed, providing users with more stable and reliable access.v6.0.13
API Hotfix v6.0.13
Budget: an error in the calculation when selecting a specific store and month has been fixed, ensuring that values are processed and displayed correctly.v6.0.09
Portal Hotfix v6.0.09
This Hotfix includes the following fix:- Statements: fixed an issue that prevented the PDF print preview from being displayed.
v6.0.12
API Hotfix v6.0.12
API Hotfix v6.0.12 includes two important fixes:- Financial Statement: fixed the Vertical Analysis (V.A.) calculation, which was not running correctly.
- Budget: fixed the error displayed when calculating values for a specific store and month.
v6.0.8
Portal Hotfix v6.0.8
Portal Hotfix v6.0.8 was released with four important fixes for Controller 360.- Financial Flow: fixed the display of the date type description.
- Statements: fixed the PDF print preview.
- Managerial and Financial Statements: adjusted the formatting of the % V.A. column.
- Analytics – Purchases: fixed the error displayed in the grid component.
v4.8.1
VR Sync360 4.8.1 Fix
Introduction
VR Sync360 is an essential tool for synchronizing VR Master and VR Controller360. An issue related to leap years was recently identified, affecting the software’s operation. This announcement explains how the fix was implemented and how users can update their installations.Detected Issue
When calculating the budget for October 2024, some users reported that VR Sync360 behaved unexpectedly. This occurred because of an issue in the calculation of the October pre-holiday date during a leap year.Implemented Solution
To resolve this issue, our development team worked on version 4.8.1 of VR Sync360. The following measures were taken:- Pre-Holiday Date Calculation Adjustment:
- The algorithm responsible for handling dates was reviewed and fixed to correctly account for leap years in October.
How to Update
- Windows Users:
- If VR Sync360 is already installed, the update will be automatic.
- If it is not installed yet, download the latest version here.
- Linux Users:
- Access the download link here.
- Follow the Linux-specific installation instructions.