Rhythmyx-7.3.2-Patch-20190816

Patch id: 732_20190816

This small patch corrects a defect that prevents some customers for Editing Templates and Slots. 

Download

Downloads are available via the support portal at https://percussionsupport.intsof.com

Previous Patches

Please note that all patches are cumulative.  The links here are to provide reference access to the release notes for everything that is included in this patch.  Prior patches do not need to be installed before installing this patch.

This patch includes the following changes:

Change Description

RHYT-2672 Workbench fails to load certain Templates and Slots with Null Pointer Exception

An issue was reported where certain templates could generate null bindings on save of the Template in the Workbench or through the SOAP API.  This would cause subsequent loads of the Template to fail. This problem has been corrected by this patch. 

Known Issues / Limitations

RHYT-2575 Workflow Notifications: Invalid notification template results in template source code being emailed

It is important to validate that Workflow Notifications have valid Velocity syntax when setting up custom notification templates.  Syntax errors will result in malformed notification messages.  This will be resolved in a future patch. 

RHYT-2574 Workflow Notification Content Item Velocity Bindings are only referenceable via ${fieldname} syntax

The bindings for notification templates currently require that ${fieldname} syntax be used to reference content item fields.  $fieldname $!fieldname or $!{fieldname} syntax does not currently work for these bindings.  This will be addressed in a future patch. 

RHYT-2576 Workflow Notifications - double links are sent if ${wflink} or $!{wflink} used intead of $wflink by template developer

When adding links to custom notification templates, the $wflink variable must be used.  $!wflink, ${wflink} or $!{wflink} will result in a second notification link being appended to the notification message.  This will be addressed in a future patch. 

RHYT-1935 - Folder with old name need to be removed manually after publishing.

Once a folder name is changed and publishing is done, the new folder is published to the publish location, however, the folder with the old name is still present in that location and currently needs to be removed manually.