Using another break point, check the output of getTask() in TaskServiceImpl.requestReview: without the changes in this PR, the changes in the custom field from the update in the previous point should not be there
The explanation is that this last getTask() is returning cached data from the local SQL session.
By calling the new TaskanaEngine API method implemented in this PR from the SPI ReviewRequiredProvider, the cache is cleared and the last getTask() above returns fresh data from DB.
Release Notes:
### For the submitter:
- [ ] I updated the [documentation](https://taskana.atlassian.net/wiki/spaces/TAS/overview) and will supply links to the specific files
- [x] I did not update the [documentation](https://taskana.atlassian.net/wiki/spaces/TAS/overview)
- [ ] I included a link to the [SonarCloud branch analysis](https://taskana.atlassian.net/wiki/spaces/TAS/pages/1019969636/SonarCloud+Integration)
- [ ] After integration of the PR, I added a description of changes on the [current release notes](https://taskana.atlassian.net/wiki/spaces/TAS/pages/1281392672/Current+Release+Notes+Taskana)
- [x] I did not update the [current release notes](https://taskana.atlassian.net/wiki/spaces/TAS/pages/1281392672/Current+Release+Notes+Taskana)
- [ ] I put the ticket in review
- [ ] After integration of the pull request, I verified our [bluemix test environment](http://taskana.mybluemix.net/taskana) is not broken
### Verified by the reviewer:
- [ ] Commit message format → (Closes) #<Issue Number>: Your commit message.
- [ ] Submitter's update to [documentation](https://taskana.atlassian.net/wiki/spaces/TAS/overview) is sufficient
- [ ] SonarCloud analysis meets our standards
- [ ] Update of the [current release notes](https://taskana.atlassian.net/wiki/spaces/TAS/pages/1281392672/Current+Release+Notes+Taskana) reflects changes
- [ ] PR fulfills the ticket
- [ ] Edge cases and unwanted side effects are tested
- [ ] Readability
Steps to reproduce the problem described in #2634:
The explanation is that this last getTask() is returning cached data from the local SQL session.
By calling the new TaskanaEngine API method implemented in this PR from the SPI ReviewRequiredProvider, the cache is cleared and the last getTask() above returns fresh data from DB.
Release Notes:
### For the submitter: - [ ] I updated the [documentation](https://taskana.atlassian.net/wiki/spaces/TAS/overview) and will supply links to the specific files - [x] I did not update the [documentation](https://taskana.atlassian.net/wiki/spaces/TAS/overview) - [ ] I included a link to the [SonarCloud branch analysis](https://taskana.atlassian.net/wiki/spaces/TAS/pages/1019969636/SonarCloud+Integration) - [ ] After integration of the PR, I added a description of changes on the [current release notes](https://taskana.atlassian.net/wiki/spaces/TAS/pages/1281392672/Current+Release+Notes+Taskana) - [x] I did not update the [current release notes](https://taskana.atlassian.net/wiki/spaces/TAS/pages/1281392672/Current+Release+Notes+Taskana) - [ ] I put the ticket in review - [ ] After integration of the pull request, I verified our [bluemix test environment](http://taskana.mybluemix.net/taskana) is not broken ### Verified by the reviewer: - [ ] Commit message format → (Closes) #<Issue Number>: Your commit message. - [ ] Submitter's update to [documentation](https://taskana.atlassian.net/wiki/spaces/TAS/overview) is sufficient - [ ] SonarCloud analysis meets our standards - [ ] Update of the [current release notes](https://taskana.atlassian.net/wiki/spaces/TAS/pages/1281392672/Current+Release+Notes+Taskana) reflects changes - [ ] PR fulfills the ticket - [ ] Edge cases and unwanted side effects are tested - [ ] Readability