Default document permissions

[ivan.todorovic]

Hi, I have one more question. After scanning or uploading in the certain folder document gets the same permissions that folder has. I am using workflow which automatically starts after upload or scan . In that workflow I am revoking permissions to every user except the user who did that upload. This might be a problem if user refreshes page after upload (when run_config starts), because workflow will not be executed and document will remain visible for other users. Is there a way to change this, so document can be seen only by the user who did the upload without running the workflow?

[jllort]

You should capture user from session and take it in consideration in your logic.

Code: Select all

Authentication auth = PrincipalUtils.getAuthentication();
auth.getName()

[ivan.todorovic]

Ok, but how can I get to that if user refreshes page after upload before workflow wizard starts (before user enters data on run_config and clicks accept)?

[jllort]

You should take control it, not in worflow, you should control if document creation -> at post ( after creation ) with scripting, have a look http://wiki.openkm.com/index.php/Automation and http://wiki.openkm.com/index.php/Scripting_-_OpenKM_6.2

The idea is take control of security during document creation ( post creation ) and not into workflow logic.

[ivan.todorovic]

OK, but what if user needs to enter some paramethers which are important (and mandatory) for that document, right after upload?
For example document type or assigned user. I know that user can insert it after whole upload is done, by changing related metadata or permissions, but how to make sure he really does that?

As much as I remember workflow can not be run if there is even automation definition. Is there an easy way to change this?

[ivan.todorovic]

I have another idea. Can you tell me the class in the source code where permissions are granted after upload?

[jllort]

Should take a look at DBDocumentModule.java but I think is not good idea change internal implementation. I continue thinking that Automation is right way to do it. And about automation and workflow, there's no limitation on start a workflow together.

[ivan.todorovic]

I found it here:

http://forum.openkm.com/viewtopic.php?f ... 3&start=15



Postby jllort » Sat Mar 16, 2013 8:58 am
"2- When you enable automation wizards are disabled. Actually from comunity version should be made some modification to set the wizards flags from automation."

Postby dip » Sun Mar 24, 2013 11:10 am
"And second, how can I disable automation to be able to test the wizard? At the moment the wizard does not show up since I previously enabled automation."

Postby jllort » Sun Mar 24, 2013 5:11 pm
"Is not possible to disable, you should delete all automation entries to disable. I think logic to switch profile wizard is based on looking for if it's present some automation definition, not any automation defitinion ( you can try disable all automation entries, but I'm not sure it going right )."

Are there any changes about this?

[ivan.todorovic]

I solved it using DBDocumentModule (or to be more precise using BaseDocumentModule). It would be good if I could do it with automation, but anyway tnx a lot!

[jllort]

Next release will come with extended extension support.