Content Activation (7.1→7.2)

Your team realizes mid-way through the 7.2 content activation wizard that the activation mapping is wrong. Past which step is it too late to change in place, and what single safeguard lets you recover regardless?

You're scheduling the two content-activation processes around the 7.1→7.2 upgrade. One must run before the upgrade; if you defer it, the damage is unrecoverable, not just inconvenient. Which one, and why is the window one-way?

Your BPMon/Analytics objects are still in the legacy (non-MAI) format when you reach content activation. What happens to them, and what's the non-obvious reason it's not just a cosmetic gap?

When modeling for content activation, should you create one logical group per logical component or per application landscape? What single property decides — and why does the intuitive choice backfire?

How many solutions should you create during activation modeling — one, or one per business-process area? When is the exception legitimate, and what gate guards it?

The actual 7.2 content activation is a three-step guided process. List the three steps in order, and the prerequisites that must already be complete before step 1.

Three core concepts were completely redesigned in Solution Manager 7.2, and modeling on the old mental picture corrupts your activation. Which three — and what's the concrete failure if you carry over the pre-7.2 model?

Which Knowledge Warehouse documents silently become inaccessible after the upgrade, and what's the boundary that separates the ones that survive from the ones that don't?

What is the real cost of choosing 'Opt Out' at the first step of content activation — and why is it not a 'do it later' option?

A colleague wants to deselect unneeded content during activation to 'clean house', assuming it gets removed. What actually happens to unselected content, and how should that change the selection criterion?

In the branch table during activation, you want a child branch to have its OWN independent systems rather than inheriting the parent's. What single choice controls this, and which way is which?

Why can neither Basis nor the functional teams complete content-activation modeling alone — and what's the specific failure when one side runs it solo?

A multinational has per-country logical components. The instinct is one LCG per country. Why is that wrong, what's the right model, and what hidden constraint can still block it?

During content activation, what is the single condition that forces you to enable sites via Site Settings — and when is doing so unnecessary (or actively over-configuring)?