How: Approved asset stay approve after update?
3 answers
What version of RAM are you using? There is not a version 7.2.1.
In lifecycles, the asset will remain in the approved state when it's updated. If there's a transition from the approved state, it will only take the transition if the asset meets the criteria. I'm thinking you may still be using a legacy review process. If you're on a newer version of RAM, using a lifecycle instead of a legacy review would probably solve your issue.
In lifecycles, the asset will remain in the approved state when it's updated. If there's a transition from the approved state, it will only take the transition if the asset meets the criteria. I'm thinking you may still be using a legacy review process. If you're on a newer version of RAM, using a lifecycle instead of a legacy review would probably solve your issue.
It is v 7.2.0.1
We have 2 scenarios here :
1) We created a new asset type using a RAM built-in lifecyle. After we have approved the asset (the asset is in approve state), we modified the approved asset but the asset didn't remain as approved as you stated it should be. Any idea Why? Is there other configuration that need to be done so that approved asset stay as approved after update?
2) Assets migration from v7.1.1.1 using CQ to v7.2.0.1. After migration, we deleted the legacy review process and replace it by a RAM built-in lifecyle; then we did an update on a migrated approved asset, but this migrated approved asset didn't stay as approved but started it own lifecyle or transition (its state set at first state in the lifecycle). Is this normal or expecteed behavior?
We have 2 scenarios here :
1) We created a new asset type using a RAM built-in lifecyle. After we have approved the asset (the asset is in approve state), we modified the approved asset but the asset didn't remain as approved as you stated it should be. Any idea Why? Is there other configuration that need to be done so that approved asset stay as approved after update?
2) Assets migration from v7.1.1.1 using CQ to v7.2.0.1. After migration, we deleted the legacy review process and replace it by a RAM built-in lifecyle; then we did an update on a migrated approved asset, but this migrated approved asset didn't stay as approved but started it own lifecyle or transition (its state set at first state in the lifecycle). Is this normal or expecteed behavior?
Hi,
I don't know about (1), but about (2), that is correct in the way it works.
States are associated directly with the review or lifecycle. If you change lifecycle or reviews there is whole new state of states. Approved for legacy is a completely different state than Approved in Simple lifecycle. In fact depending on the lifecycle there may not even be an Approved state. So whenever an asset switches legacy review or lifecycle that asset will start at the beginning of that new review or lifecycle.
Rich
I don't know about (1), but about (2), that is correct in the way it works.
2) Assets migration from v7.1.1.1 using CQ to v7.2.0.1. After migration, we deleted the legacy review process and replace it by a RAM built-in lifecyle; then we did an update on a migrated approved asset, but this migrated approved asset didn't stay as approved but started it own lifecyle or transition (its state set at first state in the lifecycle). Is this normal or expecteed behavior?
States are associated directly with the review or lifecycle. If you change lifecycle or reviews there is whole new state of states. Approved for legacy is a completely different state than Approved in Simple lifecycle. In fact depending on the lifecycle there may not even be an Approved state. So whenever an asset switches legacy review or lifecycle that asset will start at the beginning of that new review or lifecycle.
Rich