Release Information for TUA Spartacus Libraries
Last updated January 13, 2022 by Deborah Cholmeley-Jones, Solution Owner, TUA Spartacus
Table of Contents
- Release 3.2
- Release 3.1
- Release 3.0
- Release 2.0
- Release 1.3
- Release 1.2
- Release 1.1
- Release 1.0
- About Spartacus for TUA Releases
- Upgrading TUA Spartacus Libraries to a New Minor Version
- Feature Releases
This document describes what is included in all Spartacus libraries since the initial 1.0 release, up to 3.2.
- For information on specific code changes for a particular release, see the Development Release Notes.
- For information about features published in pre-release libraries, see TUA Pre-Release Information.
- For information about upgrading, see Upgrading Spartacus Libraries to a New Minor Version.
- If you have technical questions, you can get in touch with us on Stack Overflow. For non-technical questions, you can reach us on our Slack workspace. Feedback welcome!
Disclaimer - Forward-Looking Statements
This document contains or may contain forward-looking statements. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. Any information is subject to change for any reason without notice. The information in this document is not a commitment, promise or legal obligation to deliver any material, code or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP’s intentional or gross negligence.
The various documentation links provided point to SAP Commerce Cloud or Accelerator documentation or third-party external links. These links are included for information purposes only and may not reflect exactly what is implemented in Spartacus.
Release 3.2 libraries published January 13, 2022
The 3.2 libraries for the accelerator provides a new B2B Telco Spartacus storefront along with sample data. Angular 10 is used in this release. B2B functionality supported includes:
- B2B Approval Workflow Processes
- B2B Organizational Management
- B2B Telco Spartacus Storefront
- Purchase PO with Configurable Characteristics
Release 3.1 libraries published September 1, 2021
The 3.1 libraries for the accelerator provides a new Media Spartacus storefront along with sample data. With 3.1, the TUA libraries support three storefronts: Telco, Utilities, and Media. Angular 10 is used in release 3.1.
Following features are introduced in release 3.1:
Release 3.0 libraries published April 7, 2021
As release 3.0 is a new major version, it contains breaking changes. To migrate to 3.0 from 2.x, please see the following documentation:
Following features are introduced in release 3.0:
- Complex Industry Cart.
- Contract (subscription) renewal without assurance.
- Contract (subscription) termination without assurance.
- Serviceability Check. This feature documentation covers serviceability check of a selected single product offering (SPO) and also serviceability check of all product offerings at the specified address.
You can refer to the core Release Information for all versions of Spartacus Libraries documentation for updates on the Spartacus framework including the upgrade to Angular 10 and related dependencies.
Note: For information on core commerce Spartacus, see Updating to Version 3.0.
Release 2.0 libraries published December 15, 2020
As release 2.0 is a new major version, it contains breaking changes. To migrate to 2.0 from 1.x, please see the following documentation:
Please refer to core Release Information for All Versions of Spartacus Libraries documentation for updates on the Spartacus framework including the upgrade to Angular 9 and related dependencies.
It is important to note that Spartacus 2.0 for TUA completely leverages the new composite pricing framework introduced with TUA release 2007. This means that the Spartacus 2.0 for TUA no longer supports Subscription Rate Plan pricing.
Pricing complex services for telcos, utilities, or other industries, require a pricing mechanism that can handle multiple types of charges (recurring charges, one-time charges, and usage-based charges) that may also have multiple of each type of charge, as well as tiered pricing. Composite pricing is now supported in the TUA Sparatacus storefront and provides the visibility of all pricing information that a customer needs to make an informed purchasing decision. For more information, see Composite Pricing in the TUA Help portal.
Customers are always interested in getting the best deal for products and services. With price alteration discounts, customers are able to see the discounted price of the product offerings before adding the item to the shopping basket. For more information, see Pricing - Price Alteration Discounts in the TUA Help portal.
Appointment scheduling is important as it ensures that you make the best use of your time and the providers time so that they can provide remarkable service. This goes without saying for customers purchasing multiple services, and having a single service appointment to service the multiple services ordered. For more information, see Journey Management - Appointment Scheduling in the TUA Help Portal.
Release 1.3.0 libraries published November 11, 2020
While it can be hard to pinpoint precisely how much your electric and water bill will cost each month, the Cost Estimation feature helps provide an indication as to the average monthly bill for a given product offering based on the anticipated consumption provided by a customer. Leveraging the anticipated usage provided by a customer, the estimated monthly and annual cost for applicable product offerings can be presented to the customer.
Customers interested in acquiring product offerings, such as commodity items (for example, electricity or gas) need to have an availability check of the premise details. As an example, the premise address and meter id is needed to conduct a serviceability check for a commodity product offering. For more information, see Serviceability example in the TUA Help portal.
Release 1.2.0 libraries published October 28, 2020
Journey Management facilitates real-time personalized customer journeys enabling online customers to successfully place an order. With the MSISDN checklist action in place, customers who wish to purchase a simple product offering that requires an MSISDN selection, will be required to select their new telephone number as part of the ordering process. For more information, see Journey Management in the TUA Help portal.
Release 1.1.0 libraries published October 7, 2020
Increase NPS with the Customer Product Inventory. This features helps companies understand their customers by having a complete view of the “recurring” relationships or assets, their customers have with them. The Customer Product Inventory is used to dynamically determine user journeys: what the customer is interested in, what they are willing to pay, and what products, services, and prices they are entitled to. For more information, see Customer Product Inventory (CPI) in the TUA Help portal.
Maximize customer retention by understanding the consumption of services by customers. Not all customers are created equal. Some subscribers are more valuable than others. With consumption data available, companies are able to analyze the data and provide customers with some highly engaging content, upgrades, or promotional offers to keep subscribers engaged. On the flip side, with consumption data visible, customers are able to see for themselves how much of the services they are actually consuming, which helps them maximize their investment and make more informative decision. For more information, see Create Average Service Usage for Subscribed Product in the TUA Help portal.
Release 1.0.0 libraries published September 9, 2020
The commercial product catalog for service industries is different and the distinction between product offerings and products is important to understand. Simple product offerings are different than retail products and represents what is externally presented to the market. For more information, see Simple Product Offerings in the TUA Help portal.
To support the commercial product catalog of product offerings, changes were required in the way “searches” are technically conducted to search for and find simple product offerings. Changes were made in the areas of free text search, facets, and top level category menu navigation. For more information, see Product Offering Search in the TUA Help portal.
To support product offerings and the complex pricing structure they have for one time charges, recurring charges and usage charges, changes to the cart were necessary. For more information, see Cart in the TUA Help portal.
To support product offerings and the complex pricing structure, they have for one time charges, recurring charges, and usage charges, changes to the order were necessary. For more information, see Order in the TUA Help portal.
To support product offerings and the complex pricing structure they have for one time charges, recurring charges and usage charges, changes to the checkout process were necessary. For more information, see in the TUA Help portal. For more information, see Checkout in the TUA Help portal.
Improves the user experience by simplifying the purchase process for complex bundled product offerings. Configurable Guided Selling (CGS) is the process in which a customer is taken through a step-by-step guided selling journey to purchase a complex product bundle. For more information, see Configurable Guided Selling in the TUA Help portal.
Provide greater customer experiences by providing product offerings to customers with specific pricing that they are eligible for. Pricing for product offerings is extremely complex and includes one time charges, recurring charges and usage based charges. For more information, see Pricing in the TUA Help Portal.
About Spartacus for TUA Releases
- Libraries that are “released” are new, official, tested TUA Spartacus libraries available to the public (hosted on npmjs.com)
- We usually publish new libraries every 2 weeks
- Similar to Spartacus: A change in minor means we added new features, but they are configured to be off by default, so as not to cause compatibility issues. A new minor also means inclusion of changes or bug fixes that may affect compatibility, but these are also controlled by feature flags. So all significant changes are “opt-in”. See feature flag documentation for more information.
- We will normally publish pre-release libraries labelled ‘next’ a few weeks before a new minor release. The goal is to provide early access to new features and get feedback from the community.
- If you choose not to use a new feature, you should have no problems upgrading to a new Major.# with features flag set to a previous Major.#. If you do see a problem, please report a bug and we’ll assess and fix it. We encourage you to upgrade to latest libraries frequently during development in order to take advantage of bug fixes and new features.
- Please visit our Spartacus for TUA Compatibility Matrix to understand requirements. For more information, see Feature Compatibility Matrix.
- To use all functionality in Spartacus 2.*, release 2005 of SAP Commerce Cloud and 2007 of Telco & Utilities Accelerator is required.
- The latest patch release is required or at least strongly recommended, as it usually contains bug fixes that affect Spartacus
Upgrading TUA Spartacus Libraries to a New Minor Version
You can upgrade your TUA Spartacus libraries to a new minor version, as follows:
package.json, set your
#is replaced with the release version number you wish to upgrade to.
If you are upgrading from 1.x to the latest 1.3 release in order to then upgrade to 2.x, in
package.json, set your
Make sure other entries in
package.jsonmatch with below configuration. (If not available add below entries)
"@angular/localize":"^9.1.0", "@angular/service-worker": "~9.1.0", "@ng-bootstrap/ng-bootstrap": "6.0.0", "@ng-select/ng-select": "^4.0.0", "@ngrx/effects": "~9.0.0", "@ngrx/router-store": "~9.0.0", "@ngrx/store": "~9.0.0", "bootstrap": "^4.2.1", "chart.js": "^2.9.3", "express": "^4.15.2", "i18next": "^19.3.4", "i18next-xhr-backend": "^3.2.2", "material-design-icons": "^3.0.1", "ng2-charts": "^2.3.2", "ngx-infinite-scroll": "^8.0.0", "ngx-spinner": "^9.0.1", "jquery": "^3.5.1"
- Inspect the
mystore/src/app/app.module.tsfile for any changes you want to make for your setup.
- Remove the
premiseLookupentry from the backend section if present.
saveForLater: falsefrom features section if present.
- Remove the
utilitiesspaentry from the
baseSitelist under the section context.
- Update level under features section to 2.0.0.
- Add the following import
/mystore/src/polyfills.tsin the file:
import '@angular/localize/init'; import 'zone.js/dist/zone';
- Remove the
Add the following entry
mystore/src/app/app.module.tsfile if not already available:
- Delete your
For more information, see Roadmap for TUA Spartacus.