Alfresco Collaboration Connector for Microsoft 365 - End Editing fails

Description

Current behaviour
When using O365 connector, "End editing" action fails, raising an error on the OOI side.
It seems that this issue wasn't there a couple of weeks ago… So, it can be related to some changes from Microsoft ... (APIs, SDK, ?)
Here is a StackOverflow thread referring to the same error that we can see in the logs : https://stackoverflow.com/questions/66075502/graphapi-com-microsoft-graph-core-clientexception-caused-by-java-lang-illegalst
Root cause could be the same : core library implementation needing an upgrade to fit with the newest MS API / SDK.

Expected behavior
When users finish editing with MS 365, initiator of the coauthoring process makes end to the edition through the dedicated ADW Action "End Editing". Then, a new version (minor / major) is created in ACS according to users modifications

Steps to reproduce the issue

  • Edit a Microsoft Office document via the 365 connector and ADW

  • Make some changes within the content of the document

  • Go back to ADW and "End editing" through the related action

  • Error is raised and new version cannot be created + document still locked...

Please see the attachment for more details.

Environment

None

Testcase ID

None

Activity

Show:
Dwayne Ray
March 19, 2021, 5:38 PM

I’ve confirmed that OOI 1.1 resolves the issue, and is going out in an updated ADP (version 6.1.6) today. Thanks again for the quick response and attention on this issue!

Preeti Nirwal
March 19, 2021, 2:52 PM

ADP environment to be upgraded with latest version soon.

Preeti Nirwal
March 19, 2021, 2:51 PM

Thanks for your input!

for now I’ll put this Jira in “Verify” as this should be fixed in the latest version of OOI 1.1. Once ADP is upgraded please verify this bug, once we are good, we can close it. Thanks for bringing it to our attention.

Massis Buyukkalender
March 19, 2021, 2:25 PM

Hi ,

I’m using our internal SE tool named ADP (Alfresco Demo Platform) maintained by . After a quick check on ADP documentation, it seems that the version 1.0 is used on the OOI side.

: up to you now

David Edwards
March 19, 2021, 1:45 PM
Edited

What version of O365 (OOI) are you using?
The issues caused by the referenced stackoverflow site were known in V1.0 and are fixed in v1.1 and the work was done as part of
See

Done

Assignee

Unassigned

Reporter

Massis Buyukkalender

Labels

None

Premier Customer

None

Security Issue

None

Target Platform

None

Code Branch

None

Build Location

None

Regression Since

None

Work Funnel End

None

Patch Attached

None

Dependent Version/s

None

Cloud or Enterprise

None

Prioritization Score

None

Delivery Team

None

Bug Priority

Category 1

Components

Fix versions

Affects versions