Omnistudio Hybrid enables a dual-environment configuration that allows you to access both managed package and Omnistudio standard designers and runtimes within the same org.
By default, Omnistudio Hybrid is enabled for managed package users to provide a reliable path to modern workflows while maintaining metadata consistency.
Omnistudio Hybrid encourages a transition to the standard designer by allowing standard and managed package components to coexist. You can continue managing legacy components in the managed package designer while building new components in the Omnistudio standard designer and runtime to experience a refreshed layout and improved performance.
To maintain stability and reduce migration complexity, the system locks a component to the designer you select when you create it. If you choose to manage a component using the standard designer, you can't open or configure it in the managed package designer. This restriction prevents mixing parent and child components across different designer types so that your implementation remains stable and consistent as you transition individual components to the standard designer.
Key Features
- Object-level governance: Separate logic for standard and custom objects enables a modular digital transformation.
- Runtime locking: After the Managed Package Runtime setting is disabled, the system locks into standard runtime mode to maintain metadata stability.
- Designer flexibility: Switch between managed package and standard designers to resolve cross-dependency components before full deployment.
- Omnistudio Hybrid Compatibility Matrix
Use this matrix to determine the active designer and runtime environment based on your org settings and object type. - Create Components Using Omnistudio Hybrid
Select the Managed Using Standard Designer option when creating Omnistudio components to build new components in the standard designer while you continue managing legacy components in the managed package designer.