Locking down an Asset
Hi,
I am trying to understand if it is possible to lock down an Asset when it reaches a certain state. What I mean by lockdown is not allowing changes to the attributes, relationships or artefacts. We do however want to be able to progress from one state to another. We have an Asset Type called Release that represents a release. There is also an associated lifecycle. The lifecycle has a start state of draft. In this state we want to be able to make changes to all of the asset parts, i.e. relationships, attributes, etc. Then when we are happy that the asset is correct we move to the next state, submitted. It is at this point that we do not want to allow any more changes to the asset, other than the ability to move it onto the next state, accepted. It would seem that a policy would be the best way to accomplish this. However, there does not appear to be any out of the box policy that gives us this capability. Is using a policy the best approach and if so is there already a policy that gives me this ability? If there is no out of the box policy then would writing a custom policy allow me to achieve our goals? Thanks for your help Des Drury |
14 answers
no... just a bit semantics...
But the net net is that with the ability to separate updates from change state will solve the problem, as the expectation is that all Validation policies will run an a previous state before entering the "no update" state. |
This seems to have gotten way down into the weeds... let's go back to the original scenario:
Why not simply: 1. Select the option in the lifecycle config: 2. Use the out-of-the box policy called "Modify Asset Owner", and "Modify Lifecycle Manager" (if needed) so that when transition to the The result of this would be a Will this work? |
|
Sounds good... may also save the original owner in a dedicated User attributed before the policy changes the owner.
|
This seems to have gotten way down into the weeds... let's go back to the original scenario:
Why not simply: 1. Select the option in the lifecycle config: 2. Use the out-of-the box policy called "Modify Asset Owner", and "Modify Lifecycle Manager" (if needed) so that when transition to the The result of this would be a Will this work? Although this would effectively lock certain users out from being able to edit the Asset it is not exactly what we are looking to achieve. If we look at the group Release Managers, we want the members of this group to be able to edit the Release Asset when it is in draft, and then only change the state once it moves past draft. If we lock the members of this group out once it moves past draft then an administrator will need to change the state. And if we do not lock them out, so that they can change the state, then they can also change the content. Whilst update and state change permissions are all lumped together I do not see any way to lock down the content of an asset whilst still allowing the state to be changed. Cheers. Des |
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.