Since Publications provides a final end point for users to review changes, it would benefit content editors tremendously if they could also review their workflow changes.

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.

Some upgrade processes may not consider the ctColectionId column which may generate inconsistencies for customers using Publications, especially for older versions.

Add changeTrackingEnabled to the standard rest-config.yaml so that services must specify Publications support. This will simplify the process of enabling change tracking for future Headless APIs.