There is an unacceptable decrease in performance observed within large Publications. With publications housing a large number of individual changes, the current system struggles to maintain acceptable performance levels, especially during conflict checking and publishing publications. These two phases leverage handwritten SQL queries to perform those tasks that allow Publications a shortcut through our persistence layer to maximize performance in small publications. In large publications though, further considerations must be taken to ensure consistent performance.
Release Notes
Allow users to map Repeatable fields of a Web Content Structure already defined in Fragments and Collection Displays.
The /search and /suggestions APIs comes with the following enhancements:
New, optional
scopeparameter supporting Site (Group) IDs and External Reference Codes (ERCs) in /search. The scope parameter of /suggestions has also been updated to have the same semantics./searchnow is in RELEASE status.The APIs now are available under the
/o/search/v1.0/endpoint with backward compatibility for current/o/portal-search-rest/v1.0calls through server-side forward.
Refer to the documentation for more details.
Clause Contributors configuration is now stored within the blueprint’s JSON with a smaller footprint, reducing the size of a blueprint by more than 90% when using the default setting (all contributors enabled → Enable All) or the new Disable All option.
The behavior of the different options is as follows:
with Enable All, all current and future query clause contributors introduced to the platform will be enabled automatically. Disable All behaves the opposite way,
with Customize, the configuration is locked to the specified contributor list.