Renewal deal creation for multi-product bundle accounts

Outcome. An account with several active products under one contract end date gets a single renewal deal that lists every product as a line item with its own value, instead of one flat amount that hides what is actually being renewed.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-026

flowchart TD
    A[Customer, Contract End Date < 90 days, 2+ Active Products, no renewal deal yet] --> B[Set Renewal Deal Created = true]
    B --> C[Create renewal deal, associate to company]
    C --> D{Product A active?}
    D -->|Yes| D1[Add Product A line item]
    C --> E{Product B active?}
    E -->|Yes| E1[Add Product B line item]
    C --> F{Product C active?}
    F -->|Yes| F1[Add Product C line item]
    C --> G{Product D active?}
    G -->|Yes| G1[Add Product D line item]
    D1 --> H[Create task for owner: confirm line items]
    E1 --> H
    F1 --> H
    G1 --> H
    H --> I[Notify owner]

When to use it, when not to

• UseUse it on accounts where several products share the same contract end date and renewal event, and the team needs the renewal deal to reflect that composition for accurate line-item reporting.
• UseUse it as the bundle-aware version of renewal-expansion-001, which assumes a single product and a single value.
• SkipDo not use it on accounts whose products renew on different dates; that is a co-termed or multi-contract scenario, closer to renewal-expansion-041's custom object approach or renewal-expansion-050's date-sync pattern.
• SkipDo not use it if products are not tracked as deal line items on the portal at all. Line items require the products tool to be set up first.