It is now possible to use save parameters in various API functions of the WorkItems API.
// example for saving without sending mails
var saveParameters = ["com.ibm.team.workitem.common.internal.skipMail"]
Api.WorkItems.saveWorkItemWithSaveParams(storyWorkItem, saveParameters );
Api.WorkItems.saveWorkItemAndChangeStateWithSaveParams(childWorkItem, "com.ibm.team.apt.story.defined", saveParameters);
//example for commiting without sending mails
Api.WorkItems.commitWorkItemWithSaveParams(storyWorkItem, saveParameters );
Api.WorkItems.commitWorkItemAndChangeStateWithSaveParams(childWorkItem, "com.ibm.team.apt.story.defined", saveParameters);
The Stages RTC Plugin is build with Java 1.8.
Precondition script timeout is 1min. Follow Up script timeout is 3h. Script Client script timeout is 3h.
The Stages RTC Plugin interprets process exports from Stages V7.8 and is able to work with dependent elements.
Stages Workflow
var enactedElement = Api.StagesWorkflow.getEnactedElement();
var dependent = enactedElement.getDependendElements();
var process = Api.StagesWorkflow.getCurrentProcess();
var dependent = process.getDependendElements();
The Stages RTC Plugin interprets process exports from Stages V7.6 and enables RTC to enhance the functionality of ProjectAreas.
For more information on Stages V7.6 and its new features read the Stages Documentation - Release Notes.
The Stages RTC Plugin receives events when a WorkItem is transfered from one state into another. The transfer states could be a specific state, a state group or any state.
Save Workflows in Stages are no longer supported, they could be modeled as Transition Workflows.
Enacted processes from Stages v6 could be automatically transformed into V7 processes. To keep the enactment functionality some adjustments have to be made. Please involve the responsible Product Consultant.
A Guide how to model Stages V7 Workflows is located at Stages Documentation - Model and manage process execution.
The Java Script API allows access to advanced RTC functionality. For a complete description of the functionality see the JavaDoc.
The new method
public IWorkItem createWorkflowWorkItem(final IProjectAreaHandle projectAreaHandle, final StagesElement stagesElement, @CheckForNull final IWorkItem generatingWorkItem, final String workItemTypeId);
replaces the old method
public IWorkItem createWorkflowWorkItem(final IProjectAreaHandle projectAreaHandle, final StagesElement stagesElement, @CheckForNull final IWorkItem generatingWorkItem) {
so it is possible to specify the type of the generated workItem.
The following methods are deprecated due to the change of the stages model:
@Deprecated
public String getStateAttribute(final StagesElement stagesElement);
@Deprecated
public boolean isGenericWorkItemType(final StagesElement stagesElement);
@Deprecated
public boolean isStateGroup(final StagesElement stagesElement);
- public StagesAssociation getActivityAssociation()
- public StagesElement getAssociatedElement()
- public StagesElement getCurrentStateElement()
- public String getCurrentStateId()
+ public String getEventEndState()
- public StagesElement getPreviousStateElement()
- public String getPreviousStateId()
+ public String getEventStartState()
- public StagesAssociation getScriptAssociation()
- public String getWorkItemTypeId()
- public StagesElement getWorkProductElement()
- public boolean isAnyCurrentState()
+ public String isEventEndStateAny()
- public boolean isAnyPreviousState()
+ public boolean isEventStartStateAny()
- public boolean isAnyWorkItemType()
- public boolean isCurrentStateGroup()
+ public boolean isEventEndStateGroup()
- public boolean isGenericWorkItemType()
- public boolean isPreviousStateGroup()
+ public boolean isEventStartStateGroup()
- public boolean isSaveWorkflow()
- public boolean isTransitionWorkflow()
+ public StagesElement getActivatorElement()
+ public String getOperationType()
+ public StagesElement getBoundProcessElement()
+ public StagesElement getEnactedElement()
+ public String getScriptParameters()
The following functions have to be replaced:
Enactment 1.0 stages v6 | Exection stages v7 |
---|---|
StagesWorkflow | |
.getActivityAssociation() |
not supported |
.getAssociatedElement() |
.getEnactedElement() |
.getCurrentStateElement() |
not supported |
.getCurrentStateId() |
.getEventEndState() |
.getPreviousStateElement() |
not supported |
.getPreviousStateId() |
.getEventStartState() |
.getScriptAssociation() |
not supported |
.getWorkItemTypeId() |
not supported |
.getWorkProductElement() |
not supported |
.isAnyCurrentState() |
.isEventEndStateAny() |
.isAnyPreviousState() |
.isEventStartStateAny() |
.isAnyWorkItemType() |
not supported |
.isCurrentStateGroup() |
.isEventEndStateGroup() |
.isGenericWorkItemType() |
not supported |
.isPreviousStateGroup() |
.isEventStartStateGroup() |
.isSaveWorkflow() |
not supported |
.isTransitionWorkflow() |
not supported |
Now, you can access the assigned users from a stages element:
You can now get the operation data for each supported RTC operations via the operations API:
The new Version of the Stages RTC Plugin can now be triggered, when a ChangeSet is beeing delivered a Stream.
A new API for RTC Scm is part of the new Version:
Including:
Fixed a bug, which was caused by IDs, stored in work item attributes in old RTC Plugin version. The fix converts the old data into the new format.
API Function for ChangeSet trigger, recieving WorkItems is now working properly.
The Stages RTC Plugin now allows to delete Links, Supports Java 8 and includes a new test framework.
Deprecated API Version 0 is removed!
Changed stages attributes to be not internal.
Generated review work items now have no more a parent/child relation to the generating work item.
The Stages RTC Plugin now creates its own log file at logs/stages-rtc-plugin.log.
Rescheduling could theoretically cause loss off link creation. This is caused by RTC Database Exception and only happens on Bulk import >500 WorkItems with complex linking structure. There is no practical problem know. Will be solved with synchronous link creation.
Stages Workflow Configuration in Eclipse Client is empty. There is no need for configuration via Eclipse.
Add ChangeSet Trigger is per WorkItem, Remove ChangeSet is per Change Set. Handled by API.
Not all link Types trigger WorkItem Save Operation. Must be solved by IBM. See: https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=228421
Added API functions for working with ChangeSet-Links
A ClassCastException occurred if an attachment was added to a workItem.
Adding the stages plugin to an operation via eclipse client no longer adds the xmlns attribute to the follow-up/precondition entries in the Project Area Configuration XML.
Database Errors will be rescheduled asynchronous to avoid losing functionality while bulk import.
The Stages RTC Plugin receives events when ChangSets are
It enables script handling for ChangSets. The ChangeSets are modelled as Save Workflows in Stages.
XML Namespace: Updated namespace definition in export xml.
The Stages RTC Plugin interprets process exports from stages and enables RTC to enhance the functionality of ProjectAreas.
The Stages RTC Plugin receives events when a WorkItem is saved. The state of the WorkItem could be a specific state, a state group or any state.
The Stages RTC Plugin receives events when a WorkItem is transfered from one state into another. The transfer states could be a specific state, a state group or any state.
The Java Script API allows access to advanced RTC functionality. For a complete description of the functionality see the JavaDoc.
The Approvals API provides functionality
The Attachments-API provides functionality to read Attachments from WorkItems.
The Attributes-API provides functionality
The Categories-API provides functionality
The Enumerations-API provides functionality to receive Enumerations.
The Mail-API enables sending mails through the rtc standard mail system.
The Operations-API provides access to
The ProjectAreas-API provides functionality
The References-API provides functionality
The Search-API provides functionality to set up a individual RTC query based on the WorkItem Attributes.
The StagesUtils-API provides functionality
The StagesWorkflow-API provides functionality
The Systems-API provides a Logger for the RTC Log.
The TeamAreas-API provides access to Team Areas.
The Timelines-API provides functionality
The Workflows-API provides functionality
The WorkItems-API provides functionality