There may be scenarios where there is a clash between multiple uses of the same SID, e.g., by different SystemWeaver servers, between a SID used by a user o...

Item types can be removed from the meta model using the swArchitect. This article describes the prerequisites for the operation, and how to do it.  Prer...

As described in Creating an Item Type, all item types that you create will actually be sub-types of another type. This enables the sub-types to inherit prop...

At some point, you may want to change the meta model for an item type that currently, directly owns a part type so that, instead, the part type is owned by ...

Like items, parts are also objects in the database, but it is more useful to think of them as allowed links between items of different types. Parts are &quo...

Part types can be removed from the meta model using the swArchitect. This article describes the prerequisites for the operation, and how to do it.  Prerequ...

If an item type has more than one allowed part type per the meta model, it is possible to define the order of the different part types when displayed in the...

When users view item structures in SystemWeaver, they are viewing items related to other items by way of a part. The items have names and, by default, the n...

One of the more common refactorings done is to change the owner of a part type. A common case is when a new, possibly abstract type is created, and the owne...

The swArchitect client provides a tool for changing the multiplicity of a part type from Single to List and vice versa. Existing data will not be affected. ...