Release Notes 200 OK Version 4.1.0

Release Notes - Package Version 4.1.0

Description

In this significant release, we're thrilled to introduce a range of exciting features that enhance various aspects of our system. Key highlights include improvements to the Integration Channel UI, ETL UI, Logging framework, and independent ETL module execution support. Additionally, we now offer support for multiple index paths in the ETL transformation layer, empowering users with more flexibility.

Among the noteworthy additions are standard functions with patterns inside text, the ability to combine nested functions, and the introduction of invoking ETL functions using ETL Name, type, and record Id. To further enhance integration capabilities, we've included Callback response support for Webhooks, adding a layer of responsiveness to your workflows.

These enhancements aim to provide a richer and more versatile experience, ensuring that our users have the tools they need for seamless and efficient operations. We're excited about the possibilities these additions bring to your workflows and look forward to your continued success with our platform. Please refer to the detailed release notes for a complete overview of the changes and improvements in this version.

Package Version: 4.1.0

Release Date: 08-Dec-2023

Table of Contents

1. New Functionality Enhancements

• Enhanced user experience for Integration Channel, Webhook and ETL

• Introduction of Advanced Logging Framework for Integration Channel and ETL

• Different type support for executing ETL such as,

1. Extract(E)

2. Transform(T)

3. Extract and Transform(ET)

4. Extract and Load(EL)

5. Transform and Load(TL)

6. Extract, Transform and Load(ETL)

• Introduced unique name for ETL which can be used to execute ETL

• Enhancement for multiple index and hardcoded string values for Transformation mapping in ETL

• Standard function fx_etl to support passing ETL Name, Type and RecordId as input for getting the transformed data

• Support of standard function having patterns within a string

• Support of multilevel functions for cross-functions like Standard function nested inside Custom function and vice-versa

• Introduced a new standard function fx_parseJson which can find value corresponding to a specified path in the given JSON data

• Introduced a new standard function fx_regex which can take input string and regex as parameters and return the matching substring, if it exists

• Enhanced UI to have an option to filter and view all Custom Functions inside Data Mapper

• Enhanced UI to have an option to create and register its own custom function from within Data Mapper

• Improved logic to auto-generate template test class along with the custom apex class while registering for a new custom function using above functionality

• Enhanced UI to provide sample Apex class template for creating custom Apex Class for Request Header, Request Body or Integration Action.

• Revamped Webhook functionality with the option to return different types of Response Body along with response content type using Callback Response integration action such as JSON, XML and Text

2. Improvements

• Improved error notification email to include channel name.

• Remote Site Settings to be set through Setup page.

• Considered global variable $Request in place of fx_request in Integration Channel.

• Support for Parent object field name inclusion in CSV header for fx_soqlToCsv standard function.

• Retention of request body data for any content type until a channel is saved.

New Functionality Enhancements

Functionality	Description
Enhanced user experience for Integration Channel, Webhook and ETL	UI Enhancement for smooth and quick navigation inside the application and Advanced Settings in ETL to have customized experience within the application.
Introduction of Advanced Logging Framework for Integration Channel and ETL	Logging framework for Integration Channel, Webhook and ETL to have logs for different logging levels like NONE, ERROR, WARN, DEBUG.
Enhancement for supporting ETL execution for different types	Different type support for executing ETL such as: Extract(E), Transform(T), Extract and Transform(ET), Extract and Load(EL), Transform and Load(TL), Extract, Transform and Load(ETL).
Introduced unique name for ETL which can be used to execute ETL	Simplified the process of making any ETL channel available for executing from outside using a unique ETL Name.
Enhancement for multiple index and hardcoded string values for Transformation mapping in ETL	Enhanced the ETL functionality to support bulk data transformation using multiple [!index] in the transform mapping value(up to 3 levels) along with hardcoded data mapping value support.
Standard function fx_etl to support passing ETL Name, Type and RecordId as input for getting the transformed data.	Improved the standard function fx_etl to accept unique ETL Name, ETL Type and Record Id as parameters to execute ETL inside Integration Channel.
Support of standard function having patterns within a text.	Standard functions will now support patterns within Text as parameter(s).
Support of multilevel functions for cross-functions like Standard function nested inside Custom function and vice-versa.	Enhanced the application to now support multilevel functions(up to 2 levels) for various combinations as below. Custom function inside standard function. Standard function inside custom function. Standard function inside standard function. Custom function inside custom function.
Introduced a new standard function fx_parseJson which can find value corresponding to a specified path in the given JSON data.	It takes input JSON string as the first parameter and the JSON path as the second parameter, and returns the value corresponding to the given path if path and value exists.
Introduced a new standard function fx_regex which can take input string and regex as parameters and return the matching substring, if it exists.	A new standard function fx_regex is now available which can take input string and regex as parameters and return the matching substring, if it exists.
Enhanced UI to have an option to filter and view all Custom Functions inside Data Mapper.	Users can see already created custom functions in Data Mapper under the Custom category.
Enhanced UI to have an option to create and register its own custom function from within Data Mapper.	Users can now register a custom function using the link available in Data Mapper and write their own login in the specified class with predefined template code.
Improved logic to auto-generate template test class along with the custom apex class while registering for a new custom function using above functionality.	Automated the test class creation for the custom function related template class upon registration of a new custom function.
Enhanced UI to provide sample Apex class template for creating custom Apex Class for Request Header, Request Body or Integration Action.	Enhanced UI to provide sample Apex class template for creating custom Apex Class for Request Header, Request Body or Integration Action. Users can copy the template code and create their own custom code for using inside Integration Action.
Revamped Webhook and LWS functionality with the option to return different types of Response Body along with response content type using Callback Response integration action such as JSON, XML and Text	Callback response can be used in Webhook to set Response Body for a Webhook call to 200 OK. The content-type can be set using the channel configuration and customized response can be sent back to the system from where Webhook is triggered. Scope: XML and Text callback response is limited to Webhook using $ROOT as key.

Improvements

Bug Fix	Description
Improved error notification email to include channel name.	Improved error notification email to include channel name and send email to current user if specific email address is not configured in Advanced Settings.
Remote Site Settings can be set through Setup page.	The ‘Add Remote Site Settings’ button will redirect to the Salesforce Setup page so that users can register the Remote Site for any endpoint URL.
Considered global variable $Request in place of fx_request in Integration Channel.	fx_request is not changed to global variable $Request for action mapping.
Support for Parent object field name inclusion in CSV header for fx_soqlToCsv standard function.	Parent object field name should be indicated with objectname.fieldname value in CSV header for fx_soqlToCsv standard function.
Preserving request body data for any content type until a channel is saved.	Preserving request body data for any content type until a channel is saved. i.e., if switching between Body type in Integration Channel, other tab details should be kept until the channel is saved/executed.