Asset Linking Question
Is it possible to link an Approved asset to another asset without resetting the Approved assets state back to Draft?
Essentially, I want to Modify the Approved asset and save the new linking, but I don't want to have to put the asset through another lifecycle. I have the Versioning Policy enabled so that changes to the Artifacts or the Description cause a new version to be created. I don't see anything that includes or excludes the Linking in the versioning policy configuration. Is what I'm describing possible? Thanks, |
17 answers
When the asset is in the draft state and you're looking at the general details page, do you see a 'Review' link on the left side of the page?
Click the pencil icon on the general details page to modify the asset. On the Submit page, the name of the lifecycle the asset will enter is displayed in the top right of the page. What is the name of the lifecycle? I'm trying to confirm that the asset is not somehow ending up in a legacy review. I know you said it is not, but I can't reproduce this problem in a lifecycle with the 'Default Versioning Policy' and I don't see how it's ending up in the draft state. |
When the asset is in the draft state and you're looking at the general details page, do you see a 'Review' link on the left side of the page? Hi Sheehan, I appreciate the help, but I'm past the "is it plugged in" stage with lifecycles. It's definitely using a custom community lifecycle that I created, based on a master lifecycle that I also created. The lifecycle is called ISO 9001 Compliant Lifecycle and it shows up on the screen. All of the proper states come up in the Actions bar. Plus, I have no defined actions for going from Approved back to Draft. It's intentionally left as a manual action. I really do believe the Asset Versioning policy is somehow causing the strange behaviour. When I remove it, I can link and save an approved asset without it going back to Draft. I'll play with it more and see if I can find any other clues. Thanks, |
Hi,
You call it Asset Versioning Policy and we named if Default Versioning Policy. Are you sure that these are same entities? Are you just calling it Asset Versioning Policy as a short hand or is that what is really displayed on the browser? If that is what is really displayed then that may be a custom policy and not our policy. Our policy does absolutely nothing with changing the asset's state. All it does is return good or fail results. It is then up to the lifecycle to handle it. By the way make sure you are looking at the Asset's lifecycle itself and not the community or master lifecycle. There could of been a asset level customization that you didn't notice or expect to be there. Rich |
Hi, Hi Rich, Yeah, I meant Default Versioning Policy. We only use built-in policies. We have no custom policies. I don't know if you have a place you can test this but here is what we see: 1. Have an asset with the Default Versioning Policy set in the Review state. 2. Move the asset to the Approved state. 3. Have no actions defined for moving the asset from Approved to Draft, other than the Manual Action. 4. Edit the Approved asset to link it to another asset. When we do that, the asset somehow goes back to Draft once it is saved with the new link. I can't tell why that is happening. Cheers.... |
|
Hi,
Couple of questions: 1) What configuration did you apply to the Default Versioning Policy? It needs some configuration. 2) What is the name of the lifecycle, and the workflow. By default we supply two types of workflows, Stanard and Migrated, that have Draft and Approved states. Thanks, Rich |
Hi, I used the Standard workflow. I've used various configurations and they all seem to work the same, but here are the specifics for one: Versioning schema: numeric Change in asset classification: No version change required Change in asset artifacts: Version must increase Change in asset description: Version must increase On failing the policy: Issue Error Thanks, |
|
Hi,
One more thing. On which states is the Default Versioning Policy set. Policies are per state and not global for a lifecycle. I wasn't clear from your description here. Thanks, Rich |
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.