Process model corruption caused by the usage of Map node in Modeler 7.0.0.2

Flash (Alert)


Abstract

We have had multiple PMRs on 7.0.0.2 regarding process model corruption caused by the usage of Map node. The issue was fixed and released with V7.0.0.2 Interim Fix 1. Please move to V7.0.0.2 Interim Fix 1 as soon as possible if you need to use maps in your models.


Not moving to this Version would result in loosing the work done during modeling and it is not always possible to recover the models.

Content

In order to use the map nodes in a process model, upgrade to at least WebSphere Business Modeler Version 7.0.0.2 Interim Fix 1.



IBM WebSphere Business Modeler Advanced V7.0.0.2 Interim Fix 1


If you insist on staying on WebSphere Business Modeler 7.0.0.2, then when updating a process that contains map nodes, the map editors should not be opened. If you happen to open the map editors, then you should do the following:


- Close all map editors.
- Close the process editor WITHOUT SAVING.
- Open the process editor. DO NOT OPEN THE MAP EDITORS.
- Continue editing.


When updating a process that contains a map node, you should keep the map editor closed. This will prevent the process model from getting corrupted. Otherwise please upgrade to at least WebSphere Business Modeler Version 7.0.0.2 Interim Fix 1.


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Business Modeler Advanced
Corruption

Software version:

7.0.0.2

Operating system(s):

Windows

Software edition:

Advanced, Basic

Reference #:

1443562

Modified date:

2010-08-12

Translate my page

Machine Translation

Content navigation