Is this the expected behavior of WCC workflow?
1. user1 created a doc named doc1, this doc match condition for workflow1, and status is "review"
2. user1 checkout doc1 and checkin(as doc1 is in review status, checkin action should be prohibited)
3. status for doc1 is released
Is this a bug?
"If the step is a reviewer/contributor step, the reviewers can check out the revision, edit it, and check it back in before approving it. For example, editors may need to alter the content of an item in the workflow."
You can deactivate the edition and just let the reviewer approve or reject the document.
I still have a problem with that:
With edition enabled, that's just enable the capability of editing the content, in any case, I believe the author checkin that document again should not bring it to release status when that doc still meet a criteria workflow condition.
I am not a workflow expert but I'll try to help you
I do not really understand your case ...
Here are the steps the document follows :
- Submit the document
- The document enters the workflow
- A reviewer Approve/Reject/Edit the document
- If he edits it, the document is released
Is that correct ?
Instead of being released, you would like the document reentering the workflow ???
Why not do what I needed to do to prevent someone from passing a item through a workflow without checking it? I had a field with a yes/no drop down and set the default to blank, and in the exit script I made it so that if the field is blank send it back to repeat that step (in short if it was never change it will loop indefintly). What you can do is have a field like "ready to release" and when he checks it out and back in he would have to change the field to yes or no. If it's blank (or no) just send it back to his step again, and you can even have it send a different email if you choose (or not email him at all if it was sent back on repeat).
Thanks for reply.
My question is why my workflow is finished in the above case? it is not reasonable for a workflow to be finished just by checking in a new version from author. changing to another words: without approver's action, a item in workflow should not be released in any case.
Sounds like you were expecting the functionality of workflows in UCM to behave in a different manner. The way I understand the check in/out function of the workflow is that you're checking out the file and making edits to it, and when you check it back in you're approving and pushing it to the next step in the workflow (if you have one step/last step in the workflow it would release the item). Because if you were to pass a document to someone in person you wouldn't give it to him unless you were sure it's ready to hand off. It makes no sense to check a item back in unless you were down making edits to it, because the point of UCM is to store the finished content.