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: Different submit forms based on problem type?
Topic Summary: Is there a way to have different submissions dialogs for defects and enhancements.
Created On: 6-Jan-2006 18:33
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.
 6-Jan-2006 18:33
User is offline View Users Profile Print this message


Eric Rzepka

Posts: 1
Joined: 15-Jun-2005

We are about to upgrade to 4.4. We have been running 4.2 with a custom package that has a "Submit Defect" and "Submit Enhancement" pair of buttons. All these do is route to different HTML pages that contain different fields for submission for defects compared to enhancements (creating a CR with either problem_type='defect' or problem_type='enhancement' in the process).

All our defects and enhancements go through the same simple set of states and transitions. Once a CR gets to a developer, the distinction between defect and enhancement is less important.

Hence, we like the ability to have defects and enchancement share states for the purposes of querying. And share a lifecycle (apparently 2 lifecycles in one process must have separately named states).

Is there any way in the process editor to mimic this in 4.4? Or are we stuck having separate "entered" states (like "defentered" and "enhentered") in order to have separate STARTHERE2abc transitions?

My preference is to do this using the editor and create a package, rather than crafting a package by hand to apply over the process package to do what we want (like we did with 4.2 and earlier).

One solution might be to have an "entered" state and a "defentered" state, and have defects go to the defentered state, and someone automatically transition all defentered CRs to the entered state. Is there a way to have a submission trigger that can automatically transition CRs to another state?

Any thoughts or help is most appreciated.

Thanks.

Report this to a Moderator Report this to a Moderator
 12-Jan-2006 11:34
User is offline View Users Profile Print this message


michael Barnes

Posts: 85
Joined: 12-Nov-2003

I believe that it is not possible directly, as you have suggested.

However, your suggestion of "entered" and "defentered" states suggests the following posibility but it is an untested suggestion:
    Use a post-transition TRELATION to change the state


TRELATIONs are defined in ptcli.cfg in the $CCMHOME/etc directory.
This is a self-documenting file (say Telelogic). The following hints may help, if you haven't played with this before:

- ACTION= "set"
- REL_NAME = "self"
- ATTR_NAME = "crstatus"
- ATTR_VALUE = "entered"

The following is an example of a TRELATION I have defined to set an attribute on creation. However, I do not know if this will work with the crstatus attribute.
Report this to a Moderator Report this to a Moderator
 10-Mar-2006 09:52
User is offline View Users Profile Print this message


Andrea Schreiter

Posts: 2
Joined: 30-Aug-2005

I had the same task in the past and I solved this by doing the following: 1. create for all states you want to use within the lifecycle parallel states like this: cr_entered (for Change Request) and entered (for Problem Reports) cr_in_review and in_review and so on... 2. create all transition forms you need, e.g. cr_entered2cr_in_review. These forms now allow you to have a complete different look and feel than the form for entered2in_review, this a really helpful. 3. the most important part is to define in the ptcli.cfg the postconditions for the merging of the parallel state into you lifecycle like this: [TRELATION] [NAME]verify change request[/NAME] [ACTION]verify[/ACTION] [REL_NAME]self[/REL_NAME] [ATTR_NAME]crstatus[/ATTR_NAME] [ATTR_VALUE]cr_entered[/ATTR_VALUE] [/TRELATION] [TRELATION] [NAME]set change request crstatus to entered[/NAME] [ACTION]set[/ACTION] [REL_NAME]self[/REL_NAME] [ATTR_NAME]crstatus[/ATTR_NAME] [ATTR_VALUE]entered[/ATTR_VALUE] [/TRELATION] 4. define the postconditions in the lifecycle and make sure that the crstatus is on the transition form modifiable. 5. use attribute security to exclude the crstatus from all modifiable attributes for normal users. 6. create package.... This is working, we are using it. Good Luck, Andrea
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic SYNERGY forum.
There are currently 1 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 1 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.