[
http://jira.magnolia.info/browse/MGNLDMS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18244#action_18244
]
Sunish Abraham commented on MGNLDMS-137:
----------------------------------------
Hi Jan,
We are using Magnolia Data and DMS modules to feed content to Java/Spring web
application...accessing the content/data in Magnolia using JNDI module.
Here is the scenario...
1) EMEA administrator creates an abstract/ event in Staging Author. The
documents associated are version 1.0
2) Website owners receives an email about the creation
3) The website owners logs on to staging author instance, previews the event/
abstracts. Assume NL website owner previewed the event and finds every thing
okay and approves using medichannel event/ abstract paragraph. This will
trigger the workflow. This workflow will publish the content node to all
subscribers (staging public) without using INBOX.
4) So after the above step, the meta-data of the event/ abstracts gets uploaded
into NL specific folder under staging public, and the document is also
published to staging public to a shared magnolia folder.
5) But another website (FR) owner rejects the event for what ever reasons
6) EMEA admin modifies the same event and uploads a newer version of the same
document. This will trigger emails to all website owners.
7) After receiving the email the FR admin, logos on to staging author, previews
event/ abstracts and he approves it. This should activate version 1.1 of the
document to public instance.
8) The web application which is configured to use magnolia-jndi will pick up
respective versions of the document based on the value in site-key. If the
JC2.0 medichannel site is NL then version 1.0 will be available for download if
the JC2.0 medichannel site is FR then version 1.1 will be available for
download.
Sunish
> 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/
----------------------------------------------------------------
