Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |
| 261:collectionmigration [2026/04/08 19:12] – Meier, Erich | 261:collectionmigration [2026/04/08 19:58] (current) – Meier, Erich |
|---|
| If you have used "common elements" workspaces, those workspaces need to be added to all workspace collections that should have interfaces to them. | If you have used "common elements" workspaces, those workspaces need to be added to all workspace collections that should have interfaces to them. |
| |
| Please note that updating process modules and copying elements in workspaces that are __not__ part of any workspace collection, will __not__ result any process interfaces anymore. | Please note that updating process modules in and copying elements into workspaces that are __not__ part of any workspace collection, will __not__ result in any process interfaces anymore. |
| |
| **//Modelling tip://** after the upgrade to 26.1, use the "[[261:remoteassociations|Process Interfaces]]" menu to find out about current process interfaces of a particular workspace and add workspace collections accordingly. | **//Modelling tip://** after the upgrade to 26.1, use the "[[261:remoteassociations|Process Interfaces]]" menu to find out about current process interfaces of a particular workspace and add workspace collections accordingly. |
| | |
| | As a result, process interface creation should now be much more transparent and easier to control. |
| |
| |