The information in this article applies to:
Product: Metastorm BPM (e-Work)
Version: 6.x 7.x
Issue
- A procedure named MyProcedure.xep is published. When changes are made, the procedure is saved as MyProcedure.v2.xep. This procedure fails to publish, and the following message is generated: Error - Map MyProcedure already published as part of procedure MyProcedure.
Resolution
In versions of Metastorm BPM (e-Work) prior to version 7, the file name after the dot was ignored. A map named MyProcedure would publish successfully whether it was part of a procedure with filename MyProcedure.epc, MyProcedure.v2.epc, or MyProcedure.SomeOtherText.epc.
Starting with version 7, these are recognized as different filenames.