Two versions of asset and merging
One of our user faced a strange issue on asset versions and merging of assets. When we tested even we found that it is a kind of bug. Following are the details and use-case :
1) User submits an asset abc with v1.0. 2) User moved the Draft state asset abc into As-is. 3) User modified the abc asset, change its version to 1.1 and resubmitted (asset will remain Draft). 4) Its worked as designed and RAM created 2 versions of the same asset abc with one version in As-Is state and other version in Draft state. Please note that the As-is state version is 1.0 and Draft is 1.1. 5) As designed, there were no actions (modify, delete, etc.) available for As-is state asset. 6) When user changed the state of Draft asset into As-Is, it didn't merged with its As-Is state asset and As-Is state asset got stuck in its no-actions available mode. Please comment on the above use-case and let us know how we can delete that stuck As-is state asset. |
12 answers
|
Also let us know if this is working as designed or it is a defect?
Thanks..Payal. |
Step (3) above, ... user modify a version:
Did you create a new asset using the new version (action) or did you modify the asset's version field and "replaced the current asset" (in contrast to create new asset) when you pressed the update button. If you create a new asset ... it is a NEW, Different asset. If you replace the existing asset with that version ... both the 1.0, and 1.1 URL references will resolve to the 1.1. |
6) When user changed the state of Draft asset into As-Is, it didn't merged with its As-Is state asset and As-Is state asset got stuck in its no-actions available mode.
What was the actual process to do step 6? After step 6 were there now two assets? Or did the Draft asset and its contents just disappear with no changes on the As-Is asset at all? |
|
The draft state asset is changed to As-is using Actions drop-down.
Now there are 2 assets - both with same guid. But one asset is not having any actions available to it. |
|
As usual, what is the exact version of RAM? The About-> listing, including testfix if any.
|
|
|
|
Is this an internal IBM RAM that you can send a link directly to me that I can access to see what you mean?
Don't append the link here. You would need to temporarily make me a commun admin of that community to look at it. Thanks. |
|
We sent the link to you via email. Also made you the community admin.
Thanks..Payal. |
|
I don't understand. Everything looks like it should be:
a) 1.1 is in Draft - but is based upon the 1.0 as an eventual replacement for 1.0 - there is an AS-IS action available on it. b) 1.0 is in As-Is and is properly locked as it should be since the Draft asset was started to eventually replace it. When you do the As-Is on the Draft asset (and this approved by the admin if needed) then the 1.0 As-Is will be replaced by the 1.1 version. |
|
BTW: I just checked. Community Admin approval is required before it moves from Draft to As-Is once you do the As-Is action. It won't move to As-Is until the Admin approves it.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.