Multiplay
by Barbara Pach
1. Multiplay bundle structure adaptions
1.1. Cart structure adaptions
1.2. Rule engines adaptions for hierarchical bundles
1.3. Fulfilment adaptions
2. Check TV availability/feasibility/compatibility
2.1. Anzeige, wieviele SD/HD/UHD Streams beim Kunden möglich sind
2.2. Rules
2.3. Display of possible boxes
3. TV legal texts
3.1. contract
3.1.1. via e-mail to customer
3.1.2. to show
3.1.3. to sign
3.1.3.1. digital sign off on pc monitor (dupos)
3.2. order confirmation
3.3. Auftragsnummer am Vertrag/Inkl Info Auftragsverfolgung
4. Mediaboxes
4.1. Mac Adressen Eingabe für Cash & Carry (falls Cash&Carry in Scope)
4.1.1. Verification of Mac Adresses
4.2. do we have different prices (1st box free/included)?
4.3. PLC Adapter
4.3.1. Mesh
4.4. one product but different SOCs for Billing
4.5. possible number of boxes depends on internet product / speed?
4.6. if first box is not preselected or removable error message is needed "first box is needed for tv"
4.7. ActivationCode
5. Create & Config TV user
5.1. UI user field
5.2. info TV user on contract
5.3. Journey Coordinator API for displaying Config PSC in a generic way
5.4. Kontakt E-Mail Adresse als Empfänger Adresse für Produkt Informationen (Pflichtfeld/optional in verschiedenen Geschäftsfällen)
5.5. Username syntax with error messages
5.5.1. inculding syntax explanation
5.6. relation to the contractmailaddress
5.7. usage of ESB Service IdentityAndAccessManagement mandatory (last flow BRPM-20637)
5.8. Prüfung Mailadresse auf korrekte Struktur
5.9. Anzeige ob Username ein bestehender Mein A1 User oder neu ist
5.9.1. keine Smaus
5.10. Abstimmung Richtung Kirk
5.11. Anziege ob User bereits ein Xplore TV User ist
5.12. syntaxcheck of given string
5.13. Triggering Username and Password Reset E-Mail after Order is sent
5.14. usage of the already existing Parameters (no new names) because of follwing process which relay on them (e.g. PSC_ONE_TV_EMAIL_USER; PSC_EMAIL_ACCOUNT_CREATED, ..)
5.15. if username is printed in contract - no Change of the username should be possible
5.16. Kontaktemail aus PC übernehmen oder neue erstellen und wieder an alle Systeme verteilen
5.17. Configure TV user
6. Regional TV pricing
6.1. Auswirklungen CRM und Aktions IDs für Pricing
6.2. Berechtigungen(Kunde und Verkäufer)/PLZ/Machbarkeit/Zeitraum/
6.3. configuration of regional promotions
6.4. two different taxes 10% and 20% must also be considered at the discounts
6.5. Salzburg Offer
7. API changes
7.1. Adapt ShoppingCart API to support the new structure
7.2. Whitelist additional API Services&Ops
7.3. Volume & Expected Performance
7.4. Adapt ProductOffering API
7.5. Adapt ProductOfferingQualification API
8. Display product information for customer
8.1. basic information from product catalogue
8.2. detailed information/links
8.3. channel lists for tv packages
8.4. use description and classification attributes as product information
8.5. are there any promotions that are not supported yet?
8.6. contract duration
8.7. should stackability of promotions be supported?
8.8. MultiTax - should both net and gross prices be displayed?
9. Configure tv as a bundle
9.1. TV Kombi vs TV Kombi Plus
9.2. included TV Add Ons
10. Configure tv as an add-on
10.1. show tv products (example s-l)
10.2. show product information or difference, like number of channels
11. Configure tv add-ons
11.1. Show tv add-ons in a structured way (eg. first all add-ons with channels, next ethno packages, next SVOD add-ons)
11.2. different promotions for add TV and addOn broadband
12. Put tv product into cart
12.1. Trial Product/ Trial Addon = Testing Product
13. Sky packages
13.1. special connect plus promo
13.2. Pairing code
13.2.1. Verification?