Release Notes 200 OK Version 4.22.0

Release Notes - Package Version 4.22.0

Description

This release brings some of the much-anticipated feature enhancements such as Enhanced Data Store accessibility with use of custom unique keys and Time To Live(TTL) values, External Data Source(Integration Channel) as Load in ETL, Secure logging using Enable Masking functionality in Integration Channel, Multi-level function in ETL Transform, and Multiple inner queries in the ETL Data Source for better data accessibility, and so on.

Please refer to the detailed release notes for a complete overview of the changes and improvements in this version.

Package Version: 4.22.0.0

Table of Contents

New Functionality Enhancements

• Introduced new patterns such as ({!$UserId}, {!$OrganizationId}, {!$RecordId}) inside the Data Store for uniquely storing and accessing data in Org cache.

• Enhanced feature for customizing Time To Live(TTL) while accessing the data from Data Store(i.e., org cache) using fx_getDataStore() standard 200 OK function.

• Extended functionality to have default Time To Live(TTL) configuration for Data Store under Advanced Settings at channel level.

• External Data Source in ETL Load can now be used for making callouts through existing Integration Channel configuration.

• Multi-level functions can be used for complex and customized transformations in ETL.

• Multiple SOQL inner queries can now be used in Query as Data Source in ETL.

• Sensitive information used for making callouts using 200 OK can be masked in Integration Audit with the Enable Masking functionality available under Integration Channel Advanced Settings.

• Improved search option is available now for performing search ETL using Label, instead of API name while setting ETL as Request Body in Integration Channel.

• Enhanced searching of SObjects and Fields, and other Integration Actions and Data Mapping options.

• Introduced enhanced UI for Integration Action Filter.

• Bulk records in Integration Action can now be processed using /[!index] as well as [!index], (i.e., without /) in the mapping path.

• Case SObject can now be simulated using CaseNumber in Send With Data as well as Run With Data functionalities.

• Users can now reorder the execution sequence of saved Integration Actions using drag-and-drop functionality.

Improvements

• Improved UI for Integration Channel request payload section

• Addressed issue in mapping options for Data Mapper when there is at least one null value in Expected JSON

• Users should receive email notification in case of any failure during execution of post-installation script.

• Resolved issue with huge number of Integration Audit records.

• Enhanced UI to visualize Integration Action mapping value with a resizable window option.

• Improved user experience while using add or delete mapping options in the Transformation layer of ETL using “+” or delete buttons.

• Addressed mapping issue on selection of Extract JSON or Transform JSON in the ETL Data Mapper for Load as well as null values.

• Improved user experience such that on deleting the Load Item, a toast message should be displayed as "Load Item deleted successfully."

• UI enhancement for status code color and data in utility log while simulating the Integration Channel..

• UI improvements in making the consistency of the submit button.

New Functionality Enhancements

Functionality	Description
Introduced new patterns such as ({!$UserId}, {!$OrganizationId}, {!$RecordId}) inside the Data Store for uniquely storing and accessing data in Org cache	New patterns, such as {!$UserId}, {!$OrganizationId}, {!$RecordId}, have been introduced within the Data Store which can be used while setting the key, providing users with more dynamic and customizable options for uniquely identifiable data storage and retrieval.
Enhanced feature for customizing Time To Live(TTL) while accessing the data from Data Store(i.e., org cache) using fx_getDataStore() standard 200 OK function	This feature enables users to clear the temporarily stored data after a specified number of seconds from when it is accessed using fx_getDataStore() standard 200 OK function. By default, if not specified, the cached data is cleared immediately. This functionality will help users to retain the cached data for the specified duration even after accessing it for the first time.
Extended functionality to have default Time To Live(TTL) configuration for Data Store under Advanced Settings at channel level.	This functionality will help users specify a default TTL value(in seconds) in Advanced Settings of 200 OK Integration Channel based on which the Data Store value will be retained until specified duration after storing using corresponding Integration Action.
External Data Source in ETL Load can now be used for making callouts through existing Integration Channel configuration	External Data Source in ETL Load can now be used for making callouts through existing Integration Channel configuration facilitating seamless integration of extracted and/or transformed data into the external systems.
Multi-level functions can be used for complex and customized transformations in ETL	This functionality is useful when there is a need to use nested standard or custom functions to achieve further modifications on dynamic data in the transformation layer of ETL
Multiple SOQL inner queries can now be used in Query as Data Source in ETL	The ETL enhanced capabilities with support for multiple SOQL inner queries within Query as Data Source. This advancement allows for the execution of more intricate data retrieval operations, empowering users to efficiently extract with greater flexibility and precision across multiple related objects within Salesforce.
Sensitive information used for making callouts using 200 OK can be masked in Integration Audit with the Enable Masking functionality available under Integration Channel Advanced Settings.	If any sensitive information(such as credentials, tokens etc.) are used for making callouts using 200 OK, this information can be masked in Integration Audit with the new Enable Masking functionality available under Integration Channel Advanced Settings.
Improved search option is available now for performing search ETL using Label, instead of API name while setting ETL as Request Body in Integration Channel.	The search option has been enhanced, now displaying labels instead of API names, improving user experience and making it easier to identify and locate ETL records while setting up ETL as Request Body in Integration Channel.
Enhanced searching of SObjects and Fields, and other Integration Actions and Data Mapping options.	Searching for SObjects and fields has been enhanced, improving the efficiency and accuracy of locating specific objects and their associated fields within the system, such as Integration Actions and Data Mapper etc.
Introduced enhanced UI for Integration Action Filter.	The user interface for Integration Action Filters has been enhanced, improving usability and making it easier for users to create and manage action filters effectively.
Bulk records in Integration Action can now be processed using /[!index] as well as [!index], (i.e., without /) in the mapping path.	Bulk records in Integration Action can now be processed using /[!index] as well as [!index], (i.e., without /) in the mapping path. In 200 OK integration actions, users can use [!index] without slash or with slash same as [1] for bulk operations.
Case SObject can now be simulated using CaseNumber in Send With Data as well as Run With Data functionalities.	While simulating the Integration Channel or ETL using Send With Data or Run With Data respectively, users can now search and select Case records using Case Number with this enhancement.
Users can now reorder/swap the execution sequence of saved Integration Actions using drag-and-drop functionality.	Users can now swap/reorder Integration Action in case there is a need to change the order of execution among the already configured Integration Actions without need of deleting and configuring again.

Improvements

Bug Fix	Description
Addressed issue in mapping options for Data Mapper when there is at least one null value in Expected JSON	In the mapping options of Expected JSON, users faced a restriction wherein if the initial value of the JSON was NULL, they were unable to select subsequent JSON elements for mapping within the Transformation layer of ETL.
Users should receive email notification in case of any failure during execution of post-installation script.	During post-installation script execution, if there is any failure, users will now get notified via email and address any required modifications or reach out to 200 OK team for further support with the details.
Resolved issue with huge number of Integration Audit records.	With the increased number of external data source callouts, the number of Integration Audit records can be increasing. This has been handled and the potential issue has been addressed.
Enhanced UI to visualize Integration Action mapping value with a resizable window option.	The value field in action mapping is now resizable, allowing users to adjust its size according to their preferences or the length of the content they need to input, enhancing usability and flexibility.
Improved user experience while using add or delete mapping options in the Transformation layer of ETL using “+” or delete buttons.	Users can now add new transformation mapping using the "+" button or delete existing mappings using the delete buttons allowing users to efficiently manage transformation mappings within the ETL process.
Addressed mapping issue on selection of Extract JSON or Transform JSON in the ETL Data Mapper for Load as well as null values.	If there are any null values during extraction or transformation of data using ETL, data mapper is now working as expected for the mapping path upon selecting Extracted JSON or Transformed JSON in the Data Mapper.
Improved user experience such that on deleting the Load Item, a toast message should be displayed as "Load Item deleted successfully."	Improved user experience such that on deleting the Load Item, a toast message should be displayed as "Load Item deleted successfully."
UI enhancement for status code color and data in utility log while simulating the Integration Channel	Color schemes for status codes and data in utility logs have been updated, enhancing readability and visual clarity for improved monitoring and troubleshooting.
Improved UI for Integration Channel request payload section.	UI improvements for better User experience while configuring Integration Channel.
UI improvements in making the consistency of the submit button.	Changes have been made to ensure consistency in the appearance and functionality of the submit button, providing a more cohesive user experience across the platform.