diff --git a/Gemfile.lock b/Gemfile.lock index 20aeb37c3..45acf42cf 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -1,18 +1,18 @@ GEM remote: https://rubygems.org/ specs: - activesupport (6.0.2.1) + activesupport (6.0.3) concurrent-ruby (~> 1.0, >= 1.0.2) i18n (>= 0.7, < 2) minitest (~> 5.1) tzinfo (~> 1.1) - zeitwerk (~> 2.2) + zeitwerk (~> 2.2, >= 2.2.2) addressable (2.7.0) public_suffix (>= 2.0.2, < 5.0) algolia_html_extractor (2.6.2) json (~> 2.0) nokogiri (~> 1.10.4) - algoliasearch (1.27.1) + algoliasearch (1.27.2) httpclient (~> 2.8, >= 2.8.3) json (>= 1.5.1) coffee-script (2.4.1) @@ -33,10 +33,10 @@ GEM eventmachine (1.2.7) eventmachine (1.2.7-x64-mingw32) execjs (2.7.0) - faraday (1.0.0) + faraday (1.0.1) multipart-post (>= 1.2, < 3) - ffi (1.11.1) - ffi (1.11.1-x64-mingw32) + ffi (1.12.2) + ffi (1.12.2-x64-mingw32) filesize (0.2.0) forwardable-extended (2.6.0) gemoji (3.0.1) @@ -224,8 +224,8 @@ GEM jekyll (>= 3.5, < 5.0) jekyll-feed (~> 0.9) jekyll-seo-tag (~> 2.1) - minimal-mistakes-jekyll (4.18.1) - jekyll (>= 3.6, < 5.0) + minimal-mistakes-jekyll (4.19.2) + jekyll (>= 3.7, < 5.0) jekyll-feed (~> 0.1) jekyll-gist (~> 1.5) jekyll-include-cache (~> 0.1) @@ -237,19 +237,20 @@ GEM mini_portile2 (~> 2.4.0) nokogiri (1.10.9-x64-mingw32) mini_portile2 (~> 2.4.0) - octokit (4.14.0) + octokit (4.18.0) + faraday (>= 0.9) sawyer (~> 0.8.0, >= 0.5.3) pathutil (0.16.2) forwardable-extended (~> 2.6) progressbar (1.10.1) public_suffix (3.1.1) - rb-fsevent (0.10.3) + rb-fsevent (0.10.4) rb-inotify (0.10.1) ffi (~> 1.0) rouge (3.13.0) - ruby-enum (0.7.2) + ruby-enum (0.8.0) i18n - rubyzip (2.2.0) + rubyzip (2.3.0) safe_yaml (1.0.5) sass (3.7.4) sass-listen (~> 4.0.0) @@ -262,11 +263,11 @@ GEM terminal-table (1.8.0) unicode-display_width (~> 1.1, >= 1.1.1) thread_safe (0.3.6) - typhoeus (1.3.1) + typhoeus (1.4.0) ethon (>= 0.9.0) - tzinfo (1.2.6) + tzinfo (1.2.7) thread_safe (~> 0.1) - unicode-display_width (1.6.1) + unicode-display_width (1.7.0) verbal_expressions (0.1.5) wdm (0.1.1) zeitwerk (2.3.0) diff --git a/_data/navigation.yml b/_data/navigation.yml index 8883cfab9..50b626a88 100755 --- a/_data/navigation.yml +++ b/_data/navigation.yml @@ -232,11 +232,23 @@ docs: - title: Telco & Utilities Storefront Development Guide children: - - title: "About Telco & Utilities Storefront" - url: /about-telco/ - - title: "Release Information" - url: /telco-release-information/ - + - title: "About TUA Spartacus" + url: /about-tua-spartacus/ + - title: "Release Information for TUA Spartacus ➢" + url: /telco-release-information/ + subchildren: + - title: "Pre-Release Information" + url: /tua-pre-release-notes-next1/ + - title: "Roadmap for TUA Spartacus" + url: /tua-spartacus-roadmap/ + - title: "Getting Started with TUA Spartacus ➢" + url: /getting-started-with-tua-spartacus/ + subchildren: + - title: "Installing SAP Commerce Cloud for use with TUA Spartacus." + url: /installing-sap-commerce-for-tua-spartacus/ + - title: "Building the TUA Spartacus Storefront from Libraries" + url: /building-the-tua-storefront-from-libraries/ + - title: Contributing to Spartacus children: - title: "Contributor's Guide ➢" diff --git a/_pages/telco/about-telco.md b/_pages/telco/about-telco.md deleted file mode 100644 index 0051dcbff..000000000 --- a/_pages/telco/about-telco.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: About Telco & Utilities Storefront ---- - -Telco & Utilities Storefront is a ready-to-use web framework, designed to maximize average revenue per user through cost effective, streamlined process. The storefront provides all the functionality and business tools that are required to build an omnichannel e-Commerce solution, supporting the unique and individual needs of subscription-based businesses, including telecommunications, utilities, and media. - -Service providers can deliver personalized and relevant user experiences tailored to the needs of their customers. The storefront provides a future-proof technical foundation for growth, quick time-to-market, and a competitive advantage for delivering more innovative capabilities. For more information, see [Telco & Utilities Storefront](https://help.sap.com/viewer/4c33bf189ab9409e84e589295c36d96e/latest/en-US/8af76e0086691014b65a94b19f679088.html). diff --git a/_pages/telco/about-tua-spartacus.md b/_pages/telco/about-tua-spartacus.md new file mode 100644 index 000000000..ee548850e --- /dev/null +++ b/_pages/telco/about-tua-spartacus.md @@ -0,0 +1,7 @@ +--- +title: About TUA Spartacus +--- + +The telco and utilities accelerator for project "Spartacus" (TUA Spartacus) is a lean, Angular-based storefront for SAP Commerce working exclusively through the Commerce REST API. TUA Spartacus works with and enhances the Telco and Utilities Accelerator storefront. In addition to supporting Commerce REST APIs, the Telco and Utilities Accelerator supports TM Forum APIs for delivering industry-specific functionality. + +Service providers can deliver personalized and relevant user experiences tailored to the needs of their customers. The TUA storefront provides a future-proof technical foundation for growth, quick time-to-market, and a competitive advantage for delivering innovative capabilities. For more information, see [TUA Storefront](https://b2ctelco.avengers:9002/yacceleratorstorefront/b2ctelco/en/). diff --git a/_pages/telco/building-the-tua-storefront-from-libraries.md b/_pages/telco/building-the-tua-storefront-from-libraries.md new file mode 100644 index 000000000..1642cc7f3 --- /dev/null +++ b/_pages/telco/building-the-tua-storefront-from-libraries.md @@ -0,0 +1,259 @@ +--- +title: Building the TUA Spartacus Storefront from Libraries +--- + +The following instructions describe how to build a TUA storefront application using published TUA Spartacus 1.x libraries. + +**Note:** If you are building TUA Spartacus from source, see [Contributor Setup]({{ site.baseurl }}{% link _pages/contributing/contributor-setup.md %}). + +## Prerequisites + +Before carrying out the procedures below, ensure that you meet the following front-end and back-end requirements. + +## Front-End Development Requirements + +{% include docs/frontend_requirements.html %} + +### Installing or Updating the Prerequisite Development Tools + +There are a few ways you can install Angular and other prerequisite software. The following example installs yarn, node.js, and Angular CLI using [Homebrew](https://brew.sh), which was created for MacOS, but also works on Linux and Windows 10 (through the Linux subsystem feature). + +To install the prerequisite development tools, install [Homebrew](https://brew.sh), and then run the following commands: + +``` +brew install yarn +brew install node@10 +brew install angular-cli +``` + +To update existing installations, use `brew upgrade` instead of `brew install`. + +**Note:** + +- If you have a later version of node.js installed in addition to v10, you can set v10 to be used with the following command: +`brew link --force --overwrite node@10`. +- Installing Homebrew and the prerequisites is beyond the scope of this document. You can also install the prerequisites using their individual installers. + +## Back End Server Requirements + +TUA Spartacus uses SAP Commerce and Telco & Utilities Accelerator for its back end, and makes use of the sample data from the Telco & Utilities Accelerator storefront in particular. + +- SAP Commerce version: Release 1905 (latest patch is recommended). +- Telco & Utilities Accelerator version: Release 2003 (latest patch) is required. + +For more information, see [Installing SAP Commerce for use with TUA Spartacus]({{ site.baseurl }}{% link _pages/telco/installing-sap-commerce-for-tua-spartacus.md %}). + +## Creating a New Angular App + +To create a new Angular application with the name `mystore`, follow the procedure: + +1. Open a terminal or command prompt window at the location of your choice. + +2. Using the Angular CLI, generate a new Angular application with the following command: + + ```bash + ng new mystore --style=scss + ``` + + When prompted if you would like to add Angular routing, enter `n` for 'no'. + + The `mystore` folder and the new app are created. + +3. Access the newly created `mystore` folder with the following command: + + ```bash + cd mystore + ``` + +## Project Setup + +The easiest way to start a new project and to quickly set up your application: + +Run `yarn start`. + +For a full list of available parameters, visit Spartacus schematics [documentation](https://github.com/SAP/cloud-commerce-spartacus-storefront/tree/develop/projects/schematics). + +## Setting up a Storefront Manually + +Although we recommend using Schematics, there might be situations when you want to build your application from scratch. + +The dependencies in this procedure are required by the TUA Spartacus storefront. + +1. Inspect the `mystore/src/app/app.module.ts` file for any changes you want to make for your setup. For example, you might want to change the `baseUrl` to point to your server and the `basesite` to corresond with the WCMS site. You likely also want to specify the compatibility version by changing `features.level`, as the default might not be the latest version. + + To make use of the modules shipped with `tua-spa` library, the `app.module.ts` must have the following structure: + + ```typescript + import {BrowserModule} from '@angular/platform-browser'; + import {NgModule} from '@angular/core'; + import {ConfigModule} from '@spartacus/core'; + import {AppComponent} from './app.component'; + import {translationChunksConfig, translations} from '@spartacus/assets'; + import {TmaAuthModule, TmaB2cStorefrontModule, TmaProductSummaryModule, tmaTranslations, TmfModule} from '@spartacus/tua-spa'; + + @NgModule({ + declarations: [ + AppComponent + ], + imports: [ + BrowserModule, + TmaAuthModule, + TmfModule.forRoot(), + TmaB2cStorefrontModule.withConfig({ + backend: { + tmf: { + baseUrl: 'https://localhost:9002', + prefix: '/b2ctelcotmfwebservices/v2/', + }, + occ: { + baseUrl: 'https://localhost:9002', + prefix: '/rest/v2/', + endpoints: { + product_scopes: { + details: + 'products/${productCode}?fields=averageRating,stock(DEFAULT),description,availableForPickup,code,url,price(DEFAULT),numberOfReviews,manufacturer,categories(FULL),priceRange,multidimensional,configuratorType,configurable,tags,images(FULL),productOfferingPrice(FULL),productSpecification,validFor', + }, + productSearch: + 'products/search?fields=products(code,name,summary,price(FULL),images(DEFAULT),stock(FULL),averageRating,variantOptions,productSpecification),facets,breadcrumbs,pagination(DEFAULT),sorts(DEFAULT),freeTextSearch', + }, + } + }, + routing: { + routes: { + product: { + paths: ['product/:productCode/:name', 'product/:productCode'], + } + } + }, + context: { + urlParameters: ['baseSite', 'language', 'currency'], + baseSite: ['telcospa'] + }, + i18n: { + resources: translations, + chunks: translationChunksConfig, + fallbackLang: 'en' + }, + features: { + level: '1.4' + } + }), + ConfigModule.withConfig({ + i18n: { + resources: tmaTranslations + } + }), + TmaProductSummaryModule, + ], + providers: [], + bootstrap: [AppComponent] + }) + export class AppModule { + } + ``` + +2. Replace the entire contents of `mystore/src/app/app.component.html with Loading...` with: + + ```html + Loading... + ``` + +3. Open `mystore/package.json` using a text editor. + +4. Add the following dependencies to the end of the `dependencies` section of `package.json`. + + ```json + "@angular/pwa": "^0.803.2", + "@angular/service-worker": "~8.2.5", + "@ng-bootstrap/ng-bootstrap": "5.1.0", + "@ng-select/ng-select": "^3.0.7", + "@ngrx/effects": "~8.3.0", + "@ngrx/router-store": "~8.3.0", + "@ngrx/store": "~8.3.0", + "ngx-infinite-scroll": "^8.0.0", + "bootstrap": "^4.2.1", + "i18next": "^15.0.6", + "i18next-xhr-backend": "^2.0.1", + "material-design-icons": "^3.0.1", + + "@spartacus/core": "~1.5.0", + "@spartacus/styles": "~1.5.0", + "@spartacus/storefront": "~1.5.0", + "@spartacus/assets": "~1.5.0", + "@spartacus/styles": "~1.5.0", + "@spartacus/tua-spa": "~0.1.0-next.2", + ``` + + **Note:** Make sure to add a comma to the end of the last dependency statement listed in this section. For example, the last statement in your new app might be `"zone.js": "~0.9.1"` so you need to add a comma after `0.9.1"`. + +5. Make sure that the following import is found in the `mystore/src/styles.scss`: + + ```bash + @import '~@spartacus/styles/index'; + @import '~@spartacus/tua-spa/storefrontstyles/index'; + ``` + +6. From the terminal window, within `mystore`, install the dependencies by running the following command: + + ```bash + yarn install + ``` + +7. Start the angular client app. From the terminal window, within `mystore` start the application by running the following command: + + ```bash + yarn start + ``` + +8. Make sure your backend server is up and running (SAP Commerce with TUA). When the backend server is properly started, point your browser to http://localhost:4200/telcospa/en/usd. + +**Note:** + +(1) Using `~` instructs yarn to use the latest patch version (x.y.**z**); whereas, using `^` instructs yarn to use the latest minor version (x.**y**.0). + +(2) If you are updating an existing app, and changing dependencies, it is recommended to delete the `node_modules` folder before running the install command. + +### Adding Import Declarations and Storefront Configuration Settings + +**Note:** Some statements in the preceding example were generated by Angular when you first created the app. + +#### About the Import Statements + +The import statements import either modules or default data needed by TUA Spartacus. + +## Building and Starting + +This section describes how to validate your back-end installation and start the application with the storefront enabled. + +## Validating the SAP Commerce Back End + +**Note:** The Chrome browser is recommended and used in the following example, but other browsers can be used as long as they recognize and allow you to continue even though a site is using a self-signed certificate. + +1. Use a web browser to access the OCC endpoint of your backend. + + The default is available at: `{server-base-url}/rest/v2/electronics/cms/pages` + + For example, you can access: + https://localhost:9002/rest/v2/telcospa/cms/pages with a back-end instance running from `https://localhost:9002`. + +2. Accept the security exception in your browser if you are running a development instance with a self-signed HTTPS certificate. + + When the request works, you will see an XML response in your browser. + +### Starting the Storefront Application + +To start your TUA Spartacus storefront, enter the following command from `mystore` in your terminal window: + + ```bash +yarn start + ``` + + When the app server is properly started, point your browser to http://localhost:4200. + +Or, to start your TUA Spartacus storefront securely, enter the following command: + + ```bash +yarn start --ssl + ``` + +Then point your browser to https://localhost:4200. \ No newline at end of file diff --git a/_pages/telco/customer-product-inventory.md b/_pages/telco/customer-product-inventory.md new file mode 100644 index 000000000..5735c8881 --- /dev/null +++ b/_pages/telco/customer-product-inventory.md @@ -0,0 +1,117 @@ +--- +title: Customer Product Inventory (CPI) +--- + +**Note:** This feature is introduced in version 1.1.0 of the TUA Spartacus libraries. + +## Contents + +- [Overview](#overview) +- [Key Personas](#key-personas) +- [Navigation Flow](#navigation-flow) +- [Business Use Cases](#business-use-cases) + - [Viewing All Subscriptions](#viewing-all-subscriptions) + - [Viewing Details of Subscribed Products in a Tile Format](#viewing-details-of-subscribed-products-in-a-tile-format) + - [Viewing the Usage Consumption of a Subscribed Product in Pie Charts](#viewing-the-usage-consumption-of-a-subscribed-product-in-pie-charts) + - [Viewing Subscribed Products in a Grid or a Tabular Format](#viewing-subscribed-products-in-a-grid-or-a-tabular-format) +- [Requirements and Dependencies](#requirements-and-dependencies) +- [Configuring and Enabling Customer Product Inventory](#configuring-and-enabling-customer-product-inventory) +- [Further Reading](#further-reading) + +## Overview + +The Customer Product Inventory feature enables logged in customers who are browsing the telco and utilities accelerator for project "Spartacus" (TUA Spartacus) storefront to view their subscriptions-related information and subscribed products, as imported in the Telco & Utilities Accelerator from external systems. + +## Key Personas + +- Customers +- Product Managers + +## Navigation Flow + +From the **Account** menu drop-down, click **Subscriptions**. The `My Subscriptions` screen is displayed. The subscriptions show: + +- Subscription ID. For example, 1040123111111. +- Number of subscribed offerings. For example, 2. +- Usage Details. + +

+ +## Business Use Cases + +### Viewing All Subscriptions + +From the **Account** menu drop-down, click **Subscriptions**. All subscriptions are displayed. + +

+ +### Viewing Details of Subscribed Products in a Tile Format + +1. From the **Account** menu drop-down, click **Subscriptions**. All subscriptions are displayed. +2. Click the header that shows the subscriber ID. For example, **1040123111111**. The subscribed products are displayed in a tile format. + +**Note:** The subscriptions owner will see all subscription information, including contract information and pricing details. However, the subscriptions beneficiary will see limited subscriptions information. For example, no contract information and Pricing Details will be displayed. For more information on the backend configuration, see [Configuring and Enabling Customer Product Inventory](#configuring-and-enabling-customer-product-inventory). + +**Subscriptions Beneficiary:** + +

+ +**Subscriptions Owner:** + +

+ +### Viewing the Usage Consumption of a Subscribed Product in Pie Charts + +1. From the **Account** menu drop-down, click **Subscriptions**. All subscriptions are displayed. +2. Click **Usage Details**. The usage consumption for a subscribed product is displayed in pie charts. +3. Click **Go back to the Subscriptions** to navigate to the My Subscriptions page. + +

+ +### Viewing Subscribed Products in a Grid or a Tabular Format + +1. From the **Account** menu drop-down, click **Subscriptions**. All subscriptions are displayed. +2. Click **Usage Details**. The usage consumption for a subscribed product is displayed in a grid or a tabular format. +3. Click **Go back to the Subscriptions** to navigate to the My Subscriptions page. + +**Note:** The graphical representation of the usage consumption in the pie charts is displayed in a grid or a tabular format. + +

+ +## Requirements and Dependencies + +### Frontend Requirements and Dependencies + +There are no frontend requirements and dependencies for this feature. + +### Backend Requirements and Dependencies + +For more information, see [Customer Product Inventory](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/612f26c3d5f14248965ad908cf5952f6.html) in the TUA Help portal. + +### Supported Backed Functionality + +Customer Product Inventory feature involves mapping between subscriptions and users, covering the customer and billing account. It holds the data around a customer and their subscriptions. For more information, see TUA [Product Catalog](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/552515309dd545e7b7878eb081b56453.html) and [Customer Product Inventory](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/612f26c3d5f14248965ad908cf5952f6.html) in the TUA Help Portal. + +| Entity Exposed for CPI |TM Forum API |Description | +|----------------|-------------------------------|-----------------------------| +|TmaSubscriptionBase|[GET/subscriptionBase](https://help.sap.com/doc/c280898e0829413d838559088d5e4b5f/2007/en-US/index_TMF_V2.html#_listsubscriptionbase) |The API displays a list of retrieves the list of SubscriptionBase resources that a customer has access to | +|TmaSubscribedProduct |[GET /product/{productId}](https://help.sap.com/doc/c280898e0829413d838559088d5e4b5f/2007/en-US/index_TMF_V2.html#_productget) |The API displays details of a subscribed product | +|TmaSubscriptionUsage |[GET /usageConsumptionReport](https://help.sap.com/doc/c280898e0829413d838559088d5e4b5f/2007/en-US/index_TMF_V2.html#_usageconsumptionreportfind)| The API requests the calculation of a new usage consumption report for a subscribed product ||| + +## Configuring and Enabling Customer Product Inventory + +In progress. + +### Components + +In progress. + +### Sample Data + +In progress. + +## Further Reading + +Consult the TUA Help Portal for more information on the following topics: + +- [TM Forum APIs](https://help.sap.com/viewer/f59b0ac006d746caaa5fb599b4270151/2007/en-US/d46b30b30eca4d4d8ddd20ad833d77f9.html) diff --git a/_pages/telco/getting-started-with-tua-spartacus.md b/_pages/telco/getting-started-with-tua-spartacus.md new file mode 100644 index 000000000..9bedc7c45 --- /dev/null +++ b/_pages/telco/getting-started-with-tua-spartacus.md @@ -0,0 +1,8 @@ +--- +title: Getting Started with TUA Spartacus +--- + +Welcome to telco and utilities accelerator for project "Spartacus" (TUA Spartacus). TUA Spartacus is a ready-to-use web framework, designed to maximize average revenue per user through cost effective, streamlined process. TUA Spartacus provides all the functionality and business tools that are required to build an omnichannel e-Commerce solution, supporting the unique and individual needs of subscription-based businesses, including telecommunications, utilities, and media. + +- [Installing SAP Commerce Cloud for use with TUA Spartacus]({{ site.baseurl }}{% link _pages/telco/installing-sap-commerce-for-tua-spartacus.md %}) +- [Building the TUA Spartacus Storefront from Libraries]({{ site.baseurl }}{% link _pages/telco/building-the-tua-storefront-from-libraries.md %}) diff --git a/_pages/telco/installation-guide-for-tua-spartacus.md b/_pages/telco/installation-guide-for-tua-spartacus.md new file mode 100644 index 000000000..9b02e3306 --- /dev/null +++ b/_pages/telco/installation-guide-for-tua-spartacus.md @@ -0,0 +1,8 @@ +--- +title: Installation Guide for TUA Spartacus +--- + +Learn how to set up TUA Spartacus on your local machine. The instructions in the following topics describe how to install and configure TUA Spartacus and build the TUA Spartacus storefront from Libraries. + +* Installing SAP Commerce with TUA for use with Spartacus. +* Building the Spartacus Storefront for TUA from Libraries. diff --git a/_pages/telco/installing-sap-commerce-for-tua-spartacus.md b/_pages/telco/installing-sap-commerce-for-tua-spartacus.md new file mode 100644 index 000000000..79fb47942 --- /dev/null +++ b/_pages/telco/installing-sap-commerce-for-tua-spartacus.md @@ -0,0 +1,373 @@ +--- +title: Installing SAP Commerce for use with TUA Spartacus +--- + +The following instructions describe how to install and configure SAP Commerce (release 1905) with Telco & Utilities Accelerator (release 2003, latest patch) for use with a TUA Spartacus storefront. In these instructions, SAP Commerce and Telco & Utilities Accelerator are installed on your local computer, so `localhost` is used in the browser URLs. + +The installation procedure includes steps for creating and using a `b2c_telco_spa` recipe that makes use of the TUA Spartacus Sample Data (`b2ctelcospastore`), but you can use you own sample data or recipe as long as it includes the `cmsoccaddon`, `ycommercewebservices`, `acceleratorwebservicesaddon` extensions and TUA module. + +**Note:** If you are trying out TUA Spartacus for the first time and intend to use the default sample data, you must use the TUA Spartacus Sample Data store extension (should be part of your list of extensions). The TUA Spartacus Sample Data is a set of data (product offerings and content) for the telco industry. + +However, installing the TUA Spartacus Sample Data is not required in all cases. The TUA Spartacus layout is CMS driven as much as possible, but there are a few areas where the CMS structure does not provide enough information. To address this, TUA Spartacus includes a layout configuration that provides additional information for the layout rendering of the CMS content (specifically, the order of the page slots). This configuration is provided in the `TmaB2cStorefrontModule`. It is important to understand that this specific configuration is tightly coupled to the TUA Spartacus sample data, and that whenever you change the sample data (something that happens in all projects), you should introduce your own layout configuration. When you are ready to introduce your own layout configuration, do not import the `TmaB2cStorefrontModule`, but instead, use the `StorefrontModule` that does not provide any layout configuration. The `StorefrontModule` is not dependent on the TUA Spartacus sample data, and is most likely a good starting point for your custom project. + +To install and configure SAP Commerce for use with TUA Spartacus, you must complete the following procedures: + +1. [Setting up SAP Commerce with Telco & Utilities Accelerator](#setting-up-sap-commerce-with-telco--utilities-accelerator) +2. [Configuring OCC credentials](#configuring-occ-credentials) +3. [Configuring CORS](#configuring-cors) + +## Setting Up SAP Commerce with Telco & Utilities Accelerator + +Some of the steps in this procedure are derived from the documentation for installing SAP Commerce using recipes. For more information, see [Installing SAP Commerce Using Installer Recipes](https://help.sap.com/viewer/a74589c3a81a4a95bf51d87258c0ab15/latest/en-US/8c46c266866910149666a0fe4caeee4e.html) in the SAP Help Portal. + +1. Unzip the SAP Commerce and Telco & Utilities Accelerator zip archives. + + Note: Use the lastest patches for SAP Commerce version 1905 and Telco & Utilities Accelerator version 2003. + +1. [Download](https://github.com/SAP/spartacus-tua/releases) the TUA Spartacus Sample Data Store Extension. + + The TUA Spartacus Sample Data Store Extension is the extension provided in the following zip file: `b2ctelcospastore.zip`. + + + +1. Unzip the `b2ctelcospastore.zip` archive. + +1. Move the `b2ctelcospastore` folder to `sap-commerce-folder>/hybris/bin/modules/ b2c-telco-accelerator`. + + The `b2ctelcospastore` folder can be stored anywhere in the `modules` folder. The `b2c-telco-accelerator` folder is chosen as it contains other TUA sample data. + +1. In the `sap-commerce-folder>/installer/recipes` folder, duplicate the `b2c_telco` folder. + +1. Rename the copy of the `b2c_telco` folder to `b2c_telco_spa`. + +1. In `b2c_telco_spa`, the `build.gradle` file should have the following content: + + ```java + apply plugin: 'installer-platform-plugin' + apply plugin: 'installer-addon2-plugin' + + def pl = platform { + + localProperties { + property 'kernel.events.cluster.jgroups.channel', 'disable' + property 'datahub.publication.saveImpex', '' + property 'commerceservices.default.desktop.ui.experience', 'responsive' + property 'kernel.autoInitMode', 'update' + property 'installed.tenants', 'junit, api, foo' + + } + afterSetup { + ensureAdminPasswordSet() + } + + extensions { + extName 'acceleratorcms' + extName 'adaptivesearchbackoffice' + extName 'adaptivesearchsolr' + extName 'addonsupport' + extName 'b2ctelcobackoffice' + extName 'b2ctelcofulfillmentprocess' + extName 'b2ctelcospastore' + extName 'b2ctelcoaddon' + extName 'b2ctelcotmfwebservices' + extName 'b2ctelcowebservices' + + extName 'b2ctelcooccaddon' + extName 'commerceservicesbackoffice' + extName 'solrfacetsearchbackoffice' + extName 'solrserver' + extName 'subscriptionbackoffice' + extName 'yacceleratorstorefront' + extName 'yacceleratorcore' + extName 'ycommercewebservices' + extName 'pcmbackofficesamplesaddon' + + extName 'cmsbackoffice' + extName 'cmswebservices' + extName 'previewwebservices' + extName 'smarteditwebservices' + extName 'cmssmarteditwebservices' + extName 'permissionswebservices' + extName 'smarteditaddon' + extName 'cmssmartedit' + extName 'cmsoccaddon' + extName 'customerticketingaddon' + extName 'customersupportbackoffice' + + extName 'personalizationwebservices' + extName 'previewpersonalizationweb' + extName 'personalizationcmsweb' + extName 'personalizationsmartedit' + extName 'personalizationservicesbackoffice' + extName 'personalizationcmsbackoffice' + extName 'personalizationservices' + extName 'personalizationfacades' + + extName 'acceleratorservices' + extName 'assistedservicefacades' + extName 'assistedservicestorefront' + extName 'assistedservicecustomerinterestsaddon' + + extName 'rulebuilderbackoffice' + extName 'couponbackoffice' + extName 'droolsruleengineservices' + extName 'couponfacades' + extName 'couponservices' + extName 'promotionenginesamplesaddon' + extName 'acceleratorwebservicesaddon' + + } + addons { + forStoreFronts('yacceleratorstorefront') { + names('b2ctelcoaddon', 'smarteditaddon', 'customerticketingaddon', 'assistedservicestorefront', 'assistedservicecustomerinterestsaddon', 'pcmbackofficesamplesaddon', 'promotionenginesamplesaddon') + template 'yacceleratorstorefront' + } + + forStoreFronts('ycommercewebservices') { + names('b2ctelcooccaddon','cmsoccaddon','acceleratorwebservicesaddon') + template 'ycommercewebservices' + + } + + } + } + + task setup () { + doLast { + + pl.setup() + + copy { + from "${installerHome}/recipes/b2c_telco_spa/logback.xml" + into "${suiteHome}/hybris/bin/platform/tomcat/lib" + } + copy { + from "${installerHome}/recipes/b2c_telco_spa/sbg_properties" + into "${suiteHome}/hybris/bin/platform/tomcat/lib" + exclude "**/*.txt" + } + } + } + + task buildSystem(dependsOn: setup) { + doLast { + pl.build() + } + } + + task initialize (dependsOn: buildSystem) { + doLast { + pl.initialize() + } + } + + task start () { + doLast { + pl.start() + } + } + + task startInBackground () { + doLast { + pl.startInBackground() + } + } + + task stopInBackground { + doLast { + pl.stopInBackground() + } + } + ``` + +1. Open a terminal or command prompt window inside the `sap-commerce-folder>/installer` folder. + +1. Set up the recipe using the following commands for Windows: + + ```bash + install.bat -r b2c_telco_spa -A local_property:initialpassword.admin=Y0urFav0r!tePassw0rd + ``` +For Unix: + + ```bash + ./install.sh -r b2c_telco_spa -A local_property:initialpassword.admin=Y0urFav0r!tePassw0rd + ``` + + + + **Note:** Starting with release 1905, SAP Commerce releases do not ship with a default admin password. You must specify a password when running recipe commands (as shown above), or you can specify a password in a file named `custom.properties` stored in `sap-commerce-folder>\installer\customconfig`. See the [Alternate Method for Setting the SAP Commerce Admin Password](#alternate-method-for-setting-the-sap-commerce-admin-password) procedure below for information on setting a password in the `custom.properties` file. + +1. Initialize the system using the following command. From the `sap-commerce-folder>/installer` folder run the following commands for Windows: + + ```bash + install.bat -r b2c_telco_spa -A local_property:initialpassword.admin=Y0urFav0r!tePassw0rd initialize + ``` +For Unix: + + ```bash + ./install.sh -r b2c_telco_spa -A local_property:initialpassword.admin=Y0urFav0r!tePassw0rd initialize + ``` + + Initialization of the b2c_telco_spa recipe can take about 20 minutes. Sample data for this recipe includes telco specific data and content. + +1. Start SAP Commerce with the following command. From the `sap-commerce-folder>/installer` folder run the following commands for Windows: + + ```bash + install.bat -r b2c_telco_spa -A local_property:initialpassword.admin=Y0urFav0r!tePassw0rd start + ``` +For Unix: + + ```bash + ./install.sh -r b2c_telco_spa -A local_property:initialpassword.admin=Y0urFav0r!tePassw0rd start + ``` + +1. Verify that the system is working. + + - Access Admin Console: https://localhost:9002 + - Access Backoffice: https://localhost:9002/backoffice + + + **Note:** When setting up your TUA Spartacus storefront, set the base site in `app.module.ts` to `telcospa`. The following is an example: + + ```ts + context: { + baseSite: ['telcospa'] + }, + ``` + +## Configuring OCC Credentials + +By default, SAP Commerce replies to OCC REST API calls that do not require authentication. For example, you can do the following: + +- Display Open API documentation: https://localhost:9002/rest/v2/swagger-ui.html +- Display information about the `telcospa` base store: https://localhost:9002/rest/v2/telcospa/basestores/telcospa + +In order to register users and check out, SAP Commerce must be configured with a client ID and password. When required, your TUA Spartacus storefront sends this client ID and password when communicating with the backend. +For more information about OCC configuration, see [Defining OAuth Clients in an Impex File](https://help.sap.com/viewer/d0224eca81e249cb821f2cdf45a82ace/latest/en-US/627c92db29ce4fce8b01ffbe478a8b3b.html#loio4079b4327ac243b6b3bd507cda6d74ff) in the SAP Help Portal. + +The following procedure describes how to configure SAP Commerce to accept OCC REST API calls. + +1. Open the Hybris Administration Console in a web browser at the following address: `https://localhost:9002`. + +2. Hover your mouse over the **Console** tab, then click **Impex Import**. + +3. Copy-paste the following code into the **Import content** field. + + ```sql + INSERT_UPDATE OAuthClientDetails;clientId[unique=true] ;resourceIds ;scope ;authorizedGrantTypes ;authorities ;clientSecret ;registeredRedirectUri + ;client-side ;hybris ;basic ;implicit,client_credentials ;ROLE_CLIENT ;secret ;http://localhost:9001/authorizationserver/oauth2_implicit_callback; + ;mobile_android ;hybris ;basic ;authorization_code,refresh_token,password,client_credentials ;ROLE_CLIENT ;secret ;http://localhost:9001/authorizationserver/oauth2_callback; + ``` + + When you import this sample (which is the same as the sample that is provided in the SAP Commerce documentation), you add the following client ID and password: + + - client ID: `mobile_android` + - password (or secret): `secret` + + **Note:** The values for client ID and password are just samples. You would use different values for your production environments. + +4. Click the **Import content** button. + + You have now added a client ID and password to your TUA Spartacus storefront configuration. + +5. You can verify that the OAuth client has been successfully defined by entering the following curl command in a terminal or command prompt window: + + ```bash + curl -k -d "client_id=mobile_android&client_secret=secret&grant_type=client_credentials" -X POST https://localhost:9002/authorizationserver/oauth/token + ``` + + The curl command sends a POST request for an access token, using the client ID and password that you added to the backend. The command should return something similar to the following: + + ```bash + { + "access_token" : "550d9a25-87c8-4e76-af21-6174a1e56d5c", + "token_type" : "bearer", + "expires_in" : 41809, + "scope" : "basic openid" + } + ``` + +**You can now start TUA Spartacus!** After you have configured SAP Commerce to accept OCC REST API calls, you can set up and start your storefront. See [Building the TUA Spartacus Storefront from Libraries]({{ site.baseurl }}{% link _pages/telco/building-the-tua-storefront-from-libraries.md %}) for more information. + +## Configuring CORS + +CORS (Cross-Origin Resource Sharing) defines a way for a browser and a server to decide which cross-origin requests for restricted resources can or cannot be allowed. Certain TUA Spartacus functionality, such as checkout and consent management, may not work properly if the CORS OCC REST API settings are not configured properly in SAP Commerce. + +You can add these settings using the Hybris Administration Console. Hover your mouse over the **Platform** tab, click **Configuration**, then update the CORS settings. + +To configure CORS settings for OCC REST APIs, add the following to your SAP Commerce configuration (`local.properties` file of your config folder): + +```sql +corsfilter.ycommercewebservices.allowedOrigins=http://localhost:4200 https://localhost:4200 +corsfilter.ycommercewebservices.allowedMethods=GET HEAD OPTIONS PATCH PUT POST DELETE +corsfilter.ycommercewebservices.allowedHeaders=origin content-type accept authorization cache-control if-none-match x-anonymous-consents +``` + +```sql +corsfilter.b2ctelcotmfwebservices.allowedOrigins=http://localhost:4200 +https://localhost:4200 +corsfilter.b2ctelcotmfwebservices.allowedMethods=GET HEAD OPTIONS PATCH PUT POST DELETE +corsfilter.b2ctelcotmfwebservices.allowedHeaders=origin content-type accept authorization cache-control if-none-match x-anonymous-consents +``` + +```sql +corsfilter.acceleratorservices.allowedOrigins=http://localhost:4200 https://localhost:4200 +corsfilter.acceleratorservices.allowedMethods=GET HEAD OPTIONS PATCH PUT POST DELETE +corsfilter.acceleratorservices.allowedHeaders=origin content-type accept authorization cache-control +``` + +**Note:** The `x-anonymous-consents` custom header is included in the above example, but it can be removed if you plan to disable the anonymous consent feature. However, do not remove this header if you do not plan to disable the anonymous consent feature. For more information, see [Anonymous Consent]({{ site.baseurl }}{% link _pages/dev/features/anonymous-consent.md %}). + +For more information about CORS, see [ycommercewebservices Extension](https://help.sap.com/viewer/9d346683b0084da2938be8a285c0c27a/latest/en-US/8c91f3a486691014b085fb11c44412ff.html) in the SAP Help Portal. + +## Alternate Method for Setting the SAP Commerce Admin Password + +Instead of including the admin password in every install command as required for release 1905, you can create a configuration file that is used each time. + +1. Create a file named `custom.properties` inside the `installer/customconfig` folder of your SAP Commerce folder. + +2. Add the following line: `initialpassword.admin=Y0urFav0r!tePassw0rd` + + Change `Y0urFav0r!tePassw0rd` to the password you'd like to use. + +3. Save the file. + +The next time you run the recipe install command, the settings inside `custom.properties` are used to build the `local.properties` file, and there's no need to include `-A local_property:initialpassword.admin=Y0urFav0r!tePassw0rd`. + +## Supporting Regions in the Billing Address + +A specific configuration can be entered if the payment provider requires the `regions` field as part of the billing address data. + +TUA Spartacus automatically picks up on the configuration and displays the `regions` field in the form. + +1. If you do not have a `custom.properties` file, create a file named `custom.properties` inside the `installer/customconfig` folder of your SAP Commerce folder. + +2. Add the following line to your `custom.properties` file: + + ``` + mockup.payment.label.billTo.region=billTo_state + ``` + +3. Save the file. + +The next time you run the recipe install command, the settings inside `custom.properties` are used to build the `local.properties`. + +**Note:** If you wish this configuration to be present without reinstalling, you can add the property to your `local.properties` file. + +## Possible Issues + +### Failure at the Payment Step in Checkout + +You may encounter the following error message: + +``` +POST http://localhost:4200/acceleratorservices/sop-mock/process 404 (Not Found) +``` + +This issue is caused by an incorrect configuration of the `sop.post.url` property. + +Make sure this property is set to `sop.post.url=https://localhost:9002/acceleratorservices/sop-mock/process`. + +**Note:** Please make sure that you have the website properties properly set for your `telcospa` base site to point to your environment. For your **localhost** environment they should have the following values: +`website.telcospa.http=http://localhost:9001` +`website.telcospa.https=https://localhost:9002` \ No newline at end of file diff --git a/_pages/telco/journey-management-appointment.md b/_pages/telco/journey-management-appointment.md new file mode 100644 index 000000000..444289e69 --- /dev/null +++ b/_pages/telco/journey-management-appointment.md @@ -0,0 +1,142 @@ +--- +title: Journey Management - Appointment Reference +--- + +**Note:** This feature is introduced in version 1.1.0 of the TUA Spartacus libraries. + +## Contents + +- [Overview](#overview) +- [Key Personas](#key-personas) +- [Business Use Case](#business-use-case) +- [Navigation Flow](#navigation-flow) +- [Requirements and Dependencies](#requirements-and-dependencies) +- [Configuring and Enabling New Appointment](#configuring-and-enabling-new-appointment) +- [Further Reading](#further-reading) + +## Overview + +The `Journey Management - Appointment Reference` feature enables customers browsing the telco and utilities accelerator for project "Spartacus" (TUA Spartacus) storefront to browse the content of a product offering, and select a suitable appointment for arranging onsite service support, before purchasing the product offering. + +**Note:** The `Journey Management - Appointment Reference` feature applies to only those product or service offerings for which a checklist policy is configured at the backend by the Product Manager. + +## Key Personas + +- Customers +- Product Managers + +## Business Use Case + +A customer wants to purchase a product offering. Before adding the product offering to the cart, the `Select a suitable time for an appointment` screen is displayed, based on the checklist policy configured at the backend by the Product Manager. The customer is required to select a `call to schedule` option, or a suitable appointment from the available appointments. + +The business use case includes the following steps: + +1. The customer searches and selects a product offering; for example, Fiberlink 100, and clicks **Add to Cart** to add the product offering to the cart. +2. The `Select a suitable time for an appointment` screen is displayed, based on the checklist actions configured at the backend by Product Manager. The `Select a suitable time for an appointment` screen displays: + - **Call to Schedule:** The customer can select this option if a call back is required to schedule an appointment. + - **Select a Suitable Appointment:** The customer can select a suitable appointment from the available appointments. +3. The selected product offering with the appointment is added to the cart. +4. The customer can edit the appointment before proceeding to checkout the product offering. +5. The customer can view view the appointment and the order details from the `Order Details` page or the `Order History` page. + +## Navigation Flow + +1. Log in to the Telco SPA. + +

+ +2. Search and select a product offering. For example, Fiber Link 100 mbps. + +

+ +3. Click **Add to Cart**. The `Select a suitable time for an appointment` screen is displayed, based on the checklist policy configured at the backend by the Product Manager. + + **Note:** The `Please Call to Schedule` option is preselected. + +4. Click a suitable appointment from the available appointments. + +

+ +5. Click **CONTINUE**. The appointment is displayed in the `Item(s) added to your cart` screen. + +

+ +6. Click **View Cart**. The cart displays all relevant details of the product offering (Fiber Link) with the appointment. + +

+ +7. Click the pencil icon to edit or update the appointment. The `Select a suitable time for an appointment` screen is displayed. + +

+ + **Notes:** + - The earlier selected appointment is displayed by default and the **UPDATE** button is disabled, until you select a new time slot from the available appointments. + - Top five available time slots are displayed with the default `Please call to Schedule` option. + - For each cart entry, you can book only one time slot, or choose the default option `Call to Schedule'. + +8. Select a suitable appointment and click **Update**. The cart page displays the new appointment. + +

+ +9. Click **Proceed to Checkout** to buy the product offering. + +## Requirements and Dependencies + +### Frontend Requirements and Dependencies + +Your Angular development environment should include the following: + +The `Ngx-spinner` library, version 8.03 for Angular CLI 8.0. The `Ngx-spinner` library is available: + +Using npm: + + ```bash + $ npm install ngx-spinner --save + ``` + +Using yarn: + + ```bash + $ yarn add ngx-spinner + ``` + +### Backend Requirements and Dependencies + +In progress. + +### Supported Back End Functionality + +- [Product Catalog](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/552515309dd545e7b7878eb081b56453.html). +- [Telco & Utilities Accelerator Data Model for entities exposed Via TMF and OCC APIs](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/552515309dd545e7b7878eb081b56453.html). +- [Telco & Utilities Accelerator Checklist](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/552515309dd545e7b7878eb081b56453.html). + +| Entity Exposed | TMF & OCC APIs | Remark | Request or Response | +|- |- |- |- | +| Tmf Resources#TMF-ChecklistActionAPI | /checklistAction | To show applicable list of checklist policies for product offering | None | +| TMF-646 (version 2.0.0) | POST appointment/searchTimeSlot | The TM Forum API creates a search time slot entity. As per the set of criteria, this entity retrieves available time slots to book or reschedule an appointment. | **Response (200 OK):**
[
{
""id"": ""a9d239bb-dc21-4f98-a519-4a3f9aa4d2b5"",
""href"": ""https://api-appointment-v4-0-0.mybluemix.net/tmf-api/appointment/v4/searchTimeSlot/a9d239bb-dc21-4f98-a519-4a3f9aa4d2b5"",
""@schemaLocation"": ""https://api-appointment-v4-0-0.mybluemix.net/docs/#/"",
""@type"": ""SearchTimeSlot"",
""@baseType"": ""SearchTimeSlot"",
""creationDate"": ""2020-03-12T14:07:01.889Z"",
""status"": ""initialized"",
""availableTimeSlot"": [
{
""id"": ""365"",
""href"": ""https://host:port/appointment/searchtimeslot/99/availableTimeSlot/365"",
""validFor"": {
""startDateTime"": ""2020-08-28T14:00:00.000Z"",
""endDateTime"": ""2020-08-28T16:00:00.000Z""
},
""relatedParty"": {
""id"": ""56"",
""href"": ""https://host:port/partyManagement/individual/56"",
""name"": ""John Doe"",
""role"": ""technician"",
""@referredType"": ""Individual""
}
},
{
""id"": ""921"",
""href"": ""https://host:port/appointment/searchtimeslot/99/availableTimeSlot/921"",
""validFor"": {
""startDateTime"": ""2020-08-28T16:30:00.000Z"",
""endDateTime"": ""2018-08-28T18:00:00.000Z""
},
""relatedParty"": {
""id"": ""56"",
""href"": ""https://host:port/partyManagement/individual/56"",
""name"": ""John Doe"",
""role"": ""technician"",
""@referredType"": ""Individual""
}
},
{
""id"": ""325"",
""href"": ""https://host:port/appointment/searchtimeslot/99/availableTimeSlot/325"",
""validFor"": {
""startDateTime"": ""2020-08-28T18:30:00.000Z"",
""endDateTime"": ""2020-08-28T19:00:00.000Z""
},
""relatedParty"": {
""id"": ""58"",
""href"": ""https://host:port/partyManagement/individual/58"",
""name"": ""Adam Smith"",
""role"": ""technician"",
""@referredType"": ""Individual""
}
}
]
},
{
""id"": ""a9d239bb-dc21-4f98-a519-4a3f9aa4d2b5"",
""href"": ""https://api-appointment-v4-0-0.mybluemix.net/tmf-api/appointment/v4/searchTimeSlot/a9d239bb-dc21-4f98-a519-4a3f9aa4d2b5"",
""@schemaLocation"": ""https://api-appointment-v4-0-0.mybluemix.net/docs/#/"",
""@type"": ""SearchTimeSlot"",
""@baseType"": ""SearchTimeSlot"",
""creationDate"": ""2020-03-12T14:07:01.889Z"",
""status"": ""initialized"",
""availableTimeSlot"": [
{
""id"": ""365"",
""href"": ""https://host:port/appointment/searchtimeslot/99/availableTimeSlot/365"",
""validFor"": {
""startDateTime"": ""2020-08-29T14:00:00.000Z"",
""endDateTime"": ""2020-08-29T16:00:00.000Z""
},
""relatedParty"": {
""id"": ""56"",
""href"": ""https://host:port/partyManagement/individual/56"",
""name"": ""John Doe"",
""role"": ""technician"",
""@referredType"": ""Individual""
}
},
{
""id"": ""921"",
""href"": ""https://host:port/appointment/searchtimeslot/99/availableTimeSlot/921"",
""validFor"": {
""startDateTime"": ""2020-08-29T16:30:00.000Z"",
""endDateTime"": ""2020-08-29T18:00:00.000Z""
},
""relatedParty"": {
""id"": ""56"",
""href"": ""https://host:port/partyManagement/individual/56"",
""name"": ""John Doe"",
""role"": ""technician"",
""@referredType"": ""Individual""
}
}
]
}
]" | +| TMF-646 | POST /appointment | To create an appointment for the customer | **Request:**
{
""validFor"": {
""startDateTime"": ""2020-08-28T14:00:00.000Z"",
""endDateTime"": ""2020-08-28T16:00:00.000Z""
}

}

**Response (201 Created):**

""validFor"": {
""startDateTime"": ""2020-08-28T14:00:00.000Z"",
""endDateTime"": ""2020-08-28T16:00:00.000Z""
},
""id"": ""appointment-test-1"",
""href"": ""https://localhost:8080/tmf-api/appointment/v4/appointment/appointment-test-1"",
""lastUpdate"": ""2020-08-06T11:41:59.054Z"",
""@schemaLocation"": ""https://localhost:8080/docs/#/"",
""@type"": ""Appointment"",
""@baseType"": ""Appointment"",
""creationDate"": ""2020-08-06T11:41:59.054Z"",
""status"": ""initialized""
}" | +| TMF-646 | GET /appointment/{id} | To fetch the appointment details of a customer | Response : (200 OK)

{
"validFor": {
"startDateTime": "2020-08-28T14:00:00.000Z",
"endDateTime": "2020-08-28T16:00:00.000Z"
},
"id": "appointment-test-1",
"href": "https://localhost:8080/tmf-api/appointment/v4/appointment/appointment-test-1",
"lastUpdate": "2019-08-21T12:11:13.683Z",
"@schemaLocation": "https://api-appointment-v4-0-0.mybluemix.net/docs/#/",
"@type": "Appointment",
"@baseType": "Appointment",
"creationDate": "2019-08-21T12:11:13.683Z",
"status": "initialized"
} | +| TMF-646 | PATCH /appointment/{id} | Update the appointment details of a customer | **Request:**
{
""""validFor"""": {
""""startDateTime"""": """"2020-08-28T16:00:00.000Z"""",
""""endDateTime"""": """"2020-08-28T18:00:00.000Z""""
}
}

**Response (200 OK):**
{
""""validFor"""": {
""""startDateTime"""": """"2020-08-28T16:00:00.000Z"""",
""""endDateTime"""": """"2020-08-28T18:00:00.000Z""""
},
""""id"""": """"appointment-test-1"""",
""""href"""": """"https://localhost:8080/tmf-api/appointment/v4/appointment/appointment-test-1"""",
""""lastUpdate"""": """"2020-08-06T11:41:59.054Z"""",
""""@schemaLocation"""": """"https://localhost:8080/docs/#/"""",
""""@type"""": """"Appointment"""",
""""@baseType"""": """"Appointment"""",
""""creationDate"""": """"2020-08-06T11:41:59.054Z"""",
""""status"""": """"initialized""""
}""" | + +## Configuring and Enabling the Appointment Reference + +In progress. + +### Components + +| Component Name | Status | Description | +| --------------------------------------- | ------ | ----------------------------------------------------------------------------------------------- | +| TmaAppointmentDisplayComponent | New | the component displays the appointment details of an order, order-history, cart summary, and cart popup | | | +| TmaJourneyChecklistAppointmentComponent | New | the component displays the available time slots to the customer | +| TmaJourneyChecklistStepComponent | New | A stepper component that renders the checklist components | + +### Sample Data + +In progress. + +## Further Reading + +Consult the Telco & Utilities Accelerator Help Portal for more information on the following topics: + +- [Checklist Policy](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/b685dbb837ca4ad7b6c86d0bbd8a7fd7.html). +- [Customer Inventory and Cart](https://help.sap.com/viewer/c762d9007c5c4f38bafbe4788446983e/2007/en-US/6d4fed0352f04fb8ba10846024854ea6.html). diff --git a/_pages/telco/journey-management-msisdn.md b/_pages/telco/journey-management-msisdn.md new file mode 100644 index 000000000..4b597a844 --- /dev/null +++ b/_pages/telco/journey-management-msisdn.md @@ -0,0 +1,116 @@ +--- +title: Journey Management - MSISDN +--- + +**Note:** This feature is introduced in version 1.1.0 of the TUA Spartacus libraries. + +## Contents + +- [Overview](#overview) +- [Key Personas](#key-personas) +- [Business Use Case](#business-use-case) +- [Navigation Flow](#navigation-flow) +- [Requirements and Dependencies](#requirements-and-dependencies) +- [Configuring and Enabling MSISDN](#configuring-and-enabling-msisdn) +- [Further Reading](#further-reading) + +## Overview + +The `Journey Management - MSISDN (Mobile Station International Subscriber Directory Number)` feature enables the customers browsing the telco and utilities accelerator for project "Spartacus" (TUA Spartacus) storefront to select an MSISDN, before adding the selected product offering or a service plan to the cart. + +`MSISDN` is a number used to identify a mobile phone number internationally from the available MSISDNs. This number includes a country code and a National Destination Code, which identifies the subscriber's operator. + +**Note:** The `Journey Management - MSISDN` feature applies to only those product offerings or service plans for which a checklist policy is configured at the backend by the Product Manager.. + +## Key Personas + +- **Customers:** Customers who are interested in the product offerings and the different service plans. +- **Product Managers:** Backoffice users who manage the product catalog. + +## Business Use Case + +A customer wants to purchase a service plan. Before adding the chosen service plan to the cart, the `Select Your desired Phone Number` screen is displayed, based on the checklist policy configured at the backend by the Product Manager. The customer is required to select a phone number (MSISDN) from the available phone numbers. + +The business use case includes the following steps: + +1. The customer searches and selects a service plan; for example, Unlimited Starter Plan, and clicks **Add to Cart** to add the selected service plan to the cart. +2. Based on checklist actions configured for MSISDN at the backend by Product Manager, the `Select Your desired Phone Number` screen displays MSISDNs to the customer. +3. The customer selects the desired MSISDN from the available MSISDNs, before adding the service plan to the cart. +4. The selected service plan is added to the cart. +5. The customer can edit the MSISDN before proceeding to checkout the service plan. +6. The customer places an order for the service plan. + +## Navigation Flow + +- Search and select the desired service plan, for example, Unlimited Starter Plan. + +

+ +- Click **Add to Cart**. The `Select Your Desired Phone Number` screen is displayed, based on the checklist policy configured for MSISDN at the backend by the Product Manager. + + **Note:** The first MSISDN is preselected. + +- Click an MSISDN from the available MSISDNs. + +

+ +- Click **CONTINUE**. The selected MSISDN is displayed in the `Item(s) added to your cart` screen. + +

+ +- Click **View Cart**. The cart displays all relevant details of the service plan (Unlimited Starter Plan) with the MSISDN. + +

+ +- Click the pencil icon to edit the MSISDN. The `Select a suitable MSISDN` screen is displayed. +- Select a suitable MSISDN and click **Update**. The cart page displays the updated MSISDN. +- Click **Proceed to Checkout** to purchase the service plan. + +## Requirements and Dependencies + +### Frontend Requirements and Dependencies + +In progress. + +### Backend Requirements and Dependencies + +The checklist policy must be configured to display the MSISDNs screen, for the customer to select the desired MSISDN. + +### Supported Back End Functionality + +- [Product Catalog](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/552515309dd545e7b7878eb081b56453.html). +- [Telco & Utilities Accelerator Data Model for Entities exposed Via TMF and OCC APIs](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/552515309dd545e7b7878eb081b56453.html). +- [Telco & Utilities Accelerator Checklist](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/552515309dd545e7b7878eb081b56453.html). + +| Entity Exposed for Journey Checklist |TMF and OCC API |Description | +|----------------|-------------------------------|-----------------------------| +|TmaSubscriptionBase|[GET/subscriptionBase](https://help.sap.com/doc/c280898e0829413d838559088d5e4b5f/2007/en-US/index_TMF_V2.html#_listsubscriptionbase) |The API displays a list of retrieves the list of SubscriptionBase resources that a customer has access to | +|TmaSubscribedProduct |[GET /product/{productId}](https://help.sap.com/doc/c280898e0829413d838559088d5e4b5f/2007/en-US/index_TMF_V2.html#_productget) |The API displays details of a subscribed product | +|TmaSubscriptionUsage |[GET /usageConsumptionReport](https://help.sap.com/doc/c280898e0829413d838559088d5e4b5f/2007/en-US/index_TMF_V2.html#_usageconsumptionreportfind)| The API requests the calculation of a new usage consumption report for a subscribed product ||| + +## Configuring and Enabling MSISDN + +To configure and enable MSISDN, follow the steps: + +1. Log in to the **Backoffice**. +2. Navigate to **Catalog > Conditional Policies > Policy Statement > Checklist Action Statement > Configurable Psc Checklist Action Statement**. The `Checklist action type` page is displayed. +3. Click the **Checklist Action type**. The details are displayed in the following pane. +4. In the **PROPERTIES** tab, ensure that `MSISDN` is selected as the property in the Checklist Action Type field. +5. In the **Product Offering** field, select the product offering for configuring MSISDN. + +### Components + +| Component Name |Status |Description | +|----------------|-------------------------------|-----------------------------| +|TmaLogicalResourceComponent|New |Interacts with the mock TMF API to fetch details of logical resource | +|TmaLogicalResourceDisplayComponent |New |Displays the LogicalResource in the **Add to Cart** popup, in the **Cart** page and in the **Order** page |[GET /usageConsumptionReport](https://help.sap.com/doc/c280898e0829413d838559088d5e4b5f/2007/en-US/index_TMF_V2.html#_usageconsumptionreportfind)| The API requests the calculation of a new usage consumption report for a subscribed product ||| + +### Sample Data + +In progress. + +## Further Reading + +Consult the Telco & Utilities Accelerator Help Portal for more information on the following topics: + +- [Standardization of the Names of the Service Plans](https://help.sap.com/viewer/62583a7386514befa5d2821f6f9a40e5/2007/en-US/1efef20cf9ab42b59f1bdb9004e67477.html) diff --git a/_pages/telco/release-information-for-tua.md b/_pages/telco/release-information-for-tua.md new file mode 100644 index 000000000..e69de29bb diff --git a/_pages/telco/spartacus-features-for-tua.md b/_pages/telco/spartacus-features-for-tua.md new file mode 100644 index 000000000..9a45bab40 --- /dev/null +++ b/_pages/telco/spartacus-features-for-tua.md @@ -0,0 +1,10 @@ +--- +title: TUA Spartacus Features +--- + +This is a landing page for grouping together TUA Spartacus features. The TUA Spartacus features include the following: + +- Configurable Guided Selling Journey in SPA +- [Customer Product Inventory (CPI)]({{ site.baseurl }}{% link _pages/telco/customer-product-inventory.md %}) +- [Journey Management - MSISDN (Virtual Mobile Number)]({{ site.baseurl }}{% link _pages/telco/journey-management-msisdn.md %}) +- [New Appointment]({{ site.baseurl }}{% link _pages/telco/journey-management-appointment.md %}) diff --git a/_pages/telco/spartacus-tua-faqs.md b/_pages/telco/spartacus-tua-faqs.md new file mode 100644 index 000000000..7aeefcb7a --- /dev/null +++ b/_pages/telco/spartacus-tua-faqs.md @@ -0,0 +1,21 @@ +--- +title: TUA Spartacus FAQs +--- + +This document compiles frequently-asked or interesting questions related to telco and utilities accelerator for project "Spartacus" (TUA Spartacus) as a product, TUA Spartacus development, and TUA Spartacus library development we’ve received from you. + +This document also cover a wide array of questions as a service to customers, stakeholders, and others who are seeking information regarding TUA Spartacus. We hope you find what you’re looking for. + +If you have technical questions and want to contribute your questions in this document, you can get in touch with us on [Stack Overflow](https://stackoverflow.com/questions/tagged/spartacus-storefront). For non-technical questions, you can reach us on our [Slack workspace](https://join.slack.com/t/spartacus-storefront/shared_invite/enQtNDM1OTI3OTMwNjU5LTg1NGVjZmFkZjQzODc1MzFhMjc3OTZmMzIzYzg0YjMwODJiY2YxYjA5MTE5NjVmN2E5NjMxNjEzMGNlMDRjMjU). Feedback welcome! + +**What is Telco & Utilities Accelerator?** + +SAP Commerce Telco & Utilities Accelerator is a ready-to-use web framework, designed to maximize average revenue per user through cost effective, streamlined process. SAP Commerce Industry Accelerators are purpose-built extensions for the SAP Commerce solution that contains industry-specific features. + +The Accelerator provides the essential tools, functionality, and processes to support features needed by these industries. The Accelerator not only jump starts a commerce implementation, but also provides a way to easily build, extend, and deliver a simplified digital experience for their customers. + +The Accelerator provides a future-proof technical foundation for growth, quick time-to-market, and a competitive advantage for delivering more innovative capabilities. For more information, see [SAP Commerce Telco & Utilities Accelerator](https://help.sap.com/viewer/product/TELCO_ACCELERATOR/2007/en-US). + +**The SAP Telco & Utilities Accelerator exposes a TM Forum compliant API layer. Would TUA Spartacus support this?** + +Spartacus uses OCC APIs, which is leveraged in TUA Spartacus. In the TUA SPA library, functionality that is not covered using standard OCC APIs will be covered using TM Forum APIs. There is already support for TM Forum APIs and was delivered with the first TUA library. diff --git a/_pages/telco/telco-checkout.md b/_pages/telco/telco-checkout.md new file mode 100644 index 000000000..65611352f --- /dev/null +++ b/_pages/telco/telco-checkout.md @@ -0,0 +1,7 @@ +--- +title: Telco & Utilities Checkout +--- + +This is a landing page for grouping together Telco and Utilities checkout topics. The Telco & Utilities checkout topics include the following: + +- [Telco Checkout] diff --git a/_pages/telco/telco-release-information.md b/_pages/telco/telco-release-information.md index 000ca8c5a..2cc8d15af 100644 --- a/_pages/telco/telco-release-information.md +++ b/_pages/telco/telco-release-information.md @@ -1,28 +1,9 @@ --- -title: Release Information for Versions 1.0-1.1 of Telco & Utilities Spartacus Libraries +title: Release Information for Version 1.0.0 of TUA Spartacus Libraries --- -This document describes what is included in all Telco & Utilities Spartacus 1.x libraries since 1.0. +*Last updated July 24, 2020 by Deborah Cholmeley-Jones, Solution Owner, TUA Spartacus* -**Note:** Telco & Utilities Spartacus 1.x requires Angular 8. Telco & Utilities Spartacus is not intended to work with Angular 9. -*Last updated May 11, 2020 by Sachin Khasgiwale, Technical Writer, Telco & Utilities Storefront Spartacus* +Release 1.0 is the very first release of the TUA Spartacus libraries, and at this time, we have only pre-releases available for 1.0. To learn more about what our pre-releases have to offer, see [Pre-Release Information]({{ site.baseurl }}{% link _pages/telco/tua-pre-release-information.md %}). -For information on specific code changes for a particular release, see Development Release Notes at . -For information about features published in pre-release libraries, see Pre-Release Information. - -Contents: - -- Introduction -- Release 1.5 -- About Telco & Utilities Storefront Spartacus Releases -- How Telco & Utilities Storefront Spartacus is Versioned -- Future Releases - -## Introduction - -This document describes what is included in the latest releases of Telco & Utilities Spartacus libraries. - -If you have technical questions, you can get in touch with Telco & Utilities Spartacus. For non-technical questions, you can reach us on our Slack workspace. Feedback welcome! - -- [Telco Checkout] \ No newline at end of file diff --git a/_pages/telco/tua-pre-release-information.md b/_pages/telco/tua-pre-release-information.md new file mode 100644 index 000000000..233c3315a --- /dev/null +++ b/_pages/telco/tua-pre-release-information.md @@ -0,0 +1,38 @@ +--- +title: Pre-Release Information +--- +## Release 1.0.0-next.2 - July 24th, 2020 + +This document describes what is included in the latest pre-release of TUA Spartacus libraries, such as `next` and `rc` libraries. + +_Last updated July 24, 2020 by Deborah Cholmeley-Jones, Solution Owner, TUA Spartacus_ + +Aside from continued work on removing deprecated code, bug fixes, and code refactoring, the following sections highlight work that has been done for this pre-release. + +- Product Offering Prices (One-Time Charges, Recurring Charges and Usage Charges). For more information, see [Pricing in TUA Help Portal](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/ad4430d10fc3477096752d83f935faf9.html) in the TUA Help portal. +- Guided selling for complex Bundled Product Offerings. For more information, see [Configurable Guided Selling for BPOs](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/464d4b03d91442e9ac95f69808895a39.html) in the TUA Help portal. + +## Release 1.0.0-next.1 - May 18th, 2020 + +_Last updated May 18, 2020 by Deborah Cholmeley-Jones, Solution Owner, TUA Spartacus_ + +This is the very first pre-release of the Telco & Utilities Accelerator (TUA) Spartacus storefront. TUA Spartacus storefront requires Telco & Utilities Accelerator release 2003 (latest patch), with Spartacus 1.4 libraries. + +With this pre-release, the following TUA storefront features are included: + +- Login +- Customer Registration +- Search +- Support of Simple Product Offerings (SPOs). For more information, see [Support of Simple Product Offerings (SPOs)](https://help.sap.com/viewer/4c33bf189ab9409e84e589295c36d96e/1905/en-US/315410098c024e50adf4c43373761936.html?q=product%20offerings) in the TUA Help portal +- Product Offering Details Page +- Product Offering Listing Page +- Product Offering Pricing. For more information, see [Product Offering Pricing](https://help.sap.com/viewer/4c33bf189ab9409e84e589295c36d96e/1905/en-US/ad4430d10fc3477096752d83f935faf9.html) in the TUA Help portal +- Add Product Offering to Cart +- Checkout +- Order Placement +- My Account standard commerce features +- APIs supporting offer to fulfill including TM Forum APIs and OCC rest APIs + +## Questions + +If you have technical questions, you can get in touch with us on [Stack Overflow](https://stackoverflow.com/questions/tagged/spartacus-storefront). For non-technical questions, you can reach us on our [Slack workspace](https://join.slack.com/t/spartacus-storefront/shared_invite/enQtNDM1OTI3OTMwNjU5LTg1NGVjZmFkZjQzODc1MzFhMjc3OTZmMzIzYzg0YjMwODJiY2YxYjA5MTE5NjVmN2E5NjMxNjEzMGNlMDRjMjU). Feedback welcome! diff --git a/_pages/telco/tua-pre-release-notes-next1.md b/_pages/telco/tua-pre-release-notes-next1.md new file mode 100644 index 000000000..72f559941 --- /dev/null +++ b/_pages/telco/tua-pre-release-notes-next1.md @@ -0,0 +1,38 @@ +--- +title: Pre-Release Information +--- +## Release 1.0.0-next.2 - July 24th, 2020 + +This document describes what is included in the latest pre-release of TUA Spartacus libraries, such as `next` and `rc` libraries. + +_Last updated July 24, 2020 by Deborah Cholmeley-Jones, Solution Owner, TUA Spartacus_ + +Aside from continued work on removing deprecated code, bug fixes, and code refactoring, the following sections highlight work that has been done for this pre-release. + +- Product Offering Prices (One-Time Charges, Recurring Charges and Usage Charges). For more information, see [Pricing in TUA Help Portal](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/ad4430d10fc3477096752d83f935faf9.html) in the TUA Help portal. +- Guided selling for complex Bundled Product Offerings. For more information, see [Configurable Guided Selling for BPOs](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/464d4b03d91442e9ac95f69808895a39.html) in the TUA Help portal. + +## Release 1.0.0-next.1 - May 18th, 2020 + +_Last updated May 18, 2020 by Deborah Cholmeley-Jones, Solution Owner, TUA Spartacus_ + +This is the very first pre-release of the Telco & Utilities Accelerator (TUA) Spartacus storefront. TUA Spartacus storefront requires Telco & Utilities Accelerator release 2003 (latest patch), with Spartacus 1.4 libraries. + +With this pre-release, the following Telco storefront features are included: + +- Login +- Customer Registration +- Search +- Support of Simple Product Offerings (SPOs). For more information, see [Support of Simple Product Offerings (SPOs)](https://help.sap.com/viewer/4c33bf189ab9409e84e589295c36d96e/1905/en-US/315410098c024e50adf4c43373761936.html?q=product%20offerings) in the TUA Help portal +- Product Offering Details Page +- Product Offering Listing Page +- Product Offering Pricing. For more information, see [Product Offering Pricing](https://help.sap.com/viewer/4c33bf189ab9409e84e589295c36d96e/1905/en-US/ad4430d10fc3477096752d83f935faf9.html) in the TUA Help portal +- Add Product Offering to Cart +- Checkout +- Order Placement +- My Account standard commerce features +- APIs supporting offer to fulfill including TM Forum APIs and OCC rest APIs + +## Questions + +If you have technical questions, you can get in touch with us on [Stack Overflow](https://stackoverflow.com/questions/tagged/spartacus-storefront). For non-technical questions, you can reach us on our [Slack workspace](https://join.slack.com/t/spartacus-storefront/shared_invite/enQtNDM1OTI3OTMwNjU5LTg1NGVjZmFkZjQzODc1MzFhMjc3OTZmMzIzYzg0YjMwODJiY2YxYjA5MTE5NjVmN2E5NjMxNjEzMGNlMDRjMjU). Feedback welcome! diff --git a/_pages/telco/tua-spartacus-roadmap.md b/_pages/telco/tua-spartacus-roadmap.md new file mode 100644 index 000000000..c3ce203da --- /dev/null +++ b/_pages/telco/tua-spartacus-roadmap.md @@ -0,0 +1,142 @@ +--- +title: Roadmap for TUA Spartacus +--- + +*Last updated July 24, 2020 by Deborah Cholmeley-Jones, Solution Owner, TUA Spartacus* + +This document describes what is planned for TUA Spartacus for Q2 2020 and later. + +- For an overview of what was included in a specific release, see [Release Information]({{ site.baseurl }}{% link _pages/telco/telco-release-information.md %}). +- For information about features published in pre-release libraries, see [Pre-release Information]({{ site.baseurl }}{% link _pages/telco/tua-pre-release-information.md %}). + +Contents: + +- [Disclaimer - Forward-Looking Statements](#disclaimer---forward-looking-statements) +- [General Release Information](#general-release-information) +- [Planned for Rest of Q3 2020](#planned-for-rest-of-q3-2020) +- [Features planned for the second half of 2020](#features-planned-for-the-second-half-of-2020) +- [Future Outlook](#future-outlook) + +### Disclaimer - Forward-Looking Statements + +*This document contains 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 platform 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.* + +### General Release Information + +We plan to publish new Spartacus libraries every two weeks. Each release may contain bug fixes, improvements to user experience, and new features. + +When new features are available for release, normally we will publish a pre-release “next” version of the libraries with the new features, in order to get feedback. When the final, new, minor version is ready, we usually publish a release candidate (RC), with the final new x.y.0 a few days or weeks later. + +**Note:** Links provided in the following sections point to SAP Commerce Telco & Utilities Accelerator Help portal, to give an idea of what the feature is about. These links are for context-only. While we strive for feature parity, the TUA Spartacus implementation of features may not work exactly as in Accelerator. + +#### Questions? + +If you have technical questions, you can get in touch with us on [Stack Overflow](https://stackoverflow.com/questions/tagged/spartacus-storefront). + +For non-technical questions, you can reach us on our [Slack workspace](https://join.slack.com/t/spartacus-storefront/shared_invite/enQtNDM1OTI3OTMwNjU5LTg1NGVjZmFkZjQzODc1MzFhMjc3OTZmMzIzYzg0YjMwODJiY2YxYjA5MTE5NjVmN2E5NjMxNjEzMGNlMDRjMjU). + +Feedback is welcome! + +### Planned for Rest of Q3 2020 + +The first TUA Spartacus major release (1.0) is planned for early Q3 2020. This release of the TUA Spartacus storefront requires Telco & Utilities Accelerator, release 2003 (latest patch) supported by SAP Commerce 1905, with Angular 8 and Spartacus 1.4 libraries. At a high level, this release includes the overall storefront, the ability to support simple product offerings and bundled product offerings, pricing (one-time charges, recurring charges, and usage charges), and configurable guided selling. + +#### Core B2C TUA Storefront Features/MVP + +- Product Offering Search (Free Text, Facets, Menu). For more information, see [Pricing](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/ad4430d10fc3477096752d83f935faf9.html). +- Product Offering Prices (One-Time Charges, Recurring Charges and Usage Charges). For more information, see [Product Offerings](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/315410098c024e50adf4c43373761936.html). +- Simple Product Offerings (SPOs). For more information, see [Create Simple Product Offering or Bundled Product Offering Prices](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/48680f49f884453f8596488073046631.html). +- Bundled Product Offerings (BPOs). For more information, see [Product Offerings](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/315410098c024e50adf4c43373761936.html). +- Configurable Guided Selling. For more information, see [Configurable Guided Selling](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/fa22e16db2524c0bb9b12c6102ba1b5d.html). + +For more information on how pricing works for One Time Charges, Recurring Charges, and Usage Charges, see [Create Simple Product Offering or Bundled Product Offering Prices](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/48680f49f884453f8596488073046631.html). + +### Features planned for the second half of 2020 + +The items in this section are on our future roadmap - not necessarily for any specific quarter, but order of priority indicates what we’ll tackle first. + +#### My Subscriptions + +For more information on the following topics, click the links of the corresponding topics to view the [TUA Help portal](https://help.sap.com/viewer/product/TELCO_ACCELERATOR/2007/en-US). + +- View list of My Subscriptions - subscribed offerings. For more information, see [View List of my Subscriptions](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/f488da777e9b49c3882eed1b95efd215.html). +- View Consumption Details. For more information, see [View Consumption Details](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/ba5f222fb5814829bd74eaf6e6505a9f.html). +- Manage Product based on role/authorization. For more information, see [Manage Product based on role/authorization](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/1ab69d2074ea4735a68b32b14652d2b9.html). +- Display Product based on role/authorization. For more information, see [Manage Product based on role/authorization](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/1ab69d2074ea4735a68b32b14652d2b9.html). + +#### Retention Process Flows + +- Renewal +- Tariff Change +- Upgrade +- Cross-selling (Add-Ons) + +For more information, see [Eligibility Policies Evaluation](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/7a0412703ebd4cd3b5bd0d882c72c202.html) and [Eligibility Policy in Action](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/341e50fcd20149d68735656c5c1b1fff.html). + +#### Journey Management + +- Journey Coordinator. For more information, see [Journey Coordinator](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/39a59f20c92f4a0090c7ef2d007d623c.html). +- Checkist Actions. For more information, see [Checklist Actions](https://help.sap.com/viewer/c762d9007c5c4f38bafbe4788446983e/2007/en-US/9fead1b7969b425fa1c15fb985324b42.html). + +A new major (2.0) is planned 2H-2020, primarily due to planned support for Angular 9 and the new Ivy rendering engine. Telco & Utilities Accelerator support for 2007 (latest patch) with SAP Commerce 2005 will be supported with 2.0. The release of a new major version of TUA Spartacus means that the code contains breaking changes. + +#### Move to Angular 9/Ivy + +- Move to Angular 9 + - Schematics update for supporting migration + - Third party dependencies updates +- Angular Ivy support (new compilation and rendering pipeline) + - Smaller, simpler, and faster + - Better performance on mobile devices + - Less memory used + - Tree shaking for smaller packages + +#### MVP B2C Features + +- Composite Pricing. For more information, see [Composite Pricing](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/2e0fa8602fff440ba756e1a0a8390ea3.html). +- Price Alterations (Discounts). For more information, see [Price Alterations (Discounts)](https://help.sap.com/viewer/32f0086927f44c9ab1199f1dab8833cd/2007/en-US/61b21155624e4a498632964bc566e1eb.html). +- Grid pricing on Cart, Checkout and Order. For more information, see [Grid pricing on Cart, Checkout and Order](https://help.sap.com/viewer/c762d9007c5c4f38bafbe4788446983e/2007/en-US/91a9faae27bb4a7f8baa46a57078cd61.html). + +#### Stretch Features + +Additional retention scenarios based on contract terms. + +### Future Outlook + +The following features are in roadmap, but currently not planned for a specific quarter. + +B2C Self-Care and Assurance supporting: + +- Sales related process flows +- Assets +- View Bills +- Family Plans - stretch goal + +### B2C Functionality + +The following features are in roadmap, but currently not planned for a specific quarter: + +- Fixed Bundled Product Offerings +- Retention Process Flows + - Cancellation + - Pre-Paid to Post-Paid / Post-Paid to Pre-Paid + - Downgrade + - Merge Accounts + - Split Accounts + - Suspend Subscription + - Activate Service + - Deactivate Service + - Top-up Account +Automatic Cart Assignments +Price Alterations - support for allowances and taxes +Policy based Pricing - stretch goal + +#### B2B Storefront Features in the context of TUA + +- B2B Commerce Org: Also known as My Company management of units, users, budgets, cost centers, purchase threshholds, user groups, approvals. It requires SAP Commerce Cloud 2005. For more information, see [B2B Checkout and Order Process](https://help.sap.com/viewer/4c33bf189ab9409e84e589295c36d96e/latest/en-US/8ac2500f8669101493e69e1392b970fd.html) in the SAP Commerce Cloud documentation. +- B2B Checkout: Includes check out by account, enter purchase order, select cost center, shipping address restricted by cost center chosen, subject to approval process. For more information, see [B2B Checkout and Order Process](https://help.sap.com/viewer/4c33bf189ab9409e84e589295c36d96e/2005/en-US/8ac2500f8669101493e69e1392b970fd.html) in the SAP Commerce documentation. +- Product Configuration: For more information, see [Configurable Products](https://help.sap.com/viewer/9d346683b0084da2938be8a285c0c27a/2005/en-US/478f616a46f84d668f8cd42c0259cdf0.html) in the SAP Commerce documentation. +- B2B Quick Order. For more information, see [B2B Quick Orders](https://help.sap.com/viewer/4c33bf189ab9409e84e589295c36d96e/2005/en-US/caf95981aa174660b3faf839a9dddbef.html) in the SAP Commerce documentation. +- B2B Saved Carts. For more information, see [Multiple Saved Carts](https://help.sap.com/viewer/4c33bf189ab9409e84e589295c36d96e/2005/en-US/caf95981aa174660b3faf839a9dddbef.html) in the SAP Commerce documentation. \ No newline at end of file diff --git a/assets/images/Telco/1MSISDN_Add_to_Cart.png b/assets/images/Telco/1MSISDN_Add_to_Cart.png new file mode 100644 index 000000000..16bb47c41 Binary files /dev/null and b/assets/images/Telco/1MSISDN_Add_to_Cart.png differ diff --git a/assets/images/Telco/1Product_Offering.png b/assets/images/Telco/1Product_Offering.png new file mode 100644 index 000000000..7288b37ab Binary files /dev/null and b/assets/images/Telco/1Product_Offering.png differ diff --git a/assets/images/Telco/2MSISDN_Select_Desired_Phone.png b/assets/images/Telco/2MSISDN_Select_Desired_Phone.png new file mode 100644 index 000000000..5cc66430b Binary files /dev/null and b/assets/images/Telco/2MSISDN_Select_Desired_Phone.png differ diff --git a/assets/images/Telco/2Select_Suitable_Appointment.png b/assets/images/Telco/2Select_Suitable_Appointment.png new file mode 100644 index 000000000..669a9b10d Binary files /dev/null and b/assets/images/Telco/2Select_Suitable_Appointment.png differ diff --git a/assets/images/Telco/3Add_to_Cart.png b/assets/images/Telco/3Add_to_Cart.png new file mode 100644 index 000000000..2bd00d97a Binary files /dev/null and b/assets/images/Telco/3Add_to_Cart.png differ diff --git a/assets/images/Telco/3MSISDN_Items_Added-to_Cart.png b/assets/images/Telco/3MSISDN_Items_Added-to_Cart.png new file mode 100644 index 000000000..ab920f381 Binary files /dev/null and b/assets/images/Telco/3MSISDN_Items_Added-to_Cart.png differ diff --git a/assets/images/Telco/4MSISDN_Proceed_to_Checkout.png b/assets/images/Telco/4MSISDN_Proceed_to_Checkout.png new file mode 100644 index 000000000..7827b4506 Binary files /dev/null and b/assets/images/Telco/4MSISDN_Proceed_to_Checkout.png differ diff --git a/assets/images/Telco/4View_Cart.png b/assets/images/Telco/4View_Cart.png new file mode 100644 index 000000000..7741e5dd3 Binary files /dev/null and b/assets/images/Telco/4View_Cart.png differ diff --git a/assets/images/Telco/5Edit_Cart.png b/assets/images/Telco/5Edit_Cart.png new file mode 100644 index 000000000..1a29bdfd2 Binary files /dev/null and b/assets/images/Telco/5Edit_Cart.png differ diff --git a/assets/images/Telco/6Updated_Appointment.png b/assets/images/Telco/6Updated_Appointment.png new file mode 100644 index 000000000..321ed9639 Binary files /dev/null and b/assets/images/Telco/6Updated_Appointment.png differ diff --git a/assets/images/Telco/Screenshot_2020-09-02 Login.png b/assets/images/Telco/Screenshot_2020-09-02 Login.png new file mode 100644 index 000000000..f989beb79 Binary files /dev/null and b/assets/images/Telco/Screenshot_2020-09-02 Login.png differ diff --git a/assets/images/Telco/navigation-flow.png b/assets/images/Telco/navigation-flow.png new file mode 100644 index 000000000..3de44c5e4 Binary files /dev/null and b/assets/images/Telco/navigation-flow.png differ diff --git a/assets/images/Telco/subscription-beneficiary.png b/assets/images/Telco/subscription-beneficiary.png new file mode 100644 index 000000000..9c70f63c8 Binary files /dev/null and b/assets/images/Telco/subscription-beneficiary.png differ diff --git a/assets/images/Telco/subscription-owner.png b/assets/images/Telco/subscription-owner.png new file mode 100644 index 000000000..c37b4e890 Binary files /dev/null and b/assets/images/Telco/subscription-owner.png differ diff --git a/assets/images/Telco/tabular-format.png b/assets/images/Telco/tabular-format.png new file mode 100644 index 000000000..bf6c8febd Binary files /dev/null and b/assets/images/Telco/tabular-format.png differ diff --git a/assets/images/Telco/usage-consumption.png b/assets/images/Telco/usage-consumption.png new file mode 100644 index 000000000..689fb48f2 Binary files /dev/null and b/assets/images/Telco/usage-consumption.png differ diff --git a/assets/images/Telco/viewing-all-subscriptions.png b/assets/images/Telco/viewing-all-subscriptions.png new file mode 100644 index 000000000..1bdd6e293 Binary files /dev/null and b/assets/images/Telco/viewing-all-subscriptions.png differ