Reversing a Change Set in IBM Engineering Workflow Management: A Structured Methodology
Overview and Context
In the domain of software configuration management, the ability to reverse changes cleanly and efficiently is not just a convenience—it is a necessity. During a recent engagement with a customer utilising IBM Engineering Workflow Management (EWM), our team encountered a scenario that required rolling back a change without disrupting the broader development stream. The experience reinforced how a structured workflow and disciplined change management can transform a potentially complex recovery into a streamlined process.
Customer Scenario: Managing an Unintended Change in a Live Environment
During an active sprint, a developer inadvertently delivered a change set that deleted several critical configuration files. The issue was not detected until after the change had been delivered, raising immediate concerns about how to restore the missing files without affecting other valid changes in the stream.
To ensure proper accountability and visibility, a defect was immediately created and assigned within the critical sprint so the team could prioritise the fix alongside other planned work. Instead of relying on manual fixes or reverting to backups, we leveraged EWM’s built-in functionality for change set reversal—a clean, traceable, and collaborative approach to undo changes effectively.
What Made the Difference: Structured Change Sets
The key factor that enabled a successful recovery was the disciplined way in which the changes had been organised:
- Each logical unit of work was committed as an individual change set.
- Developers adhered to a practice of incremental delivery, ensuring changes were isolated and traceable.
This structure allowed the team to reverse only the specific change set that caused the issue, without interfering with other contributions.
Procedure for Reversing a Change Set in IBM EWM
When change sets are properly separated, the reversal process in EWM is straightword.
The following steps outline the method we followed:
1. Initiate the Reversal : Right-click the change set and select Reverse.
2. Patch Generation : EWM automatically generates a patch that undoes the changes introduced by the original change set.
3. Merge the Patch into the Workspace : Manually merge the patch to the workspace. This step allows for conflict resolution and selective merging if necessary.
4. Automatic Creation of a New Change Set : A new change set is created automatically to hold the reversal changes, maintaining full historical traceability.
Note: As per governance policy and to ensure better traceability, a defect is linked to the critical sprint and associated with the change set before it is delivered to the stream.
5. Deliver the Reversal Change Set : After testing and validation, deliver the new change set to the stream—cleanly rolling back the original change without disruption.
This approach ensured no data was lost, ongoing development remained uninterrupted, and full auditability was preserved.
Why We Recommend This Approach
Here’s why this method stood out as a best practice for us—and why we recommend it:
- Precision: You can undo specific changes without collateral damage.
- Clarity: Each change remains traceable in the audit trail.
- Confidence: Restores deleted or overwritten files without ambiguity.
- Collaboration-friendly: Isolated change sets make it easier for teams to work in parallel and resolve issues quickly.
Best Practice Highlight: Managing Change Sets as Independent, Auditable Units
- This experience reinforced a core principle: treat each change as a discrete, first-class unit of work. Organizing your development process around small, well-defined change sets not only enhances delivery flexibility but also strengthens your ability to recover quickly from errors.
- Whether addressing a regression, rolling back an incomplete feature, or restoring critical components, this structure provides developers with confidence and control.
Final Thoughts
- Working in IBM Engineering Workflow Management offers teams powerful tools—but it’s your process discipline that truly makes them shine. Reversing a change set became a quick, non-disruptive task in our customer engagement, thanks to a mindful approach to change management.
- If you’re managing complex systems or collaborating across teams, adopting this strategy can save time, reduce errors, and improve confidence in every delivery.
© Copyright IBM Corporation 2025