In Systems Engineering, “Rubber Stamping” is usually a bad thing, but when it comes to tool automation, it’s a lifesaver.
If you use DOORS Next Change Sets, you’ve likely run into the constraint requiring an “Approved” Work Item in EWM to deliver. The problem? EWM doesn’t care if the status is “Approved”; it wants a formal record in the Approvals tab. This creates a manual bottleneck for teams doing offline reviews or using integration tools like IBM Integration Hub Planview (Tasktop).
In this video, I demonstrate a custom EWM plugin I built that acts as a “Rubber Stamp” bot. It automatically triggers a formal approval the moment a Work Item hits a specific state.
What we cover:
- The difference between “Status” and “Formal Approval” in EWM.
- Why DOORS Next Change Set deliveries get blocked.
- A walkthrough of the Auto-Approval Plugin (Web UI — there is an Eclipse version as well).
- How this enables seamless automation with IBM Engineering Integration Hub or other automations that interact with the EWM REST API.