![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: require task release Topic Summary: Require a release when a task is created or completed, CMS6.2 Created On: 11-Nov-2004 00:09 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: I ended up using 'allow_task_with_release_any' attribute which gets installed with CMS6.2 patch 38.1. Support had this to say: That is the same behavior I observed with this attribute, that is, the associated objects get checked in before the task release value is verified. I have further verified that this is the intended behavior of this attribute, although I agree that if the purpose of implementing it is to not allow associated objects to get checked in if the attribute is not set then it is of limited use. Another option would be to use the 'allow_task_with_release_any' attribute. By creating and setting this attribute to FALSE, when creating a task the user would be required to set it the release value to something other than Any. Here are the steps to create and set this attribute: 1) set role to ccm_admin 2) ccm query -n base -t model 3) ccm attr -c allow_task_with_release_any -t boolean -v FALSE @1 4) change role out of ccm_admin As a test, try to create a task with the release value set to Any. The only downside to this is that the user can set the release value to a bogus value, but this would have been true in the original attribute too. | |
![]() |
|
Hello!
I am running CMS6.2, SP1 on HPUX. Is there a way to require the release to be set when a task is created? I have found KB article NACM00245, "How can I require a task to have a certain attribute before it is completed? " and implemented it on two dummy DBs. In the first case, it corrupted something so that no task can be created because all the pull-down menu choices are gone. I must have made a mistake-maybe because I was not ccm_root? In the second dummy DB, I was ccm_root and it worked and an error message is displayed if the task has no release or "Any" as it's value. Unfortunately, the files are still checked in. So, if it is not possible to enforce setting the release on task creation, is it possible to disallow file check-in if the task completion fails? Thanks! Terry ------------------------- Terry Carpenter |
|
![]() |
|
![]() |
|
I ended up using 'allow_task_with_release_any' attribute which gets installed with CMS6.2 patch 38.1. Support had this to say:
That is the same behavior I observed with this attribute, that is, the associated objects get checked in before the task release value is verified. I have further verified that this is the intended behavior of this attribute, although I agree that if the purpose of implementing it is to not allow associated objects to get checked in if the attribute is not set then it is of limited use. Another option would be to use the 'allow_task_with_release_any' attribute. By creating and setting this attribute to FALSE, when creating a task the user would be required to set it the release value to something other than Any. Here are the steps to create and set this attribute: 1) set role to ccm_admin 2) ccm query -n base -t model 3) ccm attr -c allow_task_with_release_any -t boolean -v FALSE @1 4) change role out of ccm_admin As a test, try to create a task with the release value set to Any. The only downside to this is that the user can set the release value to a bogus value, but this would have been true in the original attribute too. ------------------------- Terry Carpenter |
|
![]() |
Telelogic SYNERGY
» SYNERGY/CM
»
require task release
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.