Hi
When I try to add a new attribute to the list of attributes that are configured for review in the CPS for the Module, I get a dxl error (<utils/copyops.inc:308> cannot change the type of an attribute)
I know that we did change the Type of an attribute on the Module that is already configured for review in the module. I'm not sure but I thought it might fix the error if I remove that attribute(old) from list of configured attributes in the CPS and then reselect it. That way DOORS would see the new type and I can add the others attributes as well. But I am wondering if that would affect any current proposals.
Can someone know how to fix the dxl error so we will be able to configure the CPS with new attributes that require change proposals?
Thanks in advance for your help.
SystemAdmin - Tue Sep 29 13:19:01 EDT 2009 |
|
Re: CPS, updating list of attributes on DOORS 8.3
SystemAdmin - Tue Sep 29 14:46:58 EDT 2009
You can go back to IBM to have them change the dxl -- That is only option but that still will not fix you problem.
IBM will problably tell you to keep out of the CPS system unless you use their supplied GUIs. Given that -- IBM probably would tell you to start over.
If anyone tells you how to fix the problem -- don't let IBM know what you did -- might tick them off.
|
|
Re: CPS, updating list of attributes on DOORS 8.3
llandale - Tue Sep 29 16:14:03 EDT 2009
You no doubt changed the source 'type' by renaming the old attr, creating the new one with the right name and new type, copied the values from old to new, and deleted the old. In order to make History less confusing, you no doubt did these things while you did those things: turn off History for the old; Create the new with History off; After the copy, turn History on for the new. That should result in only two extra Histories, both are 'modify attr' with no details.
You will need to do that same thing for the corresponding 'Proposed nnn' attr in the CPS partner module, where 'nnn' is the name of your attribute.
The 'copy' might be the tricky part; you won't be able to do this (in general) if the new type is int or real, and you probably have a problem if its Enumerated.
..err.. I of course mean theoretically do that. You would never mess with the CPS system, IBM might get ticked about that. And you would never tell them I said it worked perfectly every time I've done it ..err.. dreamt about doing it.
There is nothing special in the CPS system; its all done with normal modules and objects and links.
|
|
Re: CPS, updating list of attributes on DOORS 8.3
SystemAdmin - Wed Sep 30 09:02:25 EDT 2009 llandale - Tue Sep 29 16:14:03 EDT 2009
You no doubt changed the source 'type' by renaming the old attr, creating the new one with the right name and new type, copied the values from old to new, and deleted the old. In order to make History less confusing, you no doubt did these things while you did those things: turn off History for the old; Create the new with History off; After the copy, turn History on for the new. That should result in only two extra Histories, both are 'modify attr' with no details.
You will need to do that same thing for the corresponding 'Proposed nnn' attr in the CPS partner module, where 'nnn' is the name of your attribute.
The 'copy' might be the tricky part; you won't be able to do this (in general) if the new type is int or real, and you probably have a problem if its Enumerated.
..err.. I of course mean theoretically do that. You would never mess with the CPS system, IBM might get ticked about that. And you would never tell them I said it worked perfectly every time I've done it ..err.. dreamt about doing it.
There is nothing special in the CPS system; its all done with normal modules and objects and links.
Thanks for your replies. it is another what to solve this issue, if so could you let me know or advice?
thanks
|
|
Re: CPS, updating list of attributes on DOORS 8.3
llandale - Wed Sep 30 13:27:40 EDT 2009 SystemAdmin - Wed Sep 30 09:02:25 EDT 2009
hi
Thanks for your replies. it is another what to solve this issue, if so could you let me know or advice?
thanks
|
|