![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Policy for Baselining Topic Summary: Created On: 16-May-2006 14:33 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Somewhere in v7 Telelogic implemented a feature which effectively hides many History Records from folks who don't have R access. In previous versions, folks who don't have R access to an object could still see the History of that object; Telelogic tried to "fix" that. The net affect is that Browsing History often results in "Read Locked Data" records.
I'm not sure of the details, but suspect that the Accesses at the time of the baseline are captured in that baseline. Thus, if a Group has R access then the CURRENT membership of that group has R access to the baseline, even if they didn't have R access at the time of the baseline. This means that we must maintain old Groups just in case these groups are required for access to Baselines. I don't like this feature. It would be better if they implemented a policy where folks who currently have RMCDA access to the module, can see all History records, even if they don't otherwise qualify. Anyway, I'm wondering of folks here have figured out a reasonable baselining strategy that covers this issue. I have to admit I'm tempted to write a DXL that captures all the Access Records everywhere in the module, resets them all to Inherited, baselines the module, then reestablishes all the ARs. - Louie |
|
![]() |
Telelogic DOORS
» Administration
»
Policy for Baselining
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.