Workflow assets cannot be fully approved with single approver after upgrade to 7.0

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.1 CE GA2
• Fix Version/s: 7.0.1 CE GA2
• Component/s: Workflow, Workflow > Upgrade
• Labels:
  • KNOWNISSUES_DE70
  • LR7UPGRADE
  • QA-AUTOMATION
  • bp-upgrades
  • fw_test_poshi
• Fix Priority: 4
• Sprint: Sprint 16: May, 02 - May, 13
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/39370

Reproduced on:
MySQL 5.7
ee-6.2.10.15 > ee-7.0.x GIT ID: b9ce80a0b1579f9538e02390a7339ac1c97dd32c.

Steps to Reproduce:

1. Import attached sql dump into MySQL 5.7
2. Add attached data folder to ee-7.0.x bundle
3. Upgrade database to 7.0 using the upgrade-tool
4. Start upgraded 7.0 portal
5. Go to Test Test > My Workflow Tasks
6. Approve Web Content Article
7. Go to Content > Web Content
8. View Article

Expected Result:
Article is fully approved.

Actual Result:
Article is shown as "Pending (Approved)" in the Web Content admin portlet. Asset is treating as pending in this portlet.

This also occurs to any new assets added under "Single Approver" after the upgrade.

Note: This only occurs with the default "Single Approver" definition. A custom uploaded definition was able to set the asset to approve correctly (even if the definition was added pre-upgrade). Comparing the single approver definition between upgraded ee-7.0.x and non-upgraded master KaleoDefinition table shows that the definitions are identical