Skip to main content

Web2Publish - Patch 4 - Change Log

This patch, released on March 16, 2026, includes bug fixes and usability improvements for Web2Publish.

Build Name on FTP: web2publish_4.7.0.6.zip


Release Notes

Issue keySummaryRelease Notes
ADMIN-3366Duplicate metadata in root levelFixed an issue where metadata at the root publication level was duplicated when using Duplicate by Process. The process now applies only to child folders and documents, excluding the root level.
ADMIN-3365Available steps: support other STEP typeAdded validation logic for additional wizard step types to control step completion:
TABLE: completed when table metadata contains values
FORM: completed when all required fields are filled
ASSIGN_PRODUCTS: completed when at least one planning exists
ADMIN-3326Improve CTA placement for 6 wizard types in W2PImproved UI consistency across six W2P wizard types by separating global actions and step-specific actions into dedicated areas, following the updated design.
Note: This update currently applies only to the FE UI layer. Backend support still needs to be defined and implemented, after which the FE will map and display the corresponding behavior.
Applied to: FORM, PROCESS, TABLE_SELECTION, PLANNING_TREE, CUSTOM_DOCUMENTS, and PRODUCTS_ASSIGNMENT steps.
ADMIN-3279Keep selected value of assign products consistent after renderingImproved the Product Assignment display to keep the selected product values consistent before and after rendering, even when page order changes during rendering. The same filtering logic is now applied across Custom, Planning, and Assign Products steps to ensure consistent results.
See configuration details: Document Filter
ADMIN-3275Update the login URL to support SSO-loginUpdated the login flow to use the SSO login URL instead of the PubServer login_url property, ensuring proper authentication when accessing the application directly via URL.
ADMIN-3184Cannot set empty value for bucket paramFixed an issue where W2P allowed an empty value for the bucket parameter, which is not supported by the core and caused an exception. Validation is now applied to prevent empty bucket values.