A question for ddm users...
How do you handle your read only data once it has been released (state change) in ddm?
Here's the workflow:
1. Designer updates the ProE data and saves to database at state of WORK. (or any state that designers have modify permissions on)
2. Designer sends package of data to an approver (who may only be using ddm office).
3. Approver then releases the package to state RELEASED (in ddm office). NB This state is read only to all users to prevent overwriting RELEASED data.
Released cycle complete.
Designer then wishes to work with the RELEASED data for another reason. Here's what happens:
Designer opens released data in ProE and ddm 'notices' that the native file attributes are different to the ddm metadata (as Release task was performed in ddm office) so ProE saves a new copy of each file in the working folder.
As the data opens in ProE it saves each individual file (locally in the working folder) and depending on the size of the assembly, takes a considerable time to load (an assembly we have that takes typicially 2 mins to load, now takes 3/4 hour).
Now here's the crunch, as the designer saves the file, he does not have permission to save back to ddm the updated attributes because of the (correctly) set ACLs for a RELEASED object. Next time the assembly is loaded into ProE, the whole re-save scenario starts again.
So how are you doing this? Is there a simple work-around I have missed?
The important underlying requirement though, is no-one has access to modify RELEASED data. This protects the data from inadvertant changes.
Any contribution greatly received.
How do you handle your read only data once it has been released (state change) in ddm?
Here's the workflow:
1. Designer updates the ProE data and saves to database at state of WORK. (or any state that designers have modify permissions on)
2. Designer sends package of data to an approver (who may only be using ddm office).
3. Approver then releases the package to state RELEASED (in ddm office). NB This state is read only to all users to prevent overwriting RELEASED data.
Released cycle complete.
Designer then wishes to work with the RELEASED data for another reason. Here's what happens:
Designer opens released data in ProE and ddm 'notices' that the native file attributes are different to the ddm metadata (as Release task was performed in ddm office) so ProE saves a new copy of each file in the working folder.
As the data opens in ProE it saves each individual file (locally in the working folder) and depending on the size of the assembly, takes a considerable time to load (an assembly we have that takes typicially 2 mins to load, now takes 3/4 hour).
Now here's the crunch, as the designer saves the file, he does not have permission to save back to ddm the updated attributes because of the (correctly) set ACLs for a RELEASED object. Next time the assembly is loaded into ProE, the whole re-save scenario starts again.
So how are you doing this? Is there a simple work-around I have missed?
The important underlying requirement though, is no-one has access to modify RELEASED data. This protects the data from inadvertant changes.
Any contribution greatly received.