Version 6.5.9
Adobe Experience Manager has been updated from v6.5.8 to v6.5.9. This update includes new features, key customer-requested enhancements, bug fixes, and performance, stability, and security improvements.
Highlights
- Ability to restore deleted pages and tree on an Experience Manager Sites page.
- Accessibility enhancements in Experience Manager Assets and Dynamic Media.
- Ability to send a notification email to a group using Assign Task workflow step.
- Set custom domain name for loading, rendering, and validating the reCAPTCHA service in Experience Manager Forms.
- When you select a form data model and a service in Invoke Form Data Model Service workflow step, you specify service arguments for input data.
- If you select Relative to Payload option to attach a file as a service argument, you can now specify the folder path that contains the file instead of the actual file name. Defining the folder name, instead of the file attachment name, enables you to reuse workflow models. You do not limit the workflow model to a single file attachment name.
- Ability to use multiple master pages in a Document of Record template in Experience Manager Forms.
- Support page breaks in Document of Record in Experience Manager Forms.
Bug Fixes
- When creating a hyperlink, the option to search a link does not work in the text component.
- Nested layout container inside another resized layout container shows an incorrect number of columns for its child components, resulting in these components not being aligned to the grid.
- onTime/offTime items do not activate/deactivate on the expected onTime/offTime.
- When a user types in improvised text for tag (tag that does not exist on the system) and presses Enter, the tag appears under the field but when the Content Fragment is saved and reopened, the improvised tag disappears.
- Inbox does not have option display the status of Asynchronous Operations.
- A duplicate component is created after restoring inheritance.
- When trying to resize a component within a container, resizing back to the original size is not possible. When the component container size is reduced, it is not possible to set the size back to the original.
- When multiple assets are selected to update the properties, sometimes either an error occurs, or properties of a deselected asset get updated.