How an operation participant works?

Hi Muthukumar,

I looked into the stale data. It appears you can't just modify the workingcopy in the participant. So I loaded the work item again and then I was able to save it in the participant.

wiServer = getService(IWorkItemServer.class);
IWorkItem wi = (IWorkItem)wiServer.getAuditableCommon().resolveAuditable(newState, IWorkItem.FULL_PROFILE, monitor).getWorkingCopy();

// Add a comment
IComments comments = newState.getComments();
IComment newComment = comments.createComment(this.getAuthenticatedContributor(),XMLString.createFromPlainText("Jazz note #2"));
wi.getComments().append(newComment);
                        wi.setHTMLDescription(XMLString.createFromPlainText(newState.getHTMLDescription().getPlainText()+"t"));
wiServer.saveWorkItem2(wi, null, null);

Hi, not sure why this didn't post correctly. I assume you have solved it yourself, below is what to do in a participant to modify and save a work item avoiding the stale data.

Please be aware that this is a new save operation and your followup action triggers again. i found this with some hint on how to avoid it: https://jazz.net/forum/questions/49087/how-to-know-who-is-saving-the-wi-user-or-participant#52519

Hi Muthukumar,

I looked into the stale data. It appears you can't just modify the workingcopy in the participant. So I loaded the work item again and then I was able to save it in the participant.

wiServer = getService(IWorkItemServer.class);
IWorkItem wi = (IWorkItem)wiServer.getAuditableCommon().resolveAuditable(newState, IWorkItem.FULL_PROFILE, monitor).getWorkingCopy();

// Add a comment
IComments comments = newState.getComments();
IComment newComment = comments.createComment(this.getAuthenticatedContributor(),XMLString.createFromPlainText("Jazz note #2"));
wi.getComments().append(newComment);
                        wi.setHTMLDescription(XMLString.createFromPlainText(newState.getHTMLDescription().getPlainText()+"t"));
wiServer.saveWorkItem2(wi, null, null);

Hi,

all preconditions and followup actions (advisors/participants) are triggered by operations such as work item save. That does not at all mean that they are actually doing things like saving or modifying work items.
A typical precondition for example checks if the save should happen based on some data. A follow up action might do something after an operation that is more or less unrelated to the data that triggered the save.

So if you want to modify data in such an operation you need to do the necessary steps to be able to.

By the way, this shows how to create a work item using an operation: https://jazz.net/wiki/bin/view/Main/ProgrammaticWorkItemCreation. You can also use it to modify work items.

I am not sure if it is possible to prevent the operations for the subsequent save you do. You could modify the work item in a way that prevents its save for example. In this case you would like the save to fail.

Dear Ralph,

I want to modify the Data of a work item from Followup condition. Lets say I want to add a Comment to the current WI (Which we are going to save) if the user has changed its Parent link.

I have tried by just adding the code for inserting comment in WI. But the comment not saved in WI. Then I add the code for Saving  the work item [saveworkitem2].
that code is working fine if user does'nt modify any data except the LINKS.
if any other modifications (State Change / Data change), Then I am getting Stale Data exception.

Guide me in this regards.

Thanks in advance

Hi, Muthukumar,

please check these posts:

https://jazz.net/forum/questions/38138/stale-data-problem-in-plain-client
https://jazz.net/forum/questions/50984/sate-data-exception-on-bulkcocurrent-workitem-update

I haven't done something like this, and I am not sure what happens. One thing with stale data is reread the work item. The other thing is, that the code you use might just not be enough.

Currently, if creating or modifying a work item I use the WorkItemOperation from https://jazz.net/wiki/bin/view/Main/ProgrammaticWorkItemCreation where the operation does all that is needed to load and save.

This is code I used in the past to update code using a workingcopy:

        IWorkItemWorkingCopyManager wcm = workItemClient.getWorkItemWorkingCopyManager();        

        wcm.connect(workItem, IWorkItem.FULL_PROFILE, null);
       
        try {
            WorkItemWorkingCopy wc = wcm.getWorkingCopy(workItem);
           
            wc.getWorkItem().setHTMLSummary(XMLString.createFromPlainText(summary));
            IWorkItem wi = wc.getWorkItem();
            List <IAttributeHandle> attribs = wi.getCustomAttributes();
            for (Iterator iterator = attribs.iterator(); iterator.hasNext();) {
                IAttributeHandle iAttributeHandle = (IAttributeHandle) iterator
                        .next();
                IAttribute anAttribute = (IAttribute)auditableClient.resolveAuditable(iAttributeHandle, IAttribute.FULL_PROFILE, null);
                System.out.println("AttName:" + anAttribute.getDisplayName());               
            }
            IDetailedStatus s = wc.save(null);
            if (!s.isOK()) {
                throw new TeamRepositoryException("Error saving work item",
                        s.getException());
            }
        } finally {
            wcm.disconnect(workItem);
        }

        System.out.println("Modified work item: " + workItem.getId() + ".");

 

Ralph, I agree with the approach.
I read a IBM article and understood that
1. Advisors are for checking the preconditions and Stop the save operation in case of any violation.
2. Participants should be used as followup conditions that is to modify the Other elements of the Artifacts based on the current work item.
3. If we want to change the attribute values of the Current Work item, then we need to add a Script based Calculated Values.

But, Instead of spending time in Scrip, As of now I added the Comment from the advisor plugin itself.

Thanks for your time.

Regards
Muthukumar