![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Created CR using customized lifecycle - how to edit lifecycle and have previously created CRs reflect this? Topic Summary: Created On: 22-Sep-2004 23:42 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Oh. That IS a conundrum - I've never noticed then when we've done a similar update. Dare I suggest contacting the TL support line, because I've no idea why it would happen. Would a server stop/restart be needed perhaps, to kick-start the attributes new behaviour? | |
![]() |
|
We have customized our CR Process, and like many ideas it is a work in progress. Things that seemed like a good idea no longer make so much sense when examined in the actual production environment. Ex: made some attributes read only when there is need to modify them, needed to add further attributes, etc....
We then further edit the Lifecycle and are left with several old CRs that do not reflect the updates to the lifecycle. Is there any way to "refresh" these CRs? Thanks! |
|
![]() |
|
![]() |
|
You could write a short script to query the database for the CRs of interest, then modify the attributes that you need, and have it loop through to do all of them?
It should be faster than manually doing it, especially if you've someone familiar with Perl |
|
![]() |
|
![]() |
|
I'm not creating new attributes, or aynthing like that and I know that I can use the command line to edit the actual values if need be.
Mainly I'm changing dialogs, how much information is displayed, which attributes are modifiable, changing role security, etc.... The previous CRs do not reflect these changes. It appears that these CRs continue on their merry path to completeness with the old dialogs, old security, and so on. Some of our CRs will continue the entire length of the project and I would REALLY like to find a way for them to reflect the changes to the lifecycle. Is there any way to do this? Attribute values are not the main issue. Consistency of our process and security are a bit above the actual value of the attributes, especially since these can be set from the command line if necessary. It doesn't make sense to most developers that we can have many CRs in our system that are displayed differently when they are in the same state. Thanks for the previous response LLarsen |
|
![]() |
|
![]() |
|
Oh.
That IS a conundrum - I've never noticed then when we've done a similar update. Dare I suggest contacting the TL support line, because I've no idea why it would happen. Would a server stop/restart be needed perhaps, to kick-start the attributes new behaviour? |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.