Hi,
I'm trying to build a workflow with published and unpublished documents. And I need that regular people sees published version of the doc while writer can have acces to the beta one. Is there any way to do that in seeddms ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is currently no distinction between pulished and unpublished, but you may use one of the states 'review' and 'approval' for it. That still won't hide the documents from other users than the owner of the document, but the owner of the document could take away read access during editing the document and grant read access once it is finished. You may even implement a hook which adds read access once the document is released.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for the reply.
That's what I did, but if I remove read acces then people, will not be able to find currently approved version of the document.
Last edit: Mgth 2016-11-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Once it is approved you have to grant read access again. That's why I have to suggested to implement a hook which is being called when the doc is approved and sets read access for everybody.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm trying to build a workflow with published and unpublished documents. And I need that regular people sees published version of the doc while writer can have acces to the beta one. Is there any way to do that in seeddms ?
There is currently no distinction between pulished and unpublished, but you may use one of the states 'review' and 'approval' for it. That still won't hide the documents from other users than the owner of the document, but the owner of the document could take away read access during editing the document and grant read access once it is finished. You may even implement a hook which adds read access once the document is released.
Thank you for the reply.
That's what I did, but if I remove read acces then people, will not be able to find currently approved version of the document.
Last edit: Mgth 2016-11-30
Once it is approved you have to grant read access again. That's why I have to suggested to implement a hook which is being called when the doc is approved and sets read access for everybody.