How do we migrate the existing assets to a master lifecycle of a community?
We have upgraded our RAM server to 7511.Earlier for a community we were using legacy review processes but now we plan to shift to master lifecycle.
We have learnt that after you configure a master lifecycle for a community you can migrate the existing assets such that the older instance of the lifecycle/review process that they have can be overwritten by this master lifecycle.
Can you please provide us the steps on how can this be achieved?
We have learnt that after you configure a master lifecycle for a community you can migrate the existing assets such that the older instance of the lifecycle/review process that they have can be overwritten by this master lifecycle.
Can you please provide us the steps on how can this be achieved?
3 answers
There is not automatic way to move legacy lifecycle asset into a Master based lifecycle per sea.
In general, if asset switches a lifecycle (because of configuration changes) it will:
Stay in the same state, if the new lifecycle is based on the same workflow.
Start from the beginning, if the new lifecycle is based on a different workflow.
In the case of a legacy lifecycle, it is not based on a workflow so no cigar. However you can follow the following process to migrate.
Create a new workfllow ... and have a mapping handing from the states in the legacy to the new life cycle.
For each state in the legacy review (call it state "O" that is mapped to state "N" in the new lifecycle):
In general, if asset switches a lifecycle (because of configuration changes) it will:
Stay in the same state, if the new lifecycle is based on the same workflow.
Start from the beginning, if the new lifecycle is based on a different workflow.
In the case of a legacy lifecycle, it is not based on a workflow so no cigar. However you can follow the following process to migrate.
Create a new workfllow ... and have a mapping handing from the states in the legacy to the new life cycle.
For each state in the legacy review (call it state "O" that is mapped to state "N" in the new lifecycle):
- Configure the new lifecycle so that asset will automatically be moved to state "N" (remove the manual rules on the transitions).
- Search for all assets in the legacy review (use: _stateWorkflowId_:(com.ibm.ram.legacy) in the search text area. Also, filter on state "O" ... so you get all assets in state "O" in legacy review.
- bulk update these assets. .... which will force them to move to the new lifecycle, and flow to state "N"
Comments
There is OSLC Asset Management documentation and samples located on the OSLC Wiki site --> http://open-services.net/wiki/asset-management/OSLC-Asset-Management-2.0-Samples/
Another option would be to use the RAM Java client API calls.
Either option you still need to follow Gili's suggestion for setting up and configuring the lifecycles so they map correctly from legacy to lifecycle... and search using the criteria suggested.
Another option would be to use the RAM Java client API calls.
Either option you still need to follow Gili's suggestion for setting up and configuring the lifecycles so they map correctly from legacy to lifecycle... and search using the criteria suggested.
Comments
