Operation id for a specific workitem save action
Hi All,
I have a requirement to trigger a server side plugin (say Follow up action) when Save operation is performed in aworkitem of specific type and not for all workitem save operations
As of now, I have used the common workitem save operation id: "com.ibm.team.workitem.operation.workItemSave
Is it possible to limit the trigger to happen only for a specific workitem save operation? or Is there any operation id available for any specific workitem save operation?
Please drop your comments ASAP
Thanks in Advance
I have a requirement to trigger a server side plugin (say Follow up action) when Save operation is performed in a
As of now, I have used the common workitem save operation id: "
Is it possible to limit the trigger to happen only for a specific workitem save operation? or Is there any operation id available for any specific workitem save operation?
Please drop your comments ASAP
Thanks in Advance
2 answers
The workitem Save operation event is fired for every workitem save.
the chain of participants/advisors is called on that single event.
why can't your code filter out all the other changes it doesn't care about?
for example, I have an advisor that is only interested in saves where dependant workitems are not resolved.
if any other save event occurrs, my code is called, but doesn't do anything (well, it checks for the condition and exits without any errors)
the chain of participants/advisors is called on that single event.
why can't your code filter out all the other changes it doesn't care about?
for example, I have an advisor that is only interested in saves where dependant workitems are not resolved.
if any other save event occurrs, my code is called, but doesn't do anything (well, it checks for the condition and exits without any errors)
The way Sam describes it is, as far as i know, the way it is supposed to be done. Please read the Extensions Workshop, it describes that the plugin should try to identify if it needs to do more work as quick as possible and just stop if there is nothing to do. It is way easier for the extension to decide than trying to provide special capabilities in the extension point provider.