User Help > Grouping Units of Work in Change Packages > Integrating With Implementer
Integrating With Implementer
Implementer provides host-based version control and configuration for software management. It also provides promotion and deployment for the movement of software changes to QA and production. For user information on Implementer, see the Implementer 10.2 User Guide. For administrative information on Implementer, see the Windchill RV&S Installation and Upgrading Guide.
An Implementer change package reflects the iSeries development done to resolve the item. Integrating Windchill RV&S with Implementer allows you to:
track each member, how it was changed, and where it is currently in the development process
group changes by the associated production environment
view Implementer information from the Windchill RV&S Web interface
The following outlines some of the main considerations when using Windchill RV&Sitems and Implementer change packages. Each change package reflects the members created or changed for a single production environment.
Multiple change packages are created for a single item when multiple production environments are affected, for example, when making a software fix to an older version as well as to the new release. If an item needs to be fixed in more than one application, a new change package is created for each application keeping each fix separate.
Development progress in Implementer optionally updates the state of an item to reflect the development progress within Implementer. For example, when a member is checked out for an item, the item state could be automatically set to Coding. When all changes for an item are promoted to quality assurance, the state could be automatically set to Testing.
Implementer development activities are controlled by an item’s workflow.
Example of Implementer Integration
The following example explains how the integration between Implementer and Windchill RV&S works:
1. An item is created in Windchill RV&S. For example, the item requests a bug fix for a software installation problem.
2. An Implementer change package is created automatically by performing a check out within Implementer. Likewise, a change package is automatically created from the Workbench by assigning an item to a lock in the Lock Detail panel or by assigning an additional item in the Multiple Items panel. The change package is assigned an ID and is in an open state.
3. Once the changes or additions necessary to satisfy the item are complete, the user promotes the members.
4. The item is moved to the state in the workflow defined for the environment. For example, the item is moved from state Test state to state QA1.