Administer > Manage WebSphere Commerce features > Workspace Administration Tool > Workspaces object locking


Catalog component

In the Catalogs tool, the lock level is applied at a high-level business object with fine-grain locks on the subobject.

A lock on the object or subobject does not inhibit the copy functionality.


Catalog object

When updating information pertaining to sales catalog or a master catalog in a workspace, be aware of the scope of locking within the catalog object. A Catalog object high-level lock is acquired on the following properties:

The catalog object has properties such as the catalog identifier, attributes, and descriptions. These particular properties determine the identity of what the catalog is and therefore are grouped under a single high-level object lock.

The catalog object has no subobject locks defined. Thus, when you update properties of the catalog such as the name, description, or attribute in the workspace, the entire catalog object is locked. This catalog becomes read-only to other users in other workspaces, task groups, or tasks based on the locking policy.


CatalogGroup object

When updating information pertaining to categories in a workspace, be aware of the scope of locking within the catalog group object. A CatalogGroup object high-level lock is acquired on the following properties:

A subobject level lock is acquired on the following properties:

The catalog group object has properties such as the catalog group name, description, attributes, images, and file attachments. These particular properties determine the identity of what the catalog group is, and therefore are grouped under a single high-level object lock.

The catalog group object has subobject locks defined for navigational relationships within the catalog group and the merchandising association. Thus, when you update properties of the catalog group such as the name, description, attributes, and file attachments in the workspace, the catalog group object is locked. This catalog group becomes read-only to other users in other workspaces, task groups, or tasks based on the locking policy. However, the lock on the catalog group would not prevent users in another workspace task to update a subobject such as the merchandising association.

Updates to a subobject acquires individual locks specific to the change, but would not lock other subobject or the logical object itself. For example, creating a merchandising association between categories or moving categories within a sales catalog are treated as a separate lock.


CatalogEntry object

When updating information pertaining to catalog entries (products, SKUs, bundles, and kits) in a workspace, be aware of the scope of locking within the catalog entry object. A CatalogEntry object high-level lock is acquired on the following properties:

A subobject level lock is acquired on the following properties:

The catalog entry object has properties such as the catalog entries name, description, descriptive and defining attributes, images and list price. These particular properties determine the identity of what the catalog entry is, and therefore are grouped under a single high-level object lock.

The catalog entry object has subobject locks defined for navigational relationships, merchandising association, and offer price. Thus, when you update properties of the catalog entry such as the name, description, attributes, and file attachments in the workspace, the catalog entry object is locked. This category becomes read-only to other users in other workspaces, task groups, or tasks based on the locking policy.


+

Search Tips   |   Advanced Search