-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Affects Version/s: Alfresco One 5.0
-
Fix Version/s: Community 6.0.4
-
Component/s: Repository
-
Labels:None
-
Environment:All
-
ACT Numbers:
Community
-
Work Funnel:Maintenance
-
Sprint:Repo 6.0 Readiness Sprint 26
-
Story Points:8
-
Work Funnel End:2018-03
-
Template:customfield_14629 168969
-
Bug Priority:
ALF-21543: cm:autoVersionOnUpdateProps is being ignored on inline edit if cm:content have no value
Use Cases:
- Required aspects and property changes
- A document has the cm:versionable aspect
- The document has cm:autoVersionOnUpdateProps ==true
- The document cm:title is modified
- Content
- The document has no content
- The document has zero byte content
- The document has some content
Acceptance Criteria:
- Platform
- Platform tests exist to cover the use cases
- cm:autoVersionOnUpdateProps is respected regardless of the state of the content i.e. property changes must version the node
- Internal Platform tests
- V1 API tests
- Share
- Share is checked as far as ScriptNode or any Platform-specific changes are required
- Resolution
- Issue is resolved for V1 API tests and internal platform tests
- ScriptNode issues raised separately or addressed after discussion
Out of Scope:
- Fixing if the issue is in the V0 APIs or above
- relates to
-
MNT-12226 Alfresco fails to version metadata after uploading new content version even when autoVersionOnUpdateProps=true
- Closed
-
ALF-2685 For Share - provide option to enable auto-versioning for metadata-only updates (can be disabled via content model)
-
- Closed
-
- shadow of
-
ALF-21543 cm:autoVersionOnUpdateProps is being ignored on inline edit if cm:content have no value
-
- Resolved
-