Workflow With Jumps And Revisions Not Behaving Correctly In 7.5.1
(Doc ID 447017.1)
Last updated on JUNE 12, 2017
Applies to:Oracle Universal Content Management - Version: 7.5.1 to 7.5.1 - Release: Stellent to Stellent
Information in this document applies to any platform.
Product: Content Server
There seem to be issues with how Workflow handles revisions when Jumps are used within the Workflow. The latest revision does not seem to be used when checking out the document from the My Workflow Assignments page.
Step 1: Reviewer "checks out" the document from "My Workflow Assignments" page and then "checks in" the document back.
Step 2: Reviewer tries "checking out" the same document again, from "My Workflow Assignments" page and the system throws the following error:
"Content Server request failed"
Unable to check out "CONTENT_0001". The selected revision is not the most recent revision.
Step 4: Reviewer tries "Checking out" the same document again, this time from "Content Information" page and it gets checked out without any errors.
Customer recently changed the setting on all of the workflows to allow the reviewers to create new revision on contribution. While this works correctly for revision one, this issue is happening for all documents with a revision number greater than 1. This issue is only happening if you have a jump step within your workflow. I created a sample workflow without any jumps and this issue does not occur.
Step 4 just states that we are able to checkout the document from the "Checkout" link from the content information page without any errors.
This error only occurs if the workflow has the following characteristics:
1. a create new revision workflow step
2. the user is not an admin
3. the step contains a wfJump instruction
4. and the revision being checked in was the second or later revision of the document.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document