Legacy Knowledge Base
Published Jul. 2, 2025

Workflow review comments are not visible under Activities Tab

Written By

Pooja Bhambani

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

  • The approve and reject comments are not visible under activities Tab in Liferay DXP 7.3, whereas, it is visible on Liferay DXP 7.2

Environment

  • Liferay DXP 7.3 

Resolution

  • The observed behavior is an intended behavior of Liferay DXP 7.3
  • The technical reason why it is not visible in newest task is that the previous comments are filtered by 'kaleoTaskInstanceTokenId', whereas, the previous messages, including the rejection message, have a different 'kaleoTaskInstanceTokenId'.

Additional Information

  • Workaround to achieve this functionality

          The notification template for a process task has to be changed by using available services and                       variable to include all task comments
          To, use this service

public List<WorkflowLog> getWorkflowLogsByWorkflowInstance(long companyId,
long workflowInstanceId, List<Integer> logTypes,
int start, int end,OrderByComparator<WorkflowLog> orderByComparator)
throws WorkflowException;

          Also, please refer to this example of its usage.

Did this article resolve your issue ?

Legacy Knowledge Base