Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic SYNERGY (steve huntington)
Decrease font size
Increase font size
Topic Title: Subsystem property in Tasks
Topic Summary:
Created On: 25-Jul-2006 08:25
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Aitor Illarramendi, on Thursday, July 27, 2006 8:30 AM

Answer:
Many thanks Lutz. I think that as you say it could be an interesting way of making task_x_subproject relation. But you have frightened me with the information about it's oldness and possible inconvenience. I'will have to think about the implementation_cost/benefits relation before using this attribute. Anyways, I know that it would not have any influence but, having subsystem names that are not specific of the project and that are read and not understood by the developers make some confusion in the process too. I know that marking any value of this attribute if we no make the subsequent query and other implementations goes nowhere but... I allways pray for some stereotype project configuration templates for all the CM in order to avoid this all specific handmade craftsman works (all different) for each project.
 25-Jul-2006 08:25
User is offline View Users Profile Print this message


Aitor Illarramendi

Posts: 38
Joined: 20-Feb-2006

Hello: I've read in several documents about the existence of this property for tasks. Looks like an extra labelling option for tasks and changes related to objects. But, I have two questions that I can't resolve by reading the documentation because I don't find the answers: 1.- Does this labelling have any speciall feature that will enhance the CM mechanism? (the CCM book says that to set this value is only for my convenience, ???, does it mean that the Task has an additional attribute that is better recommended to be by default with None value because has no use?) Could anyone explain me if I could use it for grouping tasks, changes and related things (at least I think that it would, for queries). 2.- Where could (an admin, build manager, whoever) this attribute enumerated values be changes? I'm trying to find it in the documentation, but no luck. The CCM book says that a CM admin can do it. Many thanks in advance. Best regards.
Report this to a Moderator Report this to a Moderator
 27-Jul-2006 07:11
User is offline View Users Profile Print this message


Lutz Zollikofer

Posts: 44
Joined: 31-Jul-2003

Hi,

as far as I know subsystems are relics of the pt-tool of the ancient ages of Continuus. We're still using them to group tasks to subprojects. You can modify the subsystem list by editing the file ///pt/attrange.dft. As you can see, the subsystem list is specific to each database. Furthermore you've to define a query for your query based folders, eg the all completed tasks folder.
Be aware of it's a trap, because developers often forgot to select the correct subsystem when assigning a task in a hurry.

ciao, Lutz
Report this to a Moderator Report this to a Moderator
 27-Jul-2006 07:17
User is offline View Users Profile Print this message


Lutz Zollikofer

Posts: 44
Joined: 31-Jul-2003

Sorry, the path information got lost at saving the reply.

The correct path is: /db path/db name/pt/attrange.dft.
For example: /ccmdb/test/pt/attrange.dft, when you've installed the ccm archive and cache in /ccmdb and you're using database test.
Report this to a Moderator Report this to a Moderator
 27-Jul-2006 08:30
User is offline View Users Profile Print this message


Aitor Illarramendi

Posts: 38
Joined: 20-Feb-2006

Answer Answer
Many thanks Lutz. I think that as you say it could be an interesting way of making task_x_subproject relation. But you have frightened me with the information about it's oldness and possible inconvenience. I'will have to think about the implementation_cost/benefits relation before using this attribute. Anyways, I know that it would not have any influence but, having subsystem names that are not specific of the project and that are read and not understood by the developers make some confusion in the process too. I know that marking any value of this attribute if we no make the subsequent query and other implementations goes nowhere but... I allways pray for some stereotype project configuration templates for all the CM in order to avoid this all specific handmade craftsman works (all different) for each project.
Report this to a Moderator Report this to a Moderator
 31-Jul-2006 13:42
User is offline View Users Profile Print this message


michael Barnes

Posts: 85
Joined: 12-Nov-2003

As Lutz says, subsystem no longer has any implications for the operation of the core Synergy product (there are no rules in Synergy based on this attribute), and so users are at liberty to use it for wahtever purposes they wish.

In my company we use it to identify the project lifecycle stage that the task is aimed at, with values such as Analysis, Design, Code, Test, Prototype, User Documentation. It is used by us purely to generate management reports.


If you wish all future projects to use the same list for the same purpose, then you should unpack the template pack file, make the changes to attrange.dft, then re-pack the template pack file. Unfortunately, existing projects will need to be updated individually..

You can, however, make the same list available to all projects via SYNERGY/Change, and if you only set this attribute via Change, then no updates are needed to attrange.dft (although you may need to update attrange.dft to perform queries in CM).
NOTE that the lists are maintained separately in Change (one list per installation, OR project-specific lists) and in CM (each database has its own list).
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic SYNERGY forum.
There are currently 0 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 15:34.
There are currently 0 guests browsing this forum, which makes a total of 0 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.