Can anyone tell me the rationale behind the frustrating "Read Locked Data" feature of DOORS. This prevents doing an audit of the history records. It seems absurd that a user with Database Manager powers and full RMCDA access to a module is not allowed to read the history records for deleted attributes and objects. Only the Administrator user can apparently see what is behind "Read Locked Data". However, the Administrator user account is usually owned by IT Support who do not understand the DOORS tool and will not assist you without a job ticket being raised which could take days before they respond to the ticket. In earlier versions of DOORS I don't recall this feature, why has it been implemented?
Paul Miller PMiller - Wed May 09 20:38:01 EDT 2018 |
Re: Rationale behind Read Locked Data? Louie had an explatation in thread https://www.ibm.com/developerworks/community/forums/html/threadTopic?id=77777777-0000-0000-0000-000014277571 |