Documents with expired lock still show as locked in ADW and user cannot cancel editing

[katielipovetsky]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/Alfresco/alfresco-content-app/blob/master/CONTRIBUTING.md#question

Current behavior

When locking a document and setting an expiry time, the document still shows as locked in ADW after the lock expires and you get an error trying to Cancel Editing (error is node cannot be unlocked because it isn't locked)

Expected behavior

When a lock expires on a document it should no longer be shown as locked in ADW. Possible solution is to check the expiryDate property or add isLocked to the include parameter in requests to get children when navigating through the repository

Minimal reproduction of the problem with instructions

Steps to Reproduce

1. Lock a document and include timeToExpire in the payload
   curl -X POST "http://localhost:8080/alfresco/api/-default-/public/alfresco/versions/1/nodes/{nodeId}/lock" -H "accept: application/json" -H "Content-Type: application/json" -d "{ "timeToExpire": 120, "type": "ALLOW_OWNER_CHANGES", "lifetime": "PERSISTENT"}"

2. Wait for the lock to expire and navigate to the file in ADW

3. Try to Cancel Editing on the document

What is the motivation / use case for changing the behavior?

Environment

ACA version: 2.10.0


Browser:
- [x] Chrome version XX
- [x] Firefox version XX
- [ ] Safari version XX
- [x] Edge version XX
- [ ] IE11
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others: