# Change Log All notable changes to this project are documented in this file. This project adheres to [Semantic Versioning](http://semver.org/) and the changelog is formatted based on [Keep a Changelog](http://keepachangelog.com/). ## [1.24.0] - 2026-04-30 ### Added - Added the ability to provide multiple service metadata files when using the headless generator ## [1.23.0] - 2026-04-16 ### Added - Added additional OPA5 tests during generation by analyzing the project metadata and annotations to provide meaningful tests for applications - Added the ability to select a full-service URL endpoint from the Connection Manager and use it when generating an SAP Fiori application ### Fixed - Fixed an issue where users were incorrectly notified that the SAPUI5 version in their application was not compatible with the manifest version during deployment - Fixed an issue where deployment did not timeout if no response was received from the back end ## [1.22.0] - 2026-03-19 ### Changed - Generated applications now have an ESLint configuration enabled by default ### Fixed - Fixed an issue where the generator did not display all relevant services from the selected ABAP catalog ## [1.21.0] - 2026-03-05 ### Changed - Updated the generator to display an informational message about row size limits when selecting a responsive table type - Updated generated applications to use eslint version 9 when choosing to add an ESLint configuration during generation ### Fixed - Fixed an issue where invalid package names in lower case provided during deployment configuration were not alerted to the user - Fixed an issue where users were incorrectly offered to create a new system when using the UI Service Generator - Fixed an issue where an incorrect authorization error message was displayed when selecting a destination in the generator in SAP Business Application Studio - Fixed an issue where the custom page template controller and xml files were created in the ext/main folder rather than the ext/view folder - Fixed an issue where value help metadata was not downloaded during generation if the generator was used from the command line ## [1.20.3] - 2026-02-05 ### Added - Added support for OData version 4.01 services for applications generated using SAPUI5 version 1.144 or higher - Added the ability to download metadata for value help which is referenced in an OData V4 service during generation ### Changed - Added more information to the error message displayed when the metadata for a service cannot be retrieved ### Fixed - Fixed an issue where the Application Generator crashed when deleting the main entity in the "Entity Selection" step ## [1.20.2] - 2026-01-22 ### Added - Added an info message when retrieving services for an ABAP Catalog if no services for OData V2 or OData V4 were returned ### Changed - Updated the Application Generator to support Yeoman version 5 ### Fixed - Fixed an issue where some generator prompts were incorrectly displayed if there was a validation error in a previous prompt - Fixed an issue where the option to download an ADT deployed app incorrectly offered to create a new saved system in Visual Studio Code - Fixed an issue where the generator did not detect a local CAP project if it was invoked from a subfolder of the CAP project - Fixed an issue where the SAP Fiori generator failed to find the correct saved system in Visual Studio Code when launched directly from ABAP Development Tools in Eclipse ## [1.20.1] - 2026-01-07 ### Added - Generated OData V4 applications now have lazy loading enabled by default for SAPUI5 versions 1.144 and above - ABAP deployment now provides warnings if the version of the manifest.json file and the version of SAPUI5 used in the application are not compatible ### Changed - The version added when you choose an eslint configuration has been upgraded to version 9 - Updated the Cloud Foundry deployment configuration so that you must now choose to add the application to either a managed application router or to an Application Frontend service - The advanced option to add code assist during project generation has been removed. Please use the option to generate with TypeScript, which includes code completion and type checking ### Fixed - Fixed an issue where the generator unexpectedly exited when changing from an HTTP connection to an HTTPS connection when adding a new saved system ## [1.20.0] - 2025-11-27 ### Fixed - Fixed an issue where an incorrect error message was shown during generation if the selected SAP System catalog only contained OData V2 services and the selected template type required an OData V4 service ## [1.19.6] - 2025-11-13 ### Added - Added the option to save system credentials during generation if the saved system does not already store the credentials or if the stored credentials are invalid ### Changed - Updated generated projects to use the latest version of UI5 CLI (Version 4) ### Fixed - Fixed an issue where an SAP Fiori application downloaded from an app deployed with ADT would fail to deploy again if the package was not local ## [1.19.5] - 2025-10-30 ### Fixed - Fixed an issue where the deployment configuration could not be added from the command line when using SAP Business Application Studio - Fixed an issue where a reuse library generated with SAPUI5 versions 1.71.x failed to deploy - Fixed an issue where the user was not warned when adding a new saved system if that saved system already existed when generating an application using the command line - Updated ux-ui5-tooling to no longer report high vulnerabilities with dependencies ## [1.19.2] - 2025-10-16 ### Changed - Updated ABAP Cloud saved systems to only use reentrance tickets. Existing saved system that use service keys are still supported, but you must use reentrance tickets for new ABAP Cloud system connections - Updated the default table type for SAP Fiori elements for OData V4 applications with a list report page or worklist page to an analytical table or tree table if the selected entity supports it ### Fixed - Fixed an issue where launching an SAP Fiori application in Visual Studio Code from ABAP Development Tools in Eclipse failed if the workspace in Visual Studio Code used a virtual directory - Fixed an issue where the UI Service Generator showed a message that contained invalid characters after generation - Fixed an issue where adding a new saved system using the "SAP Fiori generator" overwrote an existing saved system if it used the same connectivity details, without a warning ## [1.19.1] - 2025-10-02 ### Fixed - Fixed an issue where the "Transport Request" field was not marked as mandatory during deployment configuration - Fixed an issue where invalid error messages appeared in the output logs of the SAP Fiori generator when using an OData V4 service - Fixed an issue where the variants management script failed to load when virtual endpoints were not used ## [1.19.0] - 2025-09-18 ### Changed - Changed the warning message when using a virtual host in the destination in SAP Business Application Studio to an information message to make it clearer that deployment can continue without a fix ## Fixed - Fixed an issue where the option for ignoring certificate errors during deployment was not applied ## [1.18.7] - 2025-09-04 ### Added - Added a notification banner to the SAP Fiori generator that allows the user to launch the Project Accelerator directly ### Fixed - Fixed an issue where downloading a basic deployed application from ADT using Fiori tools would fail ## [1.18.6] - 2025-08-21 ### Added - Added an option to add a page building block to a custom page template during generation ### Changed - Updated the generator to use NPM workspaces by default when using a local CAP project as the data source - Updated generated OPA5 tests to use self-contained journeys ## Fixed - Fixed an issue where the generator was creating obsolete configuration when using a CAP Java data source ## [1.18.5] - 2025-08-07 ### Changed - Improved the performance of retrieving the full catalog service listing after SAP system selection ## Fixed - Fixed an issue during deployment configuration where the supplied package was not correctly identified as local so the user was asked to provide an unnecessary transport request - Fixed an issue where generated integration tests and unit tests failed on Windows environments - Fixed an issue where an SAP Fiori project downloaded from an ADT deployed application in ABAP had SAPUI5 linting errors ## [1.18.4] - 2025-07-24 ### Changed - Updated the SAP Fiori generator so that the table type for a list report or worklist floorplan defaults to "Analytical" if the selected entity supports it - Updated the logo for the SAP Fiori generator - Updated the generated deploy script for ABAP so that extra CLI parameters can be passed when running the npm run deploy command ## Fixed - Fixed an issue where the suggested project folder path in Visual Studio Code already contained an SAP Fiori project ## [1.18.3] - 2025-07-10 ## Fixed - Fixed an issue where the UI Service Generator showed non-ABAP destinations that were incompatible ## [1.18.2] - 2025-06-26 ### Changed - Updated generated applications to version 4 of the @ui5/cli library - Improved the tile images in the "Template Selection" screen ## Fixed - Fixed an issue where an error message was not displayed when attempting to download an ADT deployed application and none were available in the selected system - Fixed an issue where the navigation entity was requested when the supplied service did not support it - Fixed an issue where the SAP Fiori launchpad sandbox file was not correctly located during preview if the application was generated with non-virtual endpoints - Fixed an issue where the generated "Run and Debug" scripts in Visual Studio Code were not correct for applications generated with virtual endpoints - Fixed an issue where the UI Service Generator did not launch the SAP Fiori generator after the new service was created - Fixed an issue where the SAP Fiori generator did not prevent generation for path names that were longer than Windows supported ## [1.18.1] - 2025-06-12 ### Added - Added support for adding ABAP deployment configuration when using the SAP Fiori Generator in headless mode - Added the ability to bypass invalid SSL certificate errors while adding deploy configuration if the environment variable `NODE_TLS_REJECT_UNAUTHORIZED=0` is set ### Changed - Updated the warning message displayed during deployment to now include a link to Guided Answers with more details when the target landscape is using an invalid SSL certificate ### Fixed - Fixed an issue where an application generated and deployed with ABAP Development Tools could not be downloaded with SAP Fiori tools if there was no title or description in the original application - Fixed an issue where an application generated and deployed with ABAP Development Tools could not be re-deployed after being updated to support SAP Fiori tools ## [1.18.0] - 2025-05-29 ### Added - Added the ability to ignore any SSL certificate errors during generation by setting the Node.js global environment variable: NODE_TLS_REJECT_UNAUTHORIZED=0. ### Changed - Updated the generator when used in headless mode to support data sources as destinations in SAP Business Technology Platform ### Fixed - Fixed an issue where the option to generate with TypeScript was incorrectly displayed when the installed version of CDS did not support it - Fixed an issue where the generator incorrectly displayed OData V4 templates when an OData V2 service was chosen - Fixed an issue where an SAP Fiori project downloaded from an ADT deployed application in ABAP did not support SAP Fiori tools ## [1.17.6] - 2025-05-15 ### Changed - Changed the minimum required [Node.js](https://nodejs.org/en/download) version to 20.19.2 or higher ### Fixed - Fixed an issue where using an untrusted certificate in Visual Studio Code caused the preview to fail in the generated application - Fixed an issue where the description was undefined for a transport request when created as part of the UI Service Generator - Fixed an issue where a newly generated service using the UI Service Generator was not added to the project storyboard after generation ## [1.17.5] - 2025-05-01 ### Added - Newly generated SAP Fiori applications now use virtual endpoints by default ### Changed - Removed the SAP Fiori theme, Belize, as an option when using SAPUI5 version 1.136 or higher because it is no longer supported in these versions - ABAP deployment now displays a warning message when trying to redeploy an application using a different package name - The UI Service Generator now only offers the option for draft-enabled service generation if the associated business object supports drafts ### Fixed - Fixed an issue with the generator crashing if the list of destinations in SAP Business Application Studio was not successfully retrieved - Fixed an issue where the generator attempted to re-authenticate unnecessarily when navigating back to the data source step - Fixed an issue where the generator did not offer the option to use TypeScript when using a local CAP project as the data source - Fixed an issue where the package name used in deployment configuration was incorrectly validated ## [1.17.4] - 2025-04-17 ### Added - Added the option for users to create a new `mta.yaml` file when adding a deployment configuration for a Node.js CAP project when the file did not exist yet - Added support for the Application Frontend Service when adding a Cloud Foundry deployment configuration to an SAP Fiori application - Added the ability to download SAP Fiori applications from an ABAP SAPUI5 repository that has been deployed with the Quick Fiori Application generator using the ABAP Development Tools in Eclipse ### Fixed - Fixed an issue where using an ABAP Core Data Service as the object type when generating a new UI service incorrectly offered the ability to create a draft service - Fixed an issue where the expected deploy scripts were not created when adding a deployment configuration during generation of an SAP Fiori application in a CAP project - Fixed an issue where connecting to a BTP system using Visual Studio Code opened multiple browser windows for authentication - Fixed an issue where the list of services associated with a destination in SAP Business Application Studio was not successfully returned ## [1.17.3] - 2025-04-03 ### Fixed - Fixed an issue where the deployment configuration generator failed to start on Windows - Fixed an issue where the destination configuration in SAP Business Application Studio failed to load if the destination URL used uppercase and lowercase letters ## [1.17.1] - 2025-03-20 ### Changed - Optimized the file size for images in the SAP Fiori Generator ### Fixed - Fixed an issue where the required destination was not populated when adding a deployment configuration during generation. This occurred when users launched the SAP Fiori Generator from the ABAP Development Tools in Eclipse - Fixed an issue where only the SAP Fiori application folder was opened after generation, instead of also opening the CAP project that contained the SAP Fiori application ## [1.17.0] - 2025-03-05 ### Fixed - Fixed an issue where Cloud Foundry deployment configuration did not add managed application router support when selected - Fixed an issue where the "Reference Library" generator crashed on launch - Fixed an issue where deployment configuration for SAP S/4HANA Cloud used an incorrect ABAP package name - Fixed an issue where connecting to a Cloud Foundry environment on SAP BTP while using the generator crashed if the user did not have the required permissions ## [1.16.5] - 2025-02-20 ### Fixed - Fixed an issue where the Deployment Configuration Wizard would not launch successfully for migrated SAPUI5 extension projects ## [1.16.4] - 2025-02-06 ### Changed - Updated the deployment logic: now, if there is a timeout, the deployment logic is considered to have failed - Updated the SAP Fiori UI Service Generator to remove the restriction which only showed business objects that are prefixed with "I_" ### Fixed - Fixed an issue where the SAP Fiori generator crashed if the data source referenced a CAP project that used websockets - Fixed an issue where adding an SAP Fiori launchpad configuration to an existing SAP Fiori project overwrote the title and subtitle for all existing SAP Fiori launchpad configurations - Fixed an issue where a reusable library that uses TypeScript failed to deploy to ABAP landscapes - Fixed an issue where generated applications that used an OData V2 data source could not be previewed successfully when started using local SAPUI5 library sources - Fixed an issue where the UI Service Generator did not create a draft-enabled service when requested - Fixed an issue where the UI Service Generator crashed when a validation error occurred in the system connection ## [1.16.3] - 2025-01-23 ### Added - Added a warning when the back-end annotations for an OData V2 catalog service cannot be retrieved ### Changed - Updated the deployment configuration for SAP S/4HANA Cloud Public Edition and SAP S/4HANA Cloud Private Edition systems to support Cloud Foundry deployment ### Fixed - Fixed an issue where an aggregation alias defined in the metadata was not considered when generating an OData V4 ALP application - Fixed an issue where deployment for a reuse library failed when overwriting an existing deployment - Fixed an issue where deployment for a reuse library failed if the option to generate a standalone `index.html` file during deployment was chosen - Fixed an issue where generating an SAP Fiori application with TypeScript as part of a CAP project caused an error when previewed ## [1.16.2] - 2025-01-08 ### Changed - Updated the system connectivity error messages to be more descriptive ### Fixed - Fixed an issue where the generator crashed if an invalid service path was provided during data source connectivity - Fixed an issue where SAP Fiori elements applications using an OData V4 service from a catalog were incorrectly being generated as an OData V2 service application - Fixed an issue where the saved systems in Visual Studio Code incorrectly updated an On Premise system after editing - Fixed a security vulnerability reported with the generated /webapp/test/locate-reuse-libs.js file - Fixed an issue where the Application Router Generator crashed on completion - Fixed an issue with the deployment where the failFast parameter was not set correctly. - Fixed an issue where the "(Source system version)" suffix was not added to the SAPUI5 version that was used in the selected data source back-end system - Fixed an issue where the deployment configuration was not correctly pre-set when launching the SAP Fiori generator from the ABAP Development Tools in Eclipse - Fixed an issue where launching the SAP Fiori generator from the ABAP Development Tools in Eclipse failed if the ABAP system used re-entrance tickets - Fixed an issue with the deployment configuration where it was not possible to choose an existing package or transport if the application had a namespace defined - Fixed an issue where the UI5 Linter failed for a generated reusable library ## [1.16.0] - 2024-12-05 ### Added - Added the label `S4HC` to system connections that point to an SAP S/4HANA Cloud system ### Changed - Moved the option to generate the application with TypeScript out of advanced options and into the main project attributes step - Updated the deployment configuration to no longer ask for a transport request if a local package is provided - Updated the connectivity error messages to be more descriptive - Removed the system connectivity option for SAP Business Accelerator Hub from the SAP Fiori generator in SAP Business Application Studio, as this connection type is supported directly from the Service Center ### Fixed - Fixed a bug that caused the UI Service Generator to crash if `Draft Enabled` was set to `No` - Fixed an issue where the SAP Fiori generator crashed if an invalid service path was added to a partial URL destination - Fixed an issue where using a saved system in Visual Studio Code asked for authentication credentials even though they were contained in the saved system - Fixed an issue where using a full service URL with the SAP Fiori generator created an invalid entry in the generated `manifest.json` file for the service - Fixed an issue where SAP Fiori applications generated with SAP S/4HANA Cloud destinations in SAP Business Application Studio could not be used in Visual Studio Code - Fixed an issue where the target destination in the deployment configuration was not correctly populated if the application was generated directly using ADT Tools in Eclipse - Fixed an issue where Cloud Foundry was not provided as a deployment target if the application was added to a project with a managed app router - Fixed an issue where launching the SAP Fiori generator directly from a saved system would not automatically select the saved system during generation ## [1.15.6] - 2024-11-14 ### Fixed - Fixed an issue where deployment to an ABAP system failed if it was connected using a proxy - Fixed an issue where invalid error messages were displayed in the console when trying to connect to a saved system in Visual Studio Code - Fixed an issue where un-deployment of an application failed if the application was generated using TypeScript - Fixed an issue where an SAP Fiori reusable library written in TypeScript was not detected when trying to add it as a reference in an SAP Fiori application - Fixed an issue where users were not prompted for connection credentials when adding a deployment configuration for an ABAP system ## [1.15.4] - 2024-10-31 ### Added - Added the ability to automatically add table columns to the list page and sections to the object page from the command line generator - The Application Info page now automatically launches after a reusable library has been generated successfully ### Changed - Updated the SAP Fiori generator to prohibit the user from attempting to add a deployment configuration to a non-Fiori tools supported project - Updated the deployment generator so that it will prevent configuration for an SAP Fiori application in a CAP project if it does not already contain an `mta.yaml` file ### Fixed - Fixed an issue where the generator would crash if not connected to the internet when trying to retrieve the list of SAPUI5 versions - Fixed an issue where the SAPUI5 version from the selected ABAP back end wasn't displayed in the list of SAPUI5 versions when there was no connection to the internet - Fixed an issue where the UI Service Generator in VS Code would not correctly authenticate with a saved system that uses reentrance ticket authentication - Fixed an issue where launching the SAP Fiori generator directly from ADT in Eclipse could fail if the authentication was using a reentrance ticket ## [1.15.3] - 2024-10-16 ### Changed - Updated the UI Service Generator so that it no longer asks for a confirmation when launching the SAP Fiori Generator after the UI Service is generated ### Fixed - Fixed an issue where SAP Fiori applications generated as part of SAP Build Code incorrectly added deployment configurations that were not necessary - Fixed an issue where an invalid semantic object name could be provided as part of SAP Fiori launchpad configuration ## [1.15.2] - 2024-10-03 ### Added - Added an option to the UI Service Generator to automatically launch the SAP Fiori Generator to create an application with the newly generated service ### Changed - Updated the SAP Fiori Application Generator to prevent users from selecting a CAP project folder for an SAP Fiori application that didn't use a CAP data source ### Fixed - Fixed an issue where the UI Service Generator crashed when launched directly from the Service Center in SAP Business Application Studio ## [1.15.1] - 2024-09-19 ### Changed - Updated the SAP Fiori Generator to validate that the selected project folder path does not already contain an SAP Fiori application ### Fixed - Fixed an issue where the annotation sources for an OData V2 service were not correctly retrieved and included in an SAP Fiori application generated with the basic template - Fixed an issue with the SAP Fiori Generator where completed fields were reset when modifying other fields within the same section ## [1.15.0] - 2024-09-05 ### Added - Added the ability to launch the UI Service Generator from the Service Center in SAP Business Application Studio and to add the generated service to an existing storyboard project - Added support for launching the UI Service Generator from the Service Center in SAP Business Application Studio for destinations that require authentication ### Changed - Updated the warning message for A2X services that are unsuitable for SAP Fiori UI applications and included services that don't have a classification ### Fixed - Fixed an issue where the UX specification library would not install when using NPM workspaces with a CAP project during the installation of an SAP Fiori application ## [1.14.5] - 2024-08-22 ### Added - Added the ability to create a new UI service for an ABAP system, with the new service then being available for generating SAP Fiori applications - Added the option to open an existing SAP Fiori project from your workspace when you launch from ABAP Development Tools (ADT), if an SAP Fiori project in your workspace already exists that matches the system and service binding from ADT ### Changed - Improved support for storing saved system credentials in Visual Studio Code - Updated the Custom page template to remove unnecessary dependencies - Optimized the dependencies created when adding a deployment configuration to an SAP Fiori application ### Fixed - Fixed an issue where the SAP saved system could not be found when launching the SAP Fiori generator from the ABAP Development Tools environment - Fixed an issue where the deployment of your SAP Fiori application could fail if it was created using TypeScript - Fixed an issue where the generation of your SAP Fiori project could fail when being generated from the command line ## [1.14.4] - 2024-08-08 ### Changed - Updated the title of the SAP Fiori generator tab to `SAP Fiori generator` rather than using the generic `Template Wizard` title ### Fixed - Fixed an issue where deprecated warning messages were shown when installing the node libraries during generation ## [1.14.3] - 2024-07-24 ### Changed - Improved the error message text that appears when a user attempts to load the SAP Fiori generator in SAP Business Application Studio directly from ABAP Development Tools in Eclipse when the provided destination cannot retrieve the required service details ## [1.14.2] - 2024-07-10 ### Changed - Updated the minimum UI5 version to be 1.120.13 when creating an SAP Fiori application for a CAP project with SAP Build Code productivity tools - Updated the SAP Fiori generator to automatically add reference to the notes reuse library component (sap.nw.core.gbt.notes.lib.reuse) if a service is annotated with UI.Note ## [1.14.1] - 2024-06-26 ### Changed - Updated to the latest library versions for adding code assist libraries during project generation ### Fixed - Fixed an issue where adding ABAP deployment configuration using the command line could fail under certain circumstances ## [1.14.0] - 2024-06-12 ### Changed - Updated the generated SAP Fiori Basic template to not automatically enable SAPUI5 flexibility during UI5 bootstrap, as no SAPUI5 flexibility features will be used after initial generation ## [1.13.6] - 2024-05-29 ### Added - Added support for Single Sign On (SSO) authentication in Visual Studio Code using reentrance tickets ### Changed - 'Hierarchy Qualifier' is now a mandatory field when choosing the `Tree` table type with an OData V4 service ### Fixed - Fixed an issue where ABAP deployment would fail if the client ID in the `ui5-deploy.yaml` file was not enclosed in quotes ## [1.13.5] - 2024-05-15 ### Changed - Updated the SAP Business Accelerator Hub data source selection to warn that this data source is deprecated. - Removed deprecated `synchronizationMode` from the manifest.json file of generated projects with an OData V4 data source if the minimum UI5 version chosen is >= 1.110. - Improved the error message and logging when testing connections using the saved systems panel in VSCode. ### Fixed - Fixed an issue where the link to Guided Answers help documentation was not clickable from the terminal. - Fixed an issue where the ABAP destination wasn't being passed from the ABAP Development Tools in Eclipse to the SAP Fiori generator when ading deployment configuration. - Fixed an issue where deployment would fail when using the `ui5` cli command. ## [1.13.4] - 2024-05-01 ### Changed - The `Tree` table type is no longer provided as an option for the Analytical List Page template during generation, as this table type is not supported for an Analyical List Page with either a V2 or a V4 OData service. - The deploy confirmation message now resolves any environment variables from the deploy configuration to show the actual values that will be used during deployment. ### Fixed - Fixed the `archive-path` parameter so that it can reference any archive filename and it is no longer required to be called `archive.zip`. - Fixed an issue where compiling a local CAP project during generation might fail if the user had already deleted an SAP Fiori application from that CAP project. - Fixed an issue where the Fiori generator could crash in SAP Business Application Studio if the system choosen was an invalid ABAP Environment on SAP BTP. ## [1.13.3] - 2024-04-17 ### Added - Added the ability to choose a table type when generating an application that contains a list report page. - Added a check to ensure that the correct @sap/CDS version is installed before generating an SAP Fiori application for a local Node.JS CAP project. ### Changed - Updated the default description generated when creating a transport request for ABAP deployment to now include the name of the ABAP repository. - Updated the error messages returned to contain more information when there are issues with deployment to ABAP. ### Fixed - Fixed an issue where generating an SAP Fiori application into a CAP Java project could have removed any comments in the projects `pom.xml` file. ## [1.13.2] - 2024-04-03 ### Changed - Improved the error message displayed during ABAP deployment configuration when the user does not have the correct ADT authorization to retrieve package and transport requests. ### Fixed - Fixed an issue where adding a second SAP Fiori application to a CAP project would generate invalid annotation references. ## [1.13.1] - 2024-03-20 ### Fixed - Fixed an issue where users were incorrectly being asked if they want to create a standalone `index.html`during deployment configuration even if there was already an `index.html` present in the project. - Fixed an issue where users were being asked to provide authentication credentials during deployment without providing details on why they needed to re-authenticate. ## [1.13.0] - 2024-03-13 ### Changed - SAP Fiori applications generated as part of a full stack application in SAP Build Code will now always launch the page map after generation. - Updated the default minimum UI5 version used when generating an SAP Fiori application in non-interactive mode when no minimum UI5 version is supplied in the input. ### Fixed - Fixed an issue where an SAP Fiori application could have a linting error after migrating to support SAP Fiori tools. - Fixed an issue where a selected service chosen during generation could incorrectly warn that it is not suitable for UI development. - Fixed an issue where the SAP Fiori generator could crash if an invalid OData V4 service url was provided. ## [1.12.5] - 2024-02-28 ### Changed - Updated deploy error response that returns an xml document to now show the content of the error for easier reading. ### Fixed - Fixed an issue where deployment could fail with an invalid http 415 response. - Fixed an issue where users could select the group separator in a dropdown in the application wizard. ## [1.12.4] - 2024-02-14 ### Added - Added a validation message when trying to use a service from the SAP Business Accelerator Hub with an SAP Fiori template that does not support the service OData version. - Added a message after successful deployment if the deploy URL needs to be updated with an internal host reference. ### Fixed - Fixed an issue when migrating an Extensibility project that did not contain a manifest.json file. - Fixed an issue where an invalid deployment yaml file was not being correctly detected as being invalid. ## [1.12.3] - 2024-01-31 ### Added - Added a warning message when choosing to use a service from the SAP Business Accelerator Hub, as these services were not intented for use with SAP Fiori UI development. - Added the abillity to launch the SAP Fiori generator directly from an SAP saved system. When viewing an SAP saved system, a new link `Create SAP Fiori applicaton` will launch the generator and use the selected SAP saved system. ### Fixed - Fixed an issue where an incorrect error message would be returned to the user if there were no transport requests available when adding deployment configuration. ## [1.12.2] - 2024-01-17 ### Added - Added a warning message when choosing a service from an ABAP catalog during generation that was not intended for use with SAP Fiori UI development. ### Changed - Removed the deprecated freestyle SAPUI5 templates from the SAP Fiori generator. Customers are encouraged to use the Custom Page template with flexible programming model support or the Basic freestyle SAPUI5 template. Please note that existing SAP Fiori projects generated with the deprecated templates do not need to be migrated ### Fixed - Fixed an issue where the URL displayed after successful ABAP deployment may not detail the correct endpoint URL if the destination references an internal host. In such a situation, the user will now be warned that they will need to manually replace the host ## [1.12.1] - 2023-12-18 ### Fixed - Fixed an issue where invalid CDS files could be created for SAP Fiori applications generated using a CAP data source upon refresh of their development space in SAP Business Application Studio ## [1.12.0] - 2023-11-29 ### Added - Users can now add deployment configuration for Cloud Foundry to an existing application in a non-interactive mode from the command line or as a child process. ### Changed - Improved test connection functionality in the Saved Systems view in VSCode to more explicitly detail when services could not be retrieved. ### Fixed - Fixed issue with the FLP sandbox test file not loading for generated Fiori applications in a CAP project. - Fixed `typeRoots` compilation error for generated Fiori applications with TypeScript in a CAP project. - Fixed an issue where the latest version of CDS could cause a compliation failure of the CAP project. ## [1.11.5] - 2023-11-15 ### Changed - Improved error message and associated help text when connecting to an SAP saved system in VSCode fails. ### Fixed - Fixed an issue where the service annotation file was not downloaded during generation if using service url directly in a destination. - Fixed an issue where the parent `mta.yaml` file for a cloud foundry application was sometimes not updated when adding deployment configuration for a Fiori application. - Fixed an issue where the `deploy-test` command for validating ABAP deployment could sometimes report the deployment as invalid when it was valid. - Fixed an issue where undeployment of an ABAP application would fail if the application contained a namespace. ## [1.11.4] - 2023-11-01 ### Added - Choosing to automatically add table columns to a list page during generation of an SAP Fiori elements List Report or Worklist application with a CAP data source will now also add basic value helps. ### Changed - The ABAP `deploy-test` function has been updated to now also validate that the defined package name and transport request are available in the backend ABAP system. - Updated the error message for ABAP deployment when a longtext message is displayed. - The console information logged during generation now includes the time taken to generate the application. ### Fixed - Fixed an issue where building an MTA archive in SAP Business Application Studio would fail in some cases when it contained an SAP Fiori application. - Fixed an issue where deployment configuration could allow input of an invalid Cloud Foundry destination name. - Fixed an issue where the manifest id created during generation in the manifest file could be longer than permitted. ## [1.11.3] - 2023-10-18 ### Changed - Updated the generator to automatically select the default value in a dropdown list of options if only one option is available, thereby decreasing the number of clicks the user needs to perform - The generator should now warn the user if Node.js is not installed before use - Updated the manifest for OData V4 services using UI5 version 1.94 or higher to now use the `contextPath` instead of `entitySet`. ### Fixed - The FLP configuration wizard no longer writes out the value `{{flpSubtitle}}` in the launchpad if the optional subtitle for FLP is not provided. ## [1.11.2] - 2023-10-04 ### Changed - Changed the Basic template generated to also generate Typescript OPA tests when the user chooses to generate their application with Typescript support ### Fixed - Fixed an issue with the latest version of VSCode (1.83) not supporting storing and retrieving credentials from secure storage of the operating system for use with SAP saved systems - Fixed an issue with CAP projects not using a valid version of the `cds-ui5-plugin` library when choosing to use npm workspaces during generation - Fixed an issue where using uppercase characters for the project namespace during generation would lead to invalid applications that could not be previewed ## [1.11.1] - 2023-09-21 ### Changed - Removed the experimental warning that was being displayed when choosing TypeScript during generation ### Fixed - Fixed an issue where generating an SAP Fiori app as part of the `Full-Stack Application Using Productivity Tools` Dev Space in SAP Business Application Studio could generate an invalid `manifest.json` file - Fixed an issue where some local CAP projects were not being correctly detected as valid data sources during generation - Fixed an issue with generating an invalid key in the `manifest.json` file if the data source contained forward slashes - Fixed an issue where ABAP deployment was incorrectly requesting authentication details when being deployed in a CI/CD environment ## [1.11.0] - 2023-09-07 ### Added - Added the ability to generate a SAP Fiori app in VSCode with a self-signed or untrusted root CA ### Fixed - Fixed an issue when running SAP Fiori application resulted in an error due to missing `sap.cloud` property in manifest.json - Fixed an issue when Reuse Library Reference generator crashes when reference to a library is added to an exisitng library type project - Fixed an issue with generator which was launching app info page instead of page map in Low-Code-Base Full-Stack Cloud Application type dev space ## [1.10.6] - 2023-08-24 ### Added - Added ability to retain developer personalization settings for local preview on refresh or restart. ### Changed - Updated deprecation message for Fiori freestyle templates to indicate when they will be removed. - The Fiori module name suggested during generation will now increment if the default suggested name already exists. For example, the suggested module name will increment from `project1` to `project2` if the module `project1` already exists. - Changed the data source name `SAP API Business Hub` to be `SAP Business Accelerator Hub` to reflect the branding change in SAP Business Application Studio. ### Fixed - Fixed an issue where deploying a TypeScript application to an ABAP system would not include the TypeScript source artifacts in the deployed BSP. - Adding deployment configuration after generation using the wizard now correctly displays the already answered questions in the side panel. - Fixed an issue where the list of transport requests could not be retrieved during deployment configuration if the repository name or package name contained a namespace. ## [1.10.5] - 2023-08-10 ### Added - Added option to create Fiori launchpad configuration after generation using a wizard style approach rather than needing to use the command line. Users can use the command palette option `Fiori: Add SAP Fiori Launchpad Config` to launch the wizard. - Added Guided Answers link for deployment failures due to an invalid SSL certificate being used. ### Changed - Updated error messages to more clearly detail when you cannot use a V2 catalog service with the choosen SAP Fiori template. - Updated `cds-ui5-plugin` library version in generated CAP projects to support CDS V7. ### Fixed - Fixed an issue with deployment not using credentials supplied with the command line deploy target. - Fixed an issue where the deployment configuration wizard would not launch if the application was configured with managed app router support. - Fixed an issue with the un-deploy command not using credentials in local `.env` file. - Fixed an invalid URL link in the `readme.md` generated for an SAP Fiori application in a CAP project. ## [1.10.4] - 2023-07-27 ### Added - Added abililty for users to create an ABAP transport request during deployment. - Added option to generate UI annotations during generation if there are none already available for a Java CAP project. - Added a new VS Code command `Fiori: Deploy Application` to allow users to deploy their application from the command palette. ### Fixed - Fixed an issue where deployment could fail even when the correct credentials were passed as command line arguments. ## [1.10.3] - 2023-07-13 ### Added - Added support for @sap/cds version 7. ### Fixed - Fixed issue where failed ABAP deployment would not exit with an error code. - Fixed an issue where the list of transport requests provided during deployment configuration could fail if the package name contains a forward slash. ### Changed - The Fiori generator now consumes ABAP deployment logic from open source, which is published [here](https://github.com/SAP/open-ux-tools). ## [1.10.2] - 2023-06-29 ### Fixed - Fixed an issue where reference to a local Reuse Library was added as an absolute path rather than relative path to an existing Fiori project. ### Changed - SAP Fiori projects generated in dev space type `Full-Stack Application Using Productivity Tools` will now have the `minUI5Version` as 1.108.7. ## [1.10.1] - 2023-06-15 ### Added - Added option for generating SAP Fiori applications in a CAP project with TypeScript support. - Added ability to create new reusable libraries that can be referenced in SAP Fiori applications. Users can launch this generator from the command palette entry `Fiori: Open Reusable Library Generator`. ## [1.10.0] - 2023-06-01 ### Added - Added a warning when choosing to automatically add table columns during generation if the metadata service is larger than 1Mb, as this can significantly increase the time it takes to generate the application. ### Fixed - Fixed an issue where the list of local CAP projects available as the data source in the Fiori generator would sometimes show an invalid CAP project. ## [1.9.7] - 2023-05-18 ### Added - Added ability for customers to create a sub-generator that allows them to customize some of the project attributes and add their own steps and writing logic to the generated Fiori application. For more details, please see https://github.com/SAP-samples/fiori-tools-samples/sample-fiori-gen-ext. - Added support for migrating extension projects that were generated with WebIDE personal edition. ### Changed - Migrating re-use libraries no longer launches the SAP Fiori application information page, as this was invalid for these type of applications. ### Fixed - Fixed an issue with linting failures for applications generated with TypeScript support. - Fixed an issue with invalid custom controller TypeScript files being generated for the Custom Page template. ## [1.9.6] - 2023-05-03 ### Added - Added the description of the transport request alongside the transport request number when configuring your application for ABAP deployment. - Added warning message when choosing to generate an application with TypeScript support (requires version 1.11.1 or higher of the Application Wizard). ### Fixed - Fixed an issue where applications deployed using a service from the API Business Hub Enterprise would not be found in the BTP cockpit. - Fixed an issue where SAP Fiori freestyle projects being generated for CAP applications were being incorrectly identified as SAP Fiori elements projects. ## [1.9.5] - 2023-04-19 ### Changed - When selecting a CAP project using the SAP Fiori generator, if multiple CAP projects with the same name exist in the workspace, these projects will be prefixed with their folder path for easier identification. - Deployment long text console output that are clickable links will now have a message to say that the link can be clicked for more information. ### Fixed - Fixed an issue with generated SAP Fiori projects having eslint errors. - Fixed support for the managed application router with SAP Fiori applications generated using the API Business Hub Enterprise on SAP Business Application Studio. ## [1.9.4] - 2023-04-05 ### Added - Adding ABAP deployment configuration can now optionally retrieve the list of packages from the backend ABAP system. Users can still manually provide a package if the list cannot be fetched from the ABAP system. Note: This feature requires version 1.10.9 or higher of the Application Wizard, lower versions will require the user to manually provide the package name as currently. ### Changed - The `locate-reuse-lib.js` file, used to find any custom reuse libraries referenced in the manifest file, has been moved to the `webapp\test` folder. ### Fixed - Fixed identified security vulnerabilities in the generated `locate-reuse-lib.js` file. - Fixed issue when adding Cloud Foundry deployment configuration to a generated project where the destination option of `None` was incorrectly displayed. ## [1.9.3] - 2023-03-23 ### Changed - The SAP Fiori freestyle templates `SAP Fiori Worklist Application` and `SAP Fiori List-Detail Application` have been deprecated and are now reorganised into a `Deprecated Templates` section when choosing your template type. The Basic `SAPUI5 Application` template has been renamed to `Basic` and is the first template available within the SAP Fiori templates. ### Fixed - Fixed an issue where adding Cloud Foundry deployment configuration in VS Code to an existing SAP Fiori application could incorrectly display the service URL as the deployment target. ## [1.9.2] - 2023-03-09 ### Added - Adding deployment configuration for ABAP targets using the `npm run deploy-config` command line option will now allow you to select the package from the backend instead of having to type it manually. ### Changed - Changed deployment configuration for extension projects to only support ABAP targets. - Updated the version of `@ui5/cli` to version 3. Generated projects now require Node.js version 16.18 or higher. ### Fixed - Fixed issue with local preview for the SAP Fiori freestyle List-Detail application when generating with TypeScript support. ## [1.9.1] - 2023-02-23 ### Added - Added answers to the side panel of the Fiori generator so users can easily see the already answered questions. - Added Cloud Foundry support for instance based destinations defined locally in the project `mta.yaml` file. ### Changed - Filtered services from the catalog request that are not suitable for generating a Fiori application. ### Fixed - Fixed an issue with previewing Fiori freestyle applications that were generated using TypeScript. - Fixed Fiori generator crash when handling an OData source with invalid metadata. ## [1.9.0] - 2023-02-09 ### Added - Added option to generate SAP Fiori freestyle applications with TypeScript support (experimental). ### Changed - Updated the Fiori deployment configuration wizard to support editing existing deployment configuration. - Improved the error message for CAP project compilation failure using the generator. ### Fixed - Fixed an issue where users could generate their SAP Fiori application with a manifest ID greater than the permitted 70 characters. ## [1.8.6] - 2023-01-26 ### Added - Added option to generate SAP Fiori elements applications with TypeScript support (experimental). ### Changed - Updated ABAP deployment to support displaying debug log messages when either archiving the project for deployment, or from the backend service during deployment. - Updated error message if undeployment of an application fails. The new message mentions that the application may have already been undeployed. - Removed the unneeded `annotation.xml` file generated as part of a Fiori application in a CAP project. ### Fixed - Fixed an issue with using the deployment configuration generator for projects previously generated with the API Business Enterprise Hub in Business Application Studio. ## [1.8.5] - 2023-01-12 ### Added - Added ability to automatically detect local CAP projects in your workspace when choosing CAP as the data source during Fiori generation. - Added an option to create deployment configuration for an existing Fiori application using a wizard style approach rather than needing to use the command line. Users can use the command palette option `Fiori: Add Deployment Configuration` to launch the wizard. - Added links to launch SAP Guided Answers for common issues found during generation to help customers troubleshoot issues. ## [1.8.4] - 2022-12-16 ### Fixed - Fixed an issue where project path was incorrectly added to telemetry data. ## [1.8.3] - 2022-12-01 ### Added - Generator will now show its name and version at the header level of YUI wizard for easy access of information. ### Fixed - Fixed an issue where creation of deployment configuration was incorrectly allowed for steampunk system not configured as Extensibility Development system. ## [1.8.2] - 2022-11-17 ### Added - Added an option to create a transport request when adding ABAP deployment configuration to an SAP Fiori project. ### Fixed - Fixed an issue where adding a saved system was not available when adding deployment configuration during generation. - Adding TypeScript support and Javascript Code Assist support in the same project no longer causes the preview to fail. - Fixed issue with launch configuration not being created when adding an SAP Fiori project to a workspace with an existing MTA project. - Fixed issue where SAPUI5 ABAP Repository name was being reset when the package name was provided during deployment configuration. ## [1.8.1] - 2022-11-03 ### Added - Added ability to directly launch SAP Guided Answers and display the relevant guide for some errors that occur during generation. ### Fixed - Fixed an issue where adding deployment configuration to an existing SAP Fiori application from the command line would fail in VS Code. ## [1.8.0] - 2022-10-20 ### Added - Added an option `Enable TypeScript` under `Advanced Configuration` to create an SAPUI5 application with TypeScript support. - Added ability to choose a saved system in VSCode when selecting a deployment target environment. ### Changed - Updated the name and description of templates to improve the presentation of respective project types being generated. ### Fixed - Fixed an issue where `$tmp` instead of blank is displayed as default deployment package name for SAP BTP ABAP Environment. ## [1.7.6] - 2022-10-06 ### Added - Added a check to determine if the OData source provided during generation uses a self-signed certificate and, if so, we display a more meaningful error message. ### Changed - Removed the `generateManifestBundle` task from build scripts created with the SAP Fiori generator, since it's no longer needed. - Updated SAP Fiori applications generated using the flexible programming model to incorporate the `sap.fe.macros` namespace. ## [1.7.5] - 2022-09-22 ### Added - Added an option to create an SAP Fiori elements application based on the flexible programming model approach. - Added support for generating and deploying SAP Fiori applications from the API Business Hub Enterprise in SAP Business Application Studio. ### Changed - Updated the local preview of an application to use latest released SAPUI5 version if the choosen version in the project is not available on NPM. ### Fixed - Fixed an issue that potentially resulted in the migration tool getting stuck during the migration of SAP Fiori projects. - Fixed issue causing the SAP Fiori generator to crash when choosing the Form Entry Object Page floorplan with a data source from a project-specific destination in SAP Business Application Studio. ## [1.7.4] - 2022-09-08 ### Added - Added option to choose your transport request during ABAP deployment configuration from a list of available requests when applicable. ### Fixed - Fixed issue with ABAP deployment where the deployment description could not include special characters. ### Changed - Updated floorplan icons in SAP Fiori generator to reflect latest Horizon theme. ## [1.7.3] - 2022-08-25 ### Fixed - Fixed an issue where some CAP Java projects were not being correctly identified as Java projects in the Fiori generator. ## [1.7.1] - 2022-08-10 ### Added - Added links to Guided Answers for easier troubleshooting of deployment issues arising due to unavailability of SAPUI5 ABAP Repository service. ### Fixed - Fixed an issue where Form Entry Object Page (FEOP) could not be selected from a V4 service in the SAP Business Application Studio Service Centre. ## [1.7.0] - 2022-07-27 ### Added - Added two new SAPUI5 themes - `Morning Horizon` and `Evening Horizon` with `Morning Horizon` as a default theme if Minimum SAPUI5 version selected is 1.102 and above. - Added links to Guided Answers for easier troubleshooting of generator issues arising due to misconfiguration of SAP BTP destinations. ### Fixed - Fixed issue where generator crashed without internet connection. - Fixed issue where invalid input was allowed for SAPUI5 ABAP Repository field during deployment config generation. ## [1.6.7] - 2022-07-21 ### Changed - Generating an SAP Fiori application with Cloud Foundry deployment configuration into a NodeJS or JAVA CAP project will now add Cloud Foundry build and deploy commands to the root `package.json` if not already present. ## [1.6.6] - 2022-07-07 ### Added - Added ability to import and export saved ABAP On-premise SAP Systems when using VSCode. Credential information is not exported and users therefore need to re-authenticate when importing. ### Fixed - Fixed issue where saving an SAP System in VSCode would crash if the system name was not provided. - Fixed issue with back navigation when adding deployment configuration in SAP Business Application Studio. ## [1.6.4] - 2022-06-23 ### Added - Added a check when using a destination in SAP Business Application Studio with the Fiori generator to ensure that the destination catalog service(s) can be found. #### Changed - Changed deployment configuration with clear text and hints whilst enforcing transport request validation where applicable. ### Fixed - Fixed issue where an invalid saved SAP System in Windows was not displaying the correct error message. - Fixed ABAP deployment issue where user could be asked to re-authenticate against backend even if they had already authenticated successfully. ## [1.6.3] - 2022-06-09 ### Added - The list of minimum SAPUI5 versions available during project generation are now grouped into `maintained versions` and `out of maintenance versions` for easy reference. - Added a check when deploying to an existing SAPUI5 ABAP repository with a new SAP App ID. Previously the deployment would overwrite the existing one, now the user is asked to confirm the overwrite. ### Fixed - Fixed an issue where the CDS watch script for an SAP Fiori application in a Node.js CAP project was not getting created. - Fixed an issue where the previews are failing for a Fiori Freestyle application when created with Data Source as `None`. - Fixed an issue where the reuse library referenced in an existing project was not being loaded from the local workspace. ## [1.6.1] - 2022-05-26 ### Added - Added unique non-identifable `toolsId` identifer to the manifest.json file for generated projects to support telemetry. #### Changed - Updated validation of Node.js CAP data sources to detail if the compilation of the services failed. - Improved the error message when an OData service URL provided does not reference an OData service. ### Fixed - Fixed issue when using API Business Hub in SAP Business Application Studio with local preview. - Fixed issue where the Generator would not follow http redirects for an OData service URL. ## [1.6.0] - 2022-05-12 ### Added - Added support for the SAP Fiori elements Overview Page floorplan with an OData V4 data source. - Added Ability to generate Cloud Foundry deployment configuration for an existing SAP Fiori project in a non-interactive mode. #### Changed - Updated the launch targets generated for a SAP Fiori application in VSCode to remove those allowing you to specify an SAPUI5 version at runtime. Please use the Fiori Run Configurations tool to change the version of SAPUI5 needed. ### Fixed - Fixed issue where adding an SAP Fiori application to a JAVA Cap Project may fail to start if the relevant plugins and configuration were not already present in the project. These updates are now added as part of generation if needed. - Fixed the Form Entry Object Page floorplan to only accept OData V4 services. ## [1.5.5] - 2022-04-28 ### Added - Added support for the SAP Fiori elements Worklist floorplan with an OData V4 data source. #### Changed - Adding a new system during generation will now display the username of the user after authentication to the system. - The deployment name is no longer automatically populated from the module name when adding deployment configuration. ### Fixed - Fixed CAP services retrieval to support services defined in nested folders in CAP projects. ## [1.5.4] - 2022-04-14 ### Added - Added support for instance based destinations in deployment configuration for local Node.js CAP projects in SAP Business Application Studio. #### Changed - Fiori generator for application type `SAP Fiori elements` now consumes the open source SAP Fiori elements templates published [here](https://github.com/SAP/open-ux-tools). ### Fixed - Fixed bug where VSCode launch configuration would not start the project correctly in certain situations. - Fixed issue where the Fiori generator would allow the user to continue if the mandatory navigation entity was not selected. ## [1.5.3] - 2022-03-31 ### Added - Added support for creating new saved SAP systems in VSCode. Users can click on the '+' icon and select to create an ABAP on Premise or ABAP Environment on SAP Business Technology Platform saved system. Users must test the connection to validate it connects before saving. #### Changed - Determining if telemetry data is to be captured during generation is now determined from the global SAP Fiori tools setting in the command palette: `Fiori: Change Telemetry Settings`. ### Fixed - Fixed bug where message longtexts were not displayed in the console for ABAP deployment errors. These can be copied and pasted into the browser for more details. - Fixed bug where the SAP Fiori generator could crash if the project folder location was read-only. - Fixed error where SAP Fiori freestyle projects with an uploaded metadata file were not being validated correctly. ## [1.5.2] - 2022-03-17 ### Fixed - Fixed invalid xs-security.json file location when using generator in non-interactive mode for CAP projects. - Fixed launch configurations in VSCode when the Fiori project is generated inside an MTA subfolder. - Fixed bug where App Router configuration needed to be added to an MTA.yaml file before Fiori deployment configuration. - Fixed issue with deployment errors containing longtext messages that did not have the associated URL clickable. ## [1.5.1] - 2022-03-03 #### Added - Added warning during deployment if deploying to an ABAP system that uses a lower version of SAPUI5 than that specified as the minimum SAPUI5 version in the SAP Fiori project being deployed. #### Changed - Added entity selection details to the `README.md` file for a generated SAP Fiori application. ### Fixed - Fixed issue with generated applications not working with SAPUI5 versions greater than or equal to 1.100.0 - The `start-variants-management` script will not be available if the SAP Fiori project was generated by uploading a metadata document rather than using a live service. ## [1.5.0] - 2022-02-17 #### Added - Added support for editing saved SAP systems in VSCode by selecting the saved system from the SAP Systems list and updating as needed. Users must test the connection to validate it connects before saving. - Added support for matching the suggested minimum SAPUI5 version with the backend ABAP system, where applicable. The SAPUI5 version dropdown will now default to the same version of SAPUI5 if the data source provided is an ABAP backend and the SAPUI5 version can be determined. #### Changed - Removed the `Latest` label from the list of minimum SAPUI5 versions. The version of SAPUI5 choosen during generation will now be a fixed version from that selected. - Generated applications with a OData V2 data source now use an external mockserver for mock support, rather than the SAPUI5 client side mock. ### Fixed - The generated `README.md` file now correctly details if the application was generated with the Fiori elements or Fiori freestlye generator. ## [1.4.7] - 2022-02-03 #### Changed - Updated the `Analytical List Page` floorplan, when used with an V4 OData service, to now only support version 1.90 and above of SAPUI5. This enables the generated project to adhere to the latest recommended configuration. - Updated the local preview `npm` targets to not use the browser cache to ensure the latest updates are being reflected in the browser. - Removed unneeded i18n references from the generated manifest file. ### Fixed - Fixed an issue where the Fiori generator would crash if attempting to connect to an on-premise system using SAML in VSCode. ## [1.4.6] - 2022-01-20 #### Added - Generating an SAP Fiori freestyle application will launch the `Application Info` page for that application after generation completes. #### Changed - The SAP Fiori freestyle template `SAP Fiori Master-Detail Application` has been renamed `SAP Fiori List-Detail Application`. ### Fixed - Starting your SAP Fiori application from the launch/debug configuration with a specified version of UI5 will now use that specific version of UI5. - Fixed linting errors displayed after application is deployed. - SAP Fiori freestyle applications generated with a CAP project no longer identify as SAP Fiori elements applications within the SAP Fiori tools suite. ## [1.4.4] - 2021-12-09 #### Added - Added support for the experimental SAP Horizon theme, as long as a supported version of UI5 is selected during generation. #### Changed - Choosing the UI5 version for your application is no longer under `Advanced Options` and is now directly on the `Project Attributes` step for better visibility. ### Fixed - Selecting a Fiori freestyle SAPUI5 template with no datasource no longer crashes the generator. - Performing a test deployment no longer reports the result as an error unless the test deployment fails. ## [1.4.3] - 2021-11-25 #### Added - A new SAP Fiori elements floor plan is now available. The `Form Entry Object Page` floor plan for V4 OData sources allows you to create an SAP Fiori application with an object page for data entry. - The `List Report Object Page` floor plan and the new `Form Entry Object Page` floor plan can now optionally generate UI annotations during generation if there are none already available in the supplied data source. **Note:** This is an experimental feature and can be switched off by disabling the `Sap › Ux › Application Modeler: Enable Experimental Features` option in the settings. #### Changed - Generated applications now use the Fiori CLI in the generated launch configuration to start the application. ### Fixed - Fixed crash in the `CF Application Router` generator if an MTA ID with invalid characters is provided. - Using the SAP Fiori generator from the command line in Business Application Studio now supports data sources using the API Business Hub. - Generating a SAP Fiori freestyle application into a CAP project with an `mta.yaml` file should now launch successfully. - Using a Java CAP project with the SAP Fiori generator no longer requires a `package.json` file in the root folder. ## [1.4.1] - 2021-11-11 #### Added - Generating an Analytical List Page application with an OData V4 data source will now default to a table type of `AnalyticalTable`, and the user will no longer be asked to choose a table type. The user can change this table type after generation using the Page Editor tool. #### Changed - Fiori generator for application type `SAPUI5 freestyle` now consumes the open source Freestyle templates published [here](https://github.com/SAP/open-ux-tools). ### Fixed - Saved SAP systems should not ask the user to re-authenticate when being used with the Fiori generator in VSCode, unless needed. ## [1.4.0] - 2021-10-28 #### Added - UUA Authentication is now supported during deployment without launching a browser, as long as the relevant authentication parameters are supplied. See the SAP Fiori tools help portal for full details. ### Fixed - Generating an application into a CAP project no longer adds unnecessary npm dependencies. - Destinations in SAP Business Application Studio are now filtered to show only those that can be used in the generator. ## [1.3.7] - 2021-10-14 #### Added - A new npm script for ABAP deployment configuration has been added, `deploy-test`. Using this target will allow you to validate your deployment configuration without actually deploying. ## [1.3.6] - 2021-10-07 ### Fixed - OData services that require a querystring parameter in the URL are now supported. ## [1.3.5] - 2021-09-30 #### Added - The Fiori command line tools now has help context information available. Typing `npx fiori help` will give the user a list of commands that the Fiori command line tools support. Help text for individual Fiori commands can also be displayed, e.g. `npx fiori add help`. ### Fixed - Adding deployment configuration to a Fiori application with an existng MTA project should now successfully update the `mta.yaml` and `package.json` files in the parent folder. - Fixed standalone deployment configuration for Cloud Foundry destinations. - The Fiori generator no longer crashes if the Cloud Foundry account does not match that configured in SAP Business Application Studio. ## [1.3.3] - 2021-09-16 #### Added - The generator now supports optionally adding eslint validation to the generated project. Choosing this option from the advanced options of the generator will add the eslint libraries and a new target `npm run lint` to perform the validation. - ABAP deployment now allows the user to provide a project ZIP file from either the local filesystem or from a remote URL. - Successful deployment to Cloud Foundry will provide instructions on how to retreive the URL of the deployed application. - Using the `CF Application Router Generator` for generating a multi-targeted application no longer asks for the version of the MTA, but will default to `0.0.1` in the generated `mta.yaml` file. ### Fixed - Better handling for destinations with SAML authentication. - Deployment logic updated to ensure only files in the `dist` folder are uploaded. - Better support for long MTA identifier names during Cloud Foundry deployment. - Improved support for project folders with spaces with the generator. ## [1.3.2] - 2021-09-02 #### Added - Added ability to optionally include UI5 code assistance libraries to the generated application by choosing it in the advanced options of the generator. - Using a Saved System in VSCode will now ask the user to re-authenticate if the saved credentials are no longer valid. ### Fixed - Fixed an issue which caused the Fiori generator to crash when connecting to a Cloud Foundry service if the SAP Business Application Studio subaccount is not the same as the Cloud Foundry organisation. ## [1.3.1] - 2021-08-19 #### Added - Added support for generating Fiori applications using the SAP API Business Hub from the Service Center in Business Application Studio. - Non identifiable and optional telemetry data has been added for deployment. ### Fixed - The `minUI5Version` version in the generated `manifest.json` file now details the UI5 version used during generation. - Improved support for detecting Reuse libraries in the local workspace. ## [1.3.0] - 2021-07-28 ### Fixed - Fixed an issue which caused the Fiori generator to crash due to presence of multiple schemas in the metadata file - Fixed an issue where generated project was missing undeploy script when deploy config was created for Cloud Foundry environment - Fixed an issue where the cloned reuse library with missing description in i18 file was not being listed for being added as a reference ## [1.2.5] - 2021-07-22 #### Added - Added support for Cloud Foundry deployment configuration during non-interactive generation. ### Fixed - Better support for determining if pre-requisite `mta` library is installed before attempting to add Cloud Foundry deployment configuration. - Removed erroneous telemetry error messages when using the generator from the command line. - Fixed the deployment name character restrictions for ABAP deployment. ## [1.2.4] - 2021-07-08 #### Added - Destinations configured with a service URL endpoint, or a hostname, can now be used with the Fiori generator in Business Application Studio. - Reuse components and libraries in the local workspace can now be added to your project. Use the command palette entry `Fiori: Add Reference to SAP Fiori Reusable Libraries` to invoke this functionality. ### Fixed - In Business Application Studio, the Cloud Foundry Destination dropdown in the Deployment Configuration step of the Generator should now successfully return all available destinations. ## [1.2.3] - 2021-06-24 #### Added - Deploying to a system that requires authentication will now prompt for a username and password if a local `.env` file with the credentials is not present. - Installing the generator in a custom location is now supported. ### Fixed - Freestyle applications generated for a CAP project will no longer contain invalid test artefacts. - The `start-local` npm target now works with the SAP Belize theme. - Deleting a saved SAP system from VSCode now also deletes the authentication token from the secure storage. - Deployed Fiori elements applications now correctly display the application title. ## [1.2.1] - 2021-06-10 #### Added - Added support for the Service Center in Business Application Studio. Services selected in the Service Center can now be used with the Fiori generator and the user will not be asked to provide a data source during generation, the selected service from the Service Center will be used instead. - Added support for Destinations in Business Application Studio that have been configured with a service endpoint URL rather than a catalog service. ### Fixed - Requesting authentication for a saved system in VSCode no longer launches multiple browsers to authenticate. Only one browser should now open. - Browser title for deployed applications now correctly displays the application title. - Upgraded UI5 libraries to resolve security vulnerabilities. ## [1.2.0] - 2021-05-28 ### Fixed - The Fiori generator will be automatically installed if it is invoked from the command palette in VSCode and not already installed. - Projects migrated from WebIDE to Business Application Studio can now be deployed. - Migrated projects now include an OPA test script where applicable. ## [1.1.11] - 2021-05-14 #### Added - Added support to include undeployment script (check `undeploy` script in package.json) when deployment configuration is generated for ABAP systems. #### Fixed - To ensure consistency, all generated V2, V4 or CAP applications will now have a header bar and preview will launch the application in a browser directly without showing Fiori launchpad first ## [1.1.10] - 2021-04-29 #### Added - Improved the destination catalog service request to ensure the list of services returned is filtered to those suitable for Fiori applications.  Note: the catalog service needs to also be updated to accommodate this change, if not, the existing list is returned. #### Fixed - The Fiori migration wizard on Business Application Studio no longer asks for the client field. ## [1.1.9] - 2021-04-15 #### Added - Fiori elements applications generated with the following floor plans now have simple OPA automated tests generated with the project: - List Report Object Page (with either a V2 or V4 OData service) - Analytical List Page (with an V4 OData service) - Added Ability to generate a Fiori freestyle application from the command line in a non-interactive mode. - Floor plan icons in the generator have been updated. - The deployment configuration questions have been reduced where system information can already be determined. - The generator now requires [MTA](https://www.npmjs.com/package/mta) Node.js package (version 1.0 or higher) to be installed globally. Please ensure you have updated by executing `npm install -g mta`. #### Fixed - Navigating back and forwards within the wizard should not lose previously completed steps. - The generator will no longer suggest the first folder in a workspace to generate the application into. - Better handling of long module names for deployment - The generator README.MD file now correctly details the floor plan used. ## [1.1.7] - 2021-04-01 #### Added - Uploading a metadata document for V4 OData services is now supported. - Better error messaging when the destination in Business Application Studio is not available. #### Fixed - The freestyle floor plans now correctly generate for a CAP project. - Going back from deployment to the project attributes step in the wizard now retains the data between steps. - Adding launchpad config on the command line can now overwrite existing configuration if desired. ## [1.1.6] - 2021-03-26 #### Fixed - Adding Cloud Foundry deployment configuration in Business Application Studio during generation no longer results in an error. ## [1.1.5] - 2021-03-18 #### Added - Freestyle SAPUI5 floor plan now supports OData V4 services. - The analytical list page floor plan with OData V4 service now supports navigation entities. - Adding deployment configuration for Cloud Foundry now supports the managed application router. - Using the `CF Application Router Generator` for generating a multi-targeted application now supports the managed application router. #### Fixed - Applications deployed to the managed application router cannot resolve the ui5 destination. - In some cases, validation messages for invalid OData service URLs were not being displayed. ## [1.1.4] - 2021-03-04 #### Added - Added support for the central Fiori Launchpad for managed app router configurations. - Generated projects no longer contain a `.npmrc` file and use the global settings. - Project generation time has been improved. #### Fixed - The Fiori generator no longer has a conflict with the SAP Mobile Development Kit VSCode extension. - Fixed invalid 401 error for OData service URL endpoints. - Project folder is no longer created before generation starts. - Deployment to Cloud Foundry now supports Org name with spaces. - Updating an existing MTA file with deployment configuration on Windows is now supported. ## [1.1.2] - 2021-02-19 #### Added - Support for adding project deployment configuration to an existing managed app router. - Project paths in generated launch configuration are now relative. - Migrating an existing application now prompts for system client. - In SAP Business Application Studio, the destination name for MTA deployment configuration is now a dropdown of available destinations rather than a free text field. - For ABAP deployment configuration, the user can now optionally provide a deployment description. #### Fixed - Standalone deployment to Cloud Foundry no longer returns an error. ## [1.1.0] - 2021-02-05 #### Added - Initial Version - Consolidated the existing `Fiori elements` and `Fiori freestyle` generators into one. The first step of the combined generator will ask you to choose which type of application you would like to generate. - Added support for deployment configuration as part of generation. Users can now choose to add either Cloud Foundry or ABAP deployment configuration using the generator if they wish. - Added support for Fiori launch pad (FLP) configuration as part of generation. - Added a new `Cloud Foundry Application Router Generator` that allows the user to generate generic Cloud Foundry configuration which can then be used with subsequent Fiori projects. - Added support for custom paths for folder locations in CDS projects. - The authenticated username is now displayed alongside the saved system name when using VSCode.