Acquia DAM - April, 2023

This month, Widen unveiled its new name, new look, and redesigned community site. 

Widen brand merge with Acquia

Widen Collective has been rebranded as Acquia DAM (Widen). In the coming months, you will see new branding on our websites, emails, apps, and other channels. URLs containing “Widen” or “Collective” will stay the same and continue to work as they do now. This brand update will not affect you or your users’ access to DAM, Portals, embed codes, SSO, API, integrations, or any other functionality.

Redesigned DAM community 

As part of our rebrand, Widen Connect is now the Acquia DAM Community. You’ll notice a new logo and main menu, which was designed based on your feedback. Although the community looks different, what you can do there hasn’t changed. Search the support article library or log in to access DAM Customer Support, user groups, and the discussion forum. 

 

Additional option for Workflow app deliverables

If a deliverable is approved with edits in the final stage of review, you now have the option to Reopen with new version. This means that if you make the edits and want another review stage, you no longer have to upload a final version before starting that process. This change will be live for all customers on May 2.

 

Improved Channels page

On the Channels page in the Entries app, you can now see the date updated, channel creator, and status at a glance.

Bug fixes

• The video clipping feature has been fixed and is now working.
• Videos with small iframes in embedded Portals are no longer being cut off.
• An issue where downloaded files in portals didn’t reflect the most recent filename updated via API has been resolved.
• We fixed an issue in the Workflow app. When a user advances a workflow to the next stage and both stages have today as the due date, the due dates will longer be pushed back by a day.
• An issue with certain conversions failing for some Camera Raw (.cr3) files was resolved.
• A bug with viewing a portal using an access code has been fixed.
• There was a bug where the same user was made a commenter and approver of Workflow deliverable stage, and it caused an error. We added a message telling you to remove the user from one of those roles, so the error doesn’t happen.