Workshop on 7-April-2025

Screen Sharing and Catalog Data
  • Screen Sharing: Start by sharing data and processes as created and analyzed.
  • Catalog Data Approaches:
    • Daily Dump: Offering a daily dump of the catalog for system loading
    • API Calls: Utilize TMF620 APIs to get catalog data on demand.
API Specifications
  • TMF620 APIs:
    • Define specifications, methods, resources, and filters.
    • TMF620 represents product catalog entities.
Product Offering Selection
  • Catalog Interaction: After fetching product offerings, customers can select offerings and add them to their shopping cart.
  • Posting Selection: Upon selection, create an order posting that retains state in the cart.
  • Cart Modification: Once a cart is created, modifications can be made using PATCH commands (e.g., adding items).
Handling Resources
  • Resource Types:
    • MSISDN (Mobile Station International Subscriber Directory Number)
    • ICCID (Integrated Circuit Card Identifier)
  • Ported MSISDN Handling: If a number is ported, tag it within the system to transition it to a different state.
Resource Management and Availability
  • Querying for Resources:
    • Utilize TMF639 APIs to get resource inventory.
    • Implement filters for resource types (MSISDN or ICCID) based on customer preferences.
  • Dynamic Availability: Implementation of randomization in queries to avoid repeated assignment of the same resource.
  • Atomicity of Resource Assignment: Ensures that two customers cannot obtain the same number simultaneously.
Customer Management and User Registration
  • User Registration Flow:
    • Use Cognito for user sign-up with OTP verification.
    • Confirm registration by verifying OTP.
  • Self-Service User Registration:
    • Link customer service registrations to individual user accounts for ease of access and management.
Customer Types and Data Submission
  • B2C and B2B Customers:
    • Differentiate and manage types of customers for service tracking and billing preferences.
  • Creating Customer Accounts: Necessary to create individual, customer, and billing accounts via APIs for creation of customer profile.
Payment Processing and Cart Submission
  • Checkout Process:
    • Submit the cart to Collect Payments API
  • Handling Abandoned Carts:
    • Monitor for abandoned carts and utilize email/sms notifications for follow-ups.
  • Payment Method Selection: Offer customers the ability to choose their preferred payment method during checkout.
Pipelines and Workflow Management
  • Execution of Pipelines: The implementation will define the tasks needed for order management such as adding, updating, and deleting products.
  • Integration with External Services:
    • Pipelines can interface with external services for payment, inventory checks, delivery, etc.
Validation and Error Handling
  • User/Error Validation: Ensuring customer identity and errors are managed within the customer management systems to prevent duplication.
  • Pipeline Workflow Logic: Must include forwarding responses from external providers, with clear workflows defined for integrations.
Finalize and Share Documentation
  • Preparation for Follow-Up: Ensure that all findings and architectures are documented clearly for updates in next calls.
  • Open Floor for Questions: Encourage participant inquiries to clarify prior discussions, technology integration, and future implementation strategies.