Locking stream in DNG
In my DNG project, I have two streams in a component lets say Stream 1 and Stream 2, both streams are used parallelly, eventually all changes from Stream 1 are merged into Stream 2, now Only Stream 2 shall be used. I want to lock Stream 1 i.e. user shall be able to view data on Stream 1 but shall not be able to make any changes or shall not be able to edit data in Stream 1.
Is this doable in DNG?
4 answers
I haven't tried this, but you may be able to prevent users editing by:
a) create a Team that only has an admin person as member (with role which has permissions to edit)
b) in the team ensure the Everyone role has no permissions to edit
c) and then assign Team Ownership of all the artifacts in the to-be-uneditable stream to this team.
All project members/team members will be able to see the artifacts, but not edit (apart from the lucky admin person) because they only have Everyone role in that team.
You should probably try this out on a sandbox project.
HTH
Ian
I don't think there's a simple solution.
You could test setting up different project area roles (for Stream 1 and Stream 2) but every time you created a new stream you would need to create more roles.
If you went that route you could define different permissions on e.g. "Save Artifact" and "Save Link" for the role to prohibit modification of artifact types per stream and disallow and kind of saving on Stream 1. Then you'd have to assign people to that role and to the role intended for Stream 2 editors. Honestly I think this would be an administration nightmare if you were often creating streams.
Alternatively, you could, per stream, use "change set enforcement" and add or change roles to set permissions and restrict who may create/deliver change sets in the project area. It wouldn't be fool-proof and you'd need to retain some person/people in a role who could create and deliver change sets but at least you'd have a gatekeeper to prevent 'unwanted' updates to your stream(s).
To prevent edits on old Streams in my projects I do the following
1) Check "To edit this stream, changes must be made in a change set"
2) Check "To deliver to this stream, change sets must be linked to an approved change request or work item"
On our project we do not have 'approved change requests or work items' so this effectively prevents any updates to the stream.
On our project we do not have 'approved change requests or work items' so this effectively prevents any updates to the stream.
If we did need to update the stream I would temporarily change these setting to allow it.
It would be possible for someone to create a change set, do some work it and then find that they couldn't deliver it and be annoyed that they wasted their time on the updates but that has not happened yet
If you use Global Configurations, you could set the GC configuration to be a baseline. That would prevent anyone using that GC from being able to make any changes to the stream.
Of course if they go directly to the stream in a local configuration they can do whatever they want. But if your users are trained to use the GC and not a local configuration, this may work for you.