Way to pick up new lifecycle?
One of our user created a lifecycle for his community.
The issues he is having is that there are assets that were approved prior to having this lifecycle implemented and he is not even able to go and reject them. The only options available to the community administrator, is to RETIRE the asset.
Community admin would like these old assets to go through the new process and pick up the new lifecycle.
Please let us know the way to achieve this.
The issues he is having is that there are assets that were approved prior to having this lifecycle implemented and he is not even able to go and reject them. The only options available to the community administrator, is to RETIRE the asset.
Community admin would like these old assets to go through the new process and pick up the new lifecycle.
Please let us know the way to achieve this.
3 answers
1. Navigate to the lifecycle tab on the community administration page.
2. Ensure your new lifecycle is at the top of the list and that the conditions for the lifecycle match the assets you want to enter the lifecycle.
3. Modify each asset that you want to enter the new lifecycle. When the asset is modified, it will fall into the best match lifecycle for your community.
2. Ensure your new lifecycle is at the top of the list and that the conditions for the lifecycle match the assets you want to enter the lifecycle.
3. Modify each asset that you want to enter the new lifecycle. When the asset is modified, it will fall into the best match lifecycle for your community.
2. Ensure your new lifecycle is at the top of the list and that the
conditions for the lifecycle match the assets you want to enter the
lifecycle.
Be careful that (2) is what you want. There is an ordering process on
selecting lifecycles for best match. Only move it to the top if you want
it to be chosen instead of some other. BUT also remember that by doing
this you can accidentally forever hide a lifecycle if the conditions of
the top lifecycle are too broad.
An comman example that I've seen on other repositories are these
conditions in the following order:
1) assets of type ABC
2) assets of type ABC and Category QXR
Because (1) is too broad it will permanently hide (2) since it will be
selected for ALL assets of type ABC, even those with category QXR.
The order should be the more broad at the bottom and the more specific
at the top.
--
Rich Kulp
Rational Asset Manager developer
Thanks Rich and Sheehan for your responses. This would be really helpful.
I have one more query. Since community admin wants to do this operation with hundreds of assets, is it possible that he will perform the modification of assets using bulk update process and it will pick up the appropriate lifecycle. Or does batch operations in iRAM Web client circumvent the lifecycle selection event?
Thanks......Payal
I have one more query. Since community admin wants to do this operation with hundreds of assets, is it possible that he will perform the modification of assets using bulk update process and it will pick up the appropriate lifecycle. Or does batch operations in iRAM Web client circumvent the lifecycle selection event?
Thanks......Payal