On Thu, 06 Aug 2009 13:23:03 +0000, mikyjpeg wrote:

Maybe I have not understand clearly the relationship between
event/follow-up actions.

In process configuration there is a section on event handling. For
example: "WorkItem State Changed Event" is an Event or an Event Handler?
So do I have to write an EventHandler extension or a simple follow-up
extension?
And, in both case, which are the ids to use in order to catch that
event?
Is there a list of this event ids??
The problem is that there is no example or snippets, no predefined
follow-up linked to an event (instead of behaviour where I had find
example that drive me to write pre-condition and follow-up extensions).

In the Process realm, Change Events are analogous to Operations and Event
Handlers are analogous to Follow-up Actions. Just as you can register
follow-up actions for operations, you can register handlers for events.
Once your event handler is registered, teams can configure your event
handler in their process.

I'm not sure if we have a comprehensive list of the Operations and Change
Events that RTC contributes.

If I wanted to know a change event id, here's what I'd do:
1. Open a project area and go to the Process Configuration Source tab.
2. Place the cursor inside the "behavior" element inside the "team-
configuration" element (if they don't exist, create them).
3. Press ctrl+shift to summon code assist and select the "Change Event"
template to insert a change-event element. The template will
automatically select the id attribute
4. Press ctrl+shift again to summon code assist. This will list the set
of available change events. If you select one, it will insert the id for
that event into the text.

--
Jared Burns
Jazz Process Team

On Fri, 07 Aug 2009 07:38:05 +0000, mikyjpeg wrote:

This is great, I have not think that it could run on process
configuration source. It works perfectly, thank you! Back to handlers I
understand. Maybe the word "follow-up" is confusing in this case because
the two things (behaviour follow-up and event follow-up) are developed
in two different ways.

Right. Event handlers aren't exactly the same as operation follow-up
actions, but we use the same term ("follow-up action") in the syntax and
the UI because the implementation differences don't matter to people
trying to use the product.

--
Jared Burns
Jazz Process Team

https://jazz.net/wiki/bin/view/Main/CustomPreconditionsTable#operations