![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Username in object history corrupted Topic Summary: History Created On: 18-May-2007 20:08 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi.
Have anybody experienced any issues with DOORS 8.1 history? We are seeing the odd instance of a user name being corrupted in the object history - e.g instead of a certain username, we'll get a set of characters. I wonder if it's anything to do with unicode? We're using DOORS 8.1 with patch 006 clients Server 8.1.0.0 Win XP SP2 clients. Server OP: Win 2003 SP1 Regards, Ewen Miller QinetiQ |
|
![]() |
|
![]() |
|
Could you attach a picture for us to see this?
------------------------- pete.kowalski(at)motorola.com |
|
![]() |
|
![]() |
|
I have had reports of history records missing from our customers.
One example the history did not show a record for the creation of an object. It also did not show a change that was made. Has anyone else experienced this? We are using DOORS 8.1 ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
I've seen where is states "Read Locked Data" or something to that and you can't access the history record.
------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Tony, I have had that experience but I think was with 7.1 and I was told it was cleared up in 8.1 - guess not ( Or were we using 8.1 and it was fixed in 8.2 - I forget - I was with another company then). Somewhere in the one of the release notes there is a vauge reference to the problem.
When it happened the module was set up for shareable edit and it occurred when hitting the save button on the tool bar when in Shareable Edit mode. I was told by a fellow user to NOT use the save button and to use the drop down Save command. Why that makes a difference is beyond me. You might want to experiment with that in a Playground area. It was not a well documented or publicised issue and I heard from others at the UGC in Denver that had the same problem. I am now with another company and we are using 7.1 and I train folks not to use the Save button and we have not had any issues with lost history. Good luck Rob Kohl |
|
![]() |
|
![]() |
|
Odd, I've never got the habbit of using those standard icons in any Windows program; I routinely use Save and Print from the File menu.
Anyway, a little investigation reveals that the save icon uses "createItem modSaveItem" whereas the File >>Save menu item uses function saveModule(). Maybe someone who has decrypted the Telelogic code can chime in on whether the modSaveItem item uses the saveModule() function. - Louie |
|
![]() |
|
![]() |
|
I've seen where is states "Read Locked Data" or something to that and you can't access the history record. This mostly happens if you rename an attribute. Still happens in 8.3 ![]() Edited: 4-Sep-2008 at 11:23 by Tobias Gündel |
|
![]() |
|
![]() |
|
In an attempt to hide History from folks who lack read rights to objects and attributes, the History returns 'Read Locked Data' when the current user lacks R rights to the object or the attribute mentioned in the History. As you say this can happen when you rename an attribute since the old attribute name no longer exists and therefore nobody currently has R access to it. This should also happend to objects that have been purged.
The 'Administrator' never gets Read Locked Data. - Louie |
|
![]() |
|
![]() |
|
@Louie
Yes, thats correct, I asked Telelogic about it: As long as it is only one attribute you can identify it through the history to rename it to its origin and access the history again. |
|
![]() |
Telelogic DOORS
» Defect/Issue Tracking
»
Username in object history corrupted
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.