-
Type:
Bug
-
Status: Closed
-
Resolution: No Longer Reproducible
-
Affects Version/s: Master
-
Fix Version/s: None
-
Component/s: Workflow
-
Labels:None
-
Fix Priority:4
Current issue: IndexNotFoundException can be seen when the portal is initiated with a database populated with data from a previous hash
Steps to reproduce:
- Checkout liferay-portal repo to 9091b47b798c8c08603abbddeb3949602fcb0784
- Build portal (ant all)
- Start the portal with a brand new MySQL database (lportal)
- Associate Single Approver with blogs entry
- Create few entries and approve some of them and go to Metrics to be sure the data is there
- Go to CP > Search > Field Mappings and observe that workflow metrics indexes are not following the pattern: [<prefix>]workflow-metrics-instances<companyId> (
LPS-108828) - Stop the portal
- Rebase liferay-portal with latest master hash
- Build portal (ant all)
- Start the portal with the same database used on step 3
- Go to CP > Metrics
- Go to CP > Search Field Mappings
Actual result: IndexNotFoundException can be seen. Workflow metrics indexes persist without the correct pattern
Expected result: No exception should be seen and workflow metrics indexes should be displayed with the pattern described on LPS-108828
Environment:
master DXP old hash: 9091b47b798c8c08603abbddeb3949602fcb0784
master DXP new hash: 43f034138129c4601c1dd0cdf076d8cfc4e99c01
- Discovered while testing
-
LPS-108828 As a Portal Admin, I want Workflow Metrics to create an index per company
-
- Closed
-