[
http://jira.magnolia.info/browse/MGNLDMS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18317#action_18317
]
Sunish Abraham commented on MGNLDMS-137:
----------------------------------------
Hi Jan,
Yes I understand your previous statements on the current functionality (by
design) of saving current version during activation of a DMS document. We need
the functionality to be extended to save the version information of the
document being activated and save new version not replace existing document.
Yes we have found the class which is handling the saving during
activation...does the class which is doing the activation send full information
about the document (that is version information) so that the ReceiveFilter can
process it?
> Magnolia public instance does not contain versioned documents
> -------------------------------------------------------------
>
> Key: MGNLDMS-137
> URL: http://jira.magnolia.info/browse/MGNLDMS-137
> Project: Magnolia DMS Module
> Issue Type: Improvement
> Reporter: Sunish Abraham
> Assignee: Philipp Bracher
> Priority: Critical
>
> versions documents in source DMS activated does not carry the versioned
> information to the destination instance ; we have functionality in the Author
> environment of the destintation instance which requires the documents to be
> versioned
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
