Managed package versus core platform installation path
Key Takeaway
Starting with Summer '24, new customers can't get the Agentforce Health managed package, so they install on the core platform and set up person accounts and Omnistudio before specific features.
Agentforce Health began as a managed package, which is an add-on that you install into an org on top of the core Salesforce platform. Over time, Agentforce Health stopped shipping new features through the package and now builds them directly on the core platform. So choosing the installation path starts with one question: did this customer onboard before Summer '24? The answer decides which features a design can rely on.
Which path a customer takes
If the customer is new, starting with the Summer '24 release...
The customer can't access the Agentforce Health managed package. The design and installation path is the core platform, because the package isn't available.
If the customer onboarded before Summer '24...
The customer keeps access to the managed package. The org can keep using package features, but newer features are built on the core platform instead of in the package.
Two customers ask you for a design. Northside Clinic onboarded before Summer '24 and uses the Admin app, which comes from the package. Bay Home Care is signing up for the first time after Summer '24, so the package isn't available to it. Northside Clinic keeps the package and the Admin app, and any newer feature it adopts comes from the core platform. Bay Home Care's design goes on the core platform and can't rely on the Admin app from the package.