Boston 4.3.5
Highlights of this Release
This release addresses several key issues and improvements. A critical bug in the Data Manager has been fixed, ensuring proper handling of static text and object variables. Additionally, we resolved a UTF-8 marshaling error impacting RWS functionality, and an App Connector issue that prevented tokens from being written to headers without a prefix. Furthermore, the "Log Input & Output Preview" feature has been enhanced to ensure copied data reflects the raw data accurately, removing unnecessary keys.
🅱️ Bug Fixes
Data Manager (sys_action_fields) Field Variable and Static Text Usage Error
Resolved an issue where only numeric values were passed when static text and object variables were combined in the Data Manager. Now, the full object variable is properly passed as input.
Marshal UTF8 Error RWS
Fixed a UTF-8 marshaling error that affected RWS functionality, ensuring proper encoding and data serialization, preventing operation failures.
App Connector Error
Addressed an issue where tokens without a prefix could not be written to the token header, ensuring smooth token handling regardless of prefix usage.
🛠️ Enhancement
Log Input & Output Preview
Enhanced the "Log Input & Output Preview" feature to ensure copied data accurately reflects the raw data by removing unnecessary keys, improving data consistency.
Detailed Version
Data Manager (sys_action_fields) Field Variable and Static Text Usage Error
A bug was identified where static text and object variables containing numeric values were not processed correctly in the Data Manager. When users combined static text with object variables (e.g., xxxx ##obj[aa]## yyyy
), only the numeric value (e.g., 123
) was passed, instead of the entire object. This caused incomplete data to be passed through the system. This issue, present in version 4.3.4, has been fixed to ensure that the full object variable, including both static text and object values, is passed as input. This ensures data integrity and accurate handling of mixed input types.
Marshal UTF8 Error RWS
In the previous version, UTF-8 encoding errors were encountered during the marshaling process, particularly affecting the RWS (Request-Write-Serialization) functionality. This error resulted in failures when attempting to serialize and encode data, especially when dealing with special characters or multi-byte characters. The fix ensures that UTF-8 encoded data is now properly handled during the marshaling process, allowing for smooth data serialization and preventing operational failures. This improvement strengthens the system's capability to handle diverse data inputs and ensures consistent performance across different encoding scenarios.
App Connector Error
An issue was found in the App Connector where tokens without a prefix could not be written to the header, disrupting the token-handling process during API communications. This occurred because the system required a token prefix, and without it, the token would not be accepted by the connector. This bug has now been fixed to allow tokens to be successfully written to the header, even when no prefix is provided. This fix eliminates an obstacle in token processing, ensuring smoother integration and communication between the system and external services, even in cases where the token prefix is not used.
Last updated