Not allowing the author to edit the file after submitting to workflow

Suppose an author submits a file to workflow. If the file is in any task in the workflow, and the author goes to the contents tab, he is able to edit the same file, and the changes in the file gets reflected in the later tasks.
How can we stop an author from editing a file after it is being submitted to workflow.

Find more posts tagged with

Comments

Mr_Cruise

A simple solution would be to set the attribute ‘readonly’ to true on every task. However, this would mean that a user could not add, remove, or modify files in the tasks. The final solution depends on you workflow as it may require extra changes to meet your business requirements.

ISCBorisB

Suppose an author submits a file to workflow. If the file is in any task in the workflow, and the author goes to the contents tab, he is able to edit the same file, and the changes in the file gets reflected in the later tasks.
How can we stop an author from editing a file after it is being submitted to workflow.

You can lock WF Files using locktask in the *desired* place of the Flow. If you do, make sure that you transition properly on both locking Success and Failure

chiragjain

Making the attribute readonly to true, disables the edit option. But still the author can edit the file in two ways
1. Goto cpro and edit the file
2. In the task details screen, click on preview, Here the edit button is not disabled.

Please tell me how to disable the author from editing through all these ways.
Thanks

ISCBorisB

Making the attribute readonly to true, disables the edit option. But still the author can edit the file in two ways
1. Goto cpro and edit the file
2. In the task details screen, click on preview, Here the edit button is not disabled.

Please tell me how to disable the author from editing through all these ways.
Thanks

Users with proper access credentials can also edit WF File through Samba, mapped/mounted Drive, CC URL Edit command and so on.

In TS the fact that you've attached some File to the Workflow simply means that corresponding WF Objects have a reference to that File Path,
nothing more. You'd have to lock File(s) if you want to constraint Editing. As I mentioned before, use dedicated <locktask> and try to avoid
using "lock" attributes of other tasks

chiragjain

Thanks
I am using a dedicated lockTask to lock the file(s). But since the file is being lock under the author itself, hence it is able to still edit the file, even if the file is in any stage of workflow.

Do you mean to say that I should lock the file with some Admin so that the author can also not edit the file. Kindly clarify
Thanks

ISCBorisB

Thanks
I am using a dedicated lockTask to lock the file(s). But since the file is being lock under the author itself, hence it is able to still edit the file, even if the file is in any stage of workflow.

Do you mean to say that I should lock the file with some Admin so that the author can also not edit the file. Kindly clarify
Thanks

You can certainly (re)lock Files as some other Editor/Admin user. Note though that to do so may require unlocking first.

That said, your use case is somewhat obscure. Why would your Authors modify something, submit it and go right back
to modifying it again before WF ends? What is the problem you are trying to solve?

moonkhanna

Thanks
I am using a dedicated lockTask to lock the file(s). But since the file is being lock under the author itself, hence it is able to still edit the file, even if the file is in any stage of workflow.

Do you mean to say that I should lock the file with some Admin so that the author can also not edit the file. Kindly clarify
Thanks

set the lock and transferOnly attributes of the corresponding tasks to be true which way the locks will be transferred to the user who owns the next task.. and the author will not be able to edit the files through CCPro then..

Also, as Bo stated, this is User Training issue..You need to make sure that your users understand the process..