For clients that plan on using the Sharepoint protocol, WebDAV, or Share to touch objects that are created in OpenContent, there appears to be a line in our code that we are explicitly telling Alfresco that we do not want a new version when content is updated:
This is causing issues with the expected behaviour of Share/Sharepoint protocol saves since it forces everything to be checked in as the same version.
What are the places in code that are impacted if we flip this to 'true'?
@parzgnat and @gsteimer identified that "checkin as same version" may not work.
@parzgnat also identified that appending the wizard signature page may be impacted
If we make this update, the above two scenarios need to be tested to see if they work and/or produce odd side effects.
If setting to true works, we need to verify:
[ ] if documents updated through Share/Sharepoint protocol properly minor version on every save
[ ] every time the document is saved, a new PDF rendition autorendered and viewable from HPI for every minor version
[ ] Wizard signature pages work for native word documents as well as a native PDF routed for approval
[ ] Checking in as same version... can we do that anymore?
For clients that plan on using the Sharepoint protocol, WebDAV, or Share to touch objects that are created in OpenContent, there appears to be a line in our code that we are explicitly telling Alfresco that we do not want a new version when content is updated:
AlfrescoEmbContentImpl#enhancedCreateObject:
This is causing issues with the expected behaviour of Share/Sharepoint protocol saves since it forces everything to be checked in as the same version.
If we make this update, the above two scenarios need to be tested to see if they work and/or produce odd side effects.
If setting to true works, we need to verify: