This release introduces a new configuration that allows the owner of an Object Definition to decide whether it can be used inside Form Containers in Page Builder. While objects could already be mapped to forms before, administrators now have explicit control over which objects are exposed for page-level form experiences.
This provides a governance layer that helps avoid accidental exposure of internal, sensitive, or system-bound data structures, while still allowing selected objects to participate in dynamic form experiences when desired.
Key Benefits:
- This configuration gives object definition owners full control over whether their data can be used in Page Builder forms, improving security, reducing clutter in the selector, and preventing misuse of objects that were never intended for page-level experiences. Teams can now allow only the right objects to power form-based experiences, while keeping internal or backend-only objects protected.