REST api does not update the primary path on new version upload

Description

[Description]

Uploading a new version via REST api does not update the primary path of the document.

[Steps to reproduce]

  • Install alfresco 6.2.2 using the installer

  • Start alfresco

  • Login as the admin user to share

  • Create a site

  • Create/upload a text document

  • Take note of the node reference

  • In the node browser check the node's primary path

  • Execute the curl command below to update the text file, note the name change

    [Expected Behaviour]

New version of the document is created and the primary path is updated to the new name of the document

[Observed Behaviour]

New version of the document is created, the primary path of the document remains the same as the original document

[Analysis to date]

Using share's "upload new version" action it updates the document and its primary path. This is the same issue as MNT-22015 but the customer would like that fix in 6.2 as well since they are getting ready to do the upgrade to 6.2.

Environment

aws/tomcat/postgres

Testcase ID

None

Activity

Show:
Tiago Salvado
November 19, 2020, 5:52 PM

PR:

  • alfresco-community-repo

  • alfresco-enterprise-repo

The HF will be 6.2.2.8.

Once the builds finish, the release will be created.

Fixed

Assignee

Tiago Salvado

Reporter

Jose Portillo

Labels

None

Security Issue

None

Escalated By

None

Hot Fix Version

ACT Numbers

01017886

Build Location

None

Regression Since

None

Premier Customer

Yes

Work Funnel End

None

Patch Attached

None

Dependent Version/s

None

Prioritization Score

None

Delivery Team

Customer Excellence

Bug Priority

Category 2

Components

Fix versions

Affects versions