Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
2.9.0, 2.7.8, 2.8.4
-
None
-
None
Description
Current Situation
Currently if an already released item is moved to a different folder via the Cut & Paste operations the released state of the object does not change. The path and folder values in the inventory table are adjusted, but the path and folder entries in the released table are not considered.
If a user now tries to export the already released and moved objects, two things can happen.
- Setting Individual Objects
- DBInvalidDataException: No result found for query [from DBItemInventoryReleasedConfiguration where path = :path and type = :type]
- Setting Folder
- the released items from the folder are missing without an error
- the export api reads all objects from the target folder and if the objects are marked as released, tries to read from the release table
Desired Behavior
The rename api should adjust the path and folder entries in the release table, too. Subsequently other API calls, that rely on the path/folder information e.g. like the export api, will then have no problem to find the desired configuration in the release table.
Workaround
Releasing the objects again will overwrite the not-adjusted path and folder information in the release table with the correct values of the current path.