Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Single Approver Workflow Recipient Type Changes Don't Save

Written By

Kenny Back

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • We are currently running Liferay 7.4 U70 and discovered that when we make a copy of the Single Approver Workflow and try to update the "Review" node so that one of the notifications has a different Recipient Type it reverts back to Asset Creator. This was not an issue in our previous environment of Liferay 7.4 U33. Here we saw that the review notifications had two different recipient types (Asset Creator and Task Assignee). Is there a known issue with respect to this? 

 
Here are the Specific Steps:

1) Startup a vanilla bundle of 7.4 U70

2) Go to the app menu > workflow > process builder

3) Click the 3 dot menu next to the default single approver workflow and choose duplicate

4) Open the new workflow copy, click the review node, and go to notifications

5) Under the 'Review Notification' settings change the recipient from the default asset creator to site role - site content reviewer 

6) Press update

7) Observe the changes are not saved successfully

Environment

  • DXP 7.4

Resolution

  • This behavior was the result of a regression and has been resolved in Liferay 7.4 U92
  • As such, please update to Liferay 7.4 U92+ and the changes will be saved as they were in U33 

 

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?