FDK 7.0.1: Support has been added to enable the use of ES6+ (ES2018) features when building front-end apps. This enables using ES6+ constructs such as async/await.
FDK 7.0.0: The developer platform has been upgraded to run published apps on Node.js version 12.22.xx. FDK 7.0.0 contains the corresponding changes to support app creation, testing, validation, and packing in a local developer environment that is based on Node.js 12.22.xx. Support for Node.js 10.xx has been deprecated.
To enable the FDK to validate that the appropriate node and FDK versions are used, an attribute - engines - has been provided in manifest.json. When developers use FDK 7.0.0 to create an app, the engines value is auto-populated. When developers validate existing apps that were built by using the earlier versions of the FDK, the FDK prompts developers to update manifest.json. For information on the steps involved in app validation, see Validate. For more information on the engines attribute, see App Manifest.
Support has been added to enable the use of ES6+ (ES2018) features when building back-end/ serverless apps. This enables using ES6+ constructs such as async/await.
FDK 6.13.1 and FDK 6.13.2: Known issues and minor bugs have been fixed.
FDK 6.13.0: As part of our ongoing initiatives that enable developers to build secure apps, the app development platform has been upgraded. The latest platform version is 2.2. When building apps on the latest platform version,
- Ensure that all SMI functions/methods, defined in the serverless component of an SMI app, are registered (allow listed) in the app manifest. To enable this, a new attribute (functions) has been introduced in manifest.json. The functions attribute also contains a provision to specify function-based app execution timeouts for an SMI app.
- Ensure that all events defined in the server.js file of a serverless app and the corresponding callback methods are registered in manifest.json. To enable this, an attribute (events) has been introduced in manifest.json.
FDK 6.12.0: Known issues and minor bugs have been fixed.
FDK 6.11.1: Known issues and minor bugs have been fixed.
FDK 6.11.0: The FDK has been enhanced to ensure that all Request method calls to third-party domains are secure. This is achieved through domain whitelisting. For more information, see App Manifest.
FDK 6.9.8, FDK 6.9.9, and 6.10.0: Known issues and minor bugs have been fixed.
End-to-end testing: A mechanism to test the lifecycle events of locally running apps, without having to use a custom UI, has been introduced. For more information, see End-to-End Testing.
FDK 6.9.5, 6.9.6, and 6.9.7: Known issues and minor bugs have been fixed.
The App Management Portal (AMP) / Apps gallery that can be accessed through Settings > General Settings > Integrate with other Apps > Apps has been enhanced to provide a better user experience. For information on the different types of apps and how to submit an app through the new AMP, see Marketplace Listing.
FDK 6.9.0, 6.9.1, 6.9.2, 6.9.3, and 6.9.4: Known issues and minor bugs have been fixed.
FDK 6.8.0: Known issues and minor bugs have been fixed.
FDK 6.7.0, 6.7.1, and 6.7.2: Known issues and minor bugs have been fixed.
Support has been added for the full page app placeholder.
FDK 6.6.1, 6.6.2, and 6.6.3: Known issues and minor bugs have been fixed.
Front-end apps: Features that enable building front-end apps have been added. For information on the available placeholders, app life-cycle methods, and other methods that can be used to build front-end apps, see the CONFIGURATION and BASIC FEATURES sections.
FDK 6.5.5, 6.5.6, and 6.6.0: The FDK has been enhanced to enable support for the upcoming end-to-end app testing capability. Minor bugs have been fixed.
iparams callback functionality: A new feature to invoke a callback function when an event associated with an iparam occurs has been added. This feature enables making an installation page dynamic.
FDK v6.5.4: Known issues and bugs have been fixed.
FDK v6.5.3: Known issues and bugs have been fixed.
FDK v6.5.2: Support has been added for a new iparams attribute, visible, that enables displaying or hiding an iparam on the installation page.
FDK v6.5.1: Support has been added to detect sensitive iparams when running the fdk validate and fdk pack commands and display a warning to mark them as secure.
FDK v6.5.0: Known issues and bugs have been fixed.
FDK v6.4.0: Known issues and bugs have been fixed.
FDK v6.3.2: Known issues and bugs have been fixed.
As part of CLI v6.3.1, the OAuth refresh token handler has been enhanced to use appropriate refresh tokens to retrieve access tokens. At times, third-party resource providers do not issue new refresh tokens as part of their refresh strategy. The handler uses the old refresh token in such cases.
As part of CLI v6.3.0, the FDK has been enhanced to include a testing framework (beta) that enables creating automated unit tests for serverless apps. The framework uses the popular mochaV5. For information on how to write and run tests, see the Testing Framework documentation.
As part of CLI v6.2.7, the --fix option has been added to the validate command, to enable auto-fixing certain lint errors.
As part of CLI v6.2.6, some FDK bugs have been fixed.
As part of CLI v6.2.5, some FDK bugs have been fixed.
As part of CLI v6.2.4, the FDK has been updated to load static resources over HTTPS, by default.
As part of CLI v6.2.2, we have added fixes for number of bugs.
We have documented Lint validations which happen when running the fdk validate and fdk pack commands on an app.
As part of CLI v6.1.1, we have added fixes for a number of minor bugs.
To accommodate the changes in Chrome 79 and higher versions, where HTTPS pages only load secure subresources, the app testing process has been modified. According to the latest Chrome release notes, HTTPS pages will only be able to load secure subresources, with changes from Chrome 79 to Chrome 81.
The following enhancements have been made:
- In Request API, added new options, maxAttempts and retryDelay, and a new attribute, attempts.
- You can test external events on your computer using ngrok.
As part of CLI v6.0.1,
- You need to uninstall the previous CLI version by using the npm uninstall fdk -g command and install the latest CLI version.
- When testing scheduled events on your computer, the schedules will be triggered at the specified time and frequency after they are created or updated.
As part of CLI v6.0.0, added support for Node 10.x. Support for Node 8.10.x has been deprecated.
As part of CLI v5.4.0, the iparam_test_data.json file has been deprecated. Before testing the app, navigate to http://localhost:10001/custom_configs and enter appropriate values for the configured installation parameters.
As part of CLI v5.3.0, added fixes for a number of minor bugs.