Glad to hear that it' working. It's concerning that you are using the Review instead of the Approval process though.
A few inconvenient facts:
- The Approval process doesn't promote anything until it is duly approved. Most every business needs to run with this control function
- The Review process is a lot more like "I'm setting this to Released and I'm just letting you know." Any business that runs this way has no control function and chaos will of quickly result. The Review process makes perfect sense for some things that don't require strict control but not product data in general.
So, it's likely that no real business can use Promotion as supplied (with both the Approve and Review workflows mapped in the preference) where the user creating the Promotion Request selects from requiring approval or not. It's a lot like "I'm giving myself a raise and I'm just letting you know in case you'd like to comment. Note that in the workflow as supplied, the Promotion Request is approved and an email is sent to that effect prior to anyone getting a chance to review it. It's really lousy that this fact is not brought out clearly by PTC in 64 font bold red letters.
Hi Mike....this just shows how unfamiliar I am with this process.
Someone had "tweaked" the OOTB workflows that our promotion process uses. In our "Promotion Request Approval Process" workflow, the "Review Promotion Request" activity seems to have been moved so that it comes after the "Set State Approved" robot instead of the "Set State Under Review" robot.
We are using the Approval process as you describe it. The review task in that process is what we wanted to remove when an object is promoted to the obsolescence state. Copying the approval workflow and removing this activity worked, as long as you set up the promotion preferences as you originally pointed out. So now any object getting promoted to Obsolescence will be using a different Approval workflow.
Regardless of which process we use....I will still try to give myself the raise!! J