-
Type: Improvement
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: 6.0-HF30, 7.10-HF09, 8.2
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Core
When you update the blob of a Document using Drive or the platform, a new version is automatically created. But also, the lifecycle changes if it's in the state 'approved' or 'obsolete' and it follows the transition 'backToProject'. It's hardcoded in the StandardVersioningService and should be made easily configurable.
- is related to
-
NXP-23284 Remove assumptions on lifecycle transitions when automatically versioning a document
- Resolved