I am trying to understand whether the following behavior is expected design or a bug related to Direct Approval actions.

Scenario

We have an approval step in a Forms business process. Users can approve tasks in two different ways:

1. Opening the task form (typically from the email link) and approving within the form UI.

2. Using Direct Approval from an email (without opening the form itself).

Observed Behavior

• When a user opens the form and approves normally:

  • The Action History later shows the task.

  • Selecting the completed task displays the form with all submitted field values populated.

• When a user approves using Direct Approval:

  • The task shows as completed in Action History.

  • However, when viewing that approved task, the form data is not displayed.

  • The interface gives no indication that the approval was performed via Direct Approval.

Problem

This creates a troubleshooting and auditing challenge because:

• There is no visible indicator in Monitor or Action History showing the approval method.

• Administrators and users assume data is missing or failed to save.

• The difference in behavior is not obvious unless you already know how the approval was performed.

Questions

1. Is this the expected behavior when a task is approved via Direct Approval in LF Cloud?

2. If expected:

   • Is there any configuration or UI indicator that can show the approval method?

   • Is there a recommended best practice to avoid confusion during audits or support investigations?

3. If not expected:

   • Is this a known issue?

   • Are there any fixes or workarounds currently available?

Goal

Ideally, either:

• The form data would still be viewable from Action History regardless of approval method, or

• The system would clearly indicate that the task was completed via Direct Approval so administrators understand why form data is not shown.

Any clarification on intended behavior or recommended handling would be greatly appreciated.