![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Updating CPS configuration when attributes change Topic Summary: Updating CPS configuration when attributes change Created On: 16-Mar-2005 15:44 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Well, I think I've finally figured it out myself. It has nothing to do with the access rights. When you want to update the configured attributes for CPS, this function works fine if you are adding or deleting attributes to CPS, but if you want it to update an already configured enumerated attribute, using the CPS configure tool doesn't work. (Maybe they never considered this scenario, but it really seems like an oversight to me.) Furthermore, it appears that the CPS pulls its attribute lists and the drop down enumerated values that it DISPLAYS IN THE CP FORM from your original formal module, BUT the values it actually USES, it gets from what is contained the CPS module, that got configured when you first set it up. This is why I was getting the error. So when you want to change the configured content of an enumerated attribute type, instead of using the CPS configure tool, you have to open the CPS module in edit mode and actually modify your Attribute/Type in the CPS module. Keep in mind your attribute is named 'Proposed - my attribute - | |
![]() |
|
Hi -
I'm receiving an error in my Change Proposal system that I'm hoping someone can help me resolve. We have Change Proposals configured to include a few attributes in our requirements that are enumerated lists. One of them is Spiral. It shows up in our CP form and we can select the desired enumerated value for the proposed change. This has been working fine with no errors ever since we initially set it up. We recently added a couple of new planned build phases so I updated the Type enumerated list for Spiral in the requirements module. I then went to submit a change proposal to add and modify requirements and allocate them to one of the new planned Spirals. Received an error that "there was a problem with the 'Proposed Spiral' attribute, invalid enum value: "<my new value>". I figured oh, I probably needed to just update the configuration. So I went through the configure CPS steps again and tried again, it still does not work. I tried removing my attribute from the CP configuration and then putting it back in and it still didn't work. I even added another attribute that uses the same Type (with the updated enum list) into my module, then reconfigured CPS to include that new attribute, and tried submitting again, and it gives the same error. It does NOT give the error with the orig Spiral attribute or the new one, if you use one of the original Type enum values that were included when it was FIRST configured way back when... But it always gives the error if you use any of the new values. So it appears to be an issue with the Type definition, not the Attribute. Has anyone ever seen this error? Has anyone ever successfully updated an enumerated Type/Attribute and successfully used it in CPS without errors? Please help!! Thanks, Colleen ![]() |
|
![]() |
|
![]() |
|
Hello Colleen.
If you have added new enumeration constants to the attribute's type, and it has specific access rights, I think the access rights might be set to Inherit from Parent. You might want to check that you've cleared the Inherit from Parent checkbox after you've added the new values. Hope this helps. Ewen Miller. QinetiQ |
|
![]() |
|
![]() |
|
ok. I just went and tried that and it had no effect, still get the same error.
|
|
![]() |
|
![]() |
|
Well, I think I've finally figured it out myself. It has nothing to do with the access rights. When you want to update the configured attributes for CPS, this function works fine if you are adding or deleting attributes to CPS, but if you want it to update an already configured enumerated attribute, using the CPS configure tool doesn't work. (Maybe they never considered this scenario, but it really seems like an oversight to me.) Furthermore, it appears that the CPS pulls its attribute lists and the drop down enumerated values that it DISPLAYS IN THE CP FORM from your original formal module, BUT the values it actually USES, it gets from what is contained the CPS module, that got configured when you first set it up. This is why I was getting the error. So when you want to change the configured content of an enumerated attribute type, instead of using the CPS configure tool, you have to open the CPS module in edit mode and actually modify your Attribute/Type in the CPS module. Keep in mind your attribute is named 'Proposed - my attribute -
Edited: 17-Mar-2005 at 15:38 by Colleen Caswell |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.