What's new?

Subcategory in app submission process New feature Freshworks has introduced subcategories to improve app discoverability. When submitting apps in the Freshworks Marketplace, you can select relevant subcategories under each app category. Subcategories help enhance the app filtering and improve the user experience. For more information, see Subcategory.

FDK v9.2.1 Minor engineering enhancement

Additional lint validations checks: We have documented additional lint validations that happen when running the fdk validate, fdk run, and fdk pack commands on an app. To learn more, see Lint validations.

Secure nested iparams on the custom installation page Security bux fix

On the custom installation page, secure iparams are not visible when used in the frontend app. However, when included in nested objects, they were accessible via object property accessors, which was not intended. We have now introduced a way to mark nested iparams as secure. To learn more, see Use postConfigs method.

Freddy AI powered app submission process New feature

Freshworks has introduced an enhanced app submission process, powered by Freddy AI, alongside a new Apps Categorization framework. This upgrade aims to improve app discoverability and build trust in the marketplace. The Freshworks Marketplace is also updating its app categories to better align with industry standards and user needs, promoting faster app discovery and adoption for enhanced business success. For more information, see App submission process.

FDK 9.2.0 New feature

Developer app settings

When developing an app, you may need to configure credentials such as tokens, API keys, and so on. Previously, the only way to set such credentials was to hard-code them in the code and pack and submit the app file to publish on the Freshworks marketplace. However, this method of hard-coding credentials raised security concerns and required releasing new app versions to update the credentials.

To resolve such issues and enable effective management of settings, the developer platform supports configuring credentials as variables while submitting the app in the Freshworks Developer portal. The app settings functionality allows you to provide runtime data to the app without hard-coding it in the app code.

To learn more about the app settings functionality, see Developer app settings.

FDK 9.1.3 Minor engineering enhancement

Freshworks CLI enhancements:

• A summary that displays the count of errors or warnings when running the fdk validate command has been added.

• Bugs that caused the CLI to abruptly stop if there were many validation errors and warnings have been fixed.

• Bug fixes have been added to some additional minor issues.

FDK 9.1.2 Minor engineering enhancement

• Key-value storage enhancement: When storing key-value pairs in a data store, the length of the key has been increased from 30 characters to 60 characters, and the combined size of the key and value has increased from 8 KB to 40 KB.

• fdk pack command: The option to skip code coverage when packing the app has been added. To learn more about the option to skip code coverage, see Freshworks CLI > Pack command.

• .report.json file: Checks have been added to verify if the .report.json file, generated after running an app, is modified or deleted during the app packing process. If the file is modified or deleted, an error message is displayed when running the fdk pack command.

FDK 9.1.1 Engineering enhancement

The latest FDK version supports building apps for both platform version v2.3 and v3.0. Platform version 3.0 enables building a global app across multiple products. To learn more about global apps, see Freshworks global app ecosystem.

Request Method enhancement: The request timeout value has been updated to a default of 15 seconds, with other possible values being 20, 25, and 30 seconds. Previously, the default value was 5 seconds, and the maximum value was 10 seconds. The default app execution timeout is 20 seconds. If the request timeout is increased to 20, 25, or 30 seconds, the app execution timeout is extended to 40 seconds.

unpkg CDN: The support for the unpkg CDN has been discontinued for both self-hosted and third-party libraries in frontend apps. Use any alternative CDNs when importing libraries for your frontend apps.

FDK installation using Homebrew and Chocolatey Feature enhancement

Previously, the only method for installing FDK was through NPM. Thus, developers were required to install NVM and a compatible Node.js version on their system.

Developers now have the option to use Homebrew (on macOS and Linux) and Chocolatey (on Windows) for installing the FDK along with the compatible Node.js version using a single command. This command creates a custom folder in the system and installs the necessary Node.js version and FDK in that custom folder.

For information on the steps to install FDK using Homebrew or Chocolatey, see the Install the FDK + CLI section.

FDK 9.0.9 Minor engineering enhancement

OAuth callback enhancement: During the OAuth handshake, the callback URL could have query parameters appended to it. The query parameter product was getting added to the callback URL without verifying whether the same product value exists in the URL's query parameters. This resulted in multiple instances of the product value in the callback URL's query parameters. This issue is fixed, and the callback URLs are checked to ensure that the product value is not already present in the URL's query parameters before appending it.

FDK 9.0.8 Minor engineering enhancement

Request Method enhancement: In templated Request Method, the sanitization of <requestTemplateName>.schema.headers was being skipped. This issue has now been fixed.

ngrok version upgrade: The FDK uses ngrok to support testing External events. The ngrok version that was used has been upgraded for better performance.

FDK 9.0.7 Minor engineering enhancement

Request Method enhancement: During local testing of apps that use the Request Method to make third-party HTTP requests, you can specify a request timeout value. You can configure a maximum of 10s as the request timeout value. This maximum limit was not being recognised. The issue has now been fixed.