![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Email on Modify Attribute... Topic Summary: Getting the original values in post-trigger Created On: 26-Mar-2007 08:33 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello all,
I have a slightly different problem with email notifications using the Synergy/Change CSAPI (i am already able to send them at least
![]() |
|
![]() |
|
![]() |
|
We ran into a similar problem. The best we've come up with so far is to parse the transition log, starting from the end, to find the previous value. Of course this only works with attributes where the original value is logged in the first place. (Not the case for text attributes or with the [state name]_id and [state_name]_time attributes.) Also, if the transition log is greater than 32000 lines, the CSAPI can't seem to handle it. In those cases we had to go through a CM session to get the transition log text.
I'd be interested to know if someone else has found a better solution. -Julie Lee |
|
![]() |
|
![]() |
|
There is always the possibility to use pre-triggers to save the attributes in a DB or a file, using the username and CR number as an ID and then read them in the post-trigger, but that has some limitations:
- Pre-triggers are available only on transitions. Maybe someone knows how to put them on pre-state modifications. - We should assign all of them manually. - If we use normal pre-trigger, it will slow the transitions if the data is too much. - If we use an asynchronous pre-trigger, it may finish after the running of the post-trigger (also if the data is too much). But overall it is possible. I wanted to know if there is a better way ![]() |
|
![]() |
Telelogic SYNERGY
» SYNERGY/Change
»
Email on Modify Attribute...
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.