Catalog component
In the Catalogs tool, the lock level is applied at a high-level business object with fine-grain locks on the subordinate object.locks are applied to the subordinate objects of an object when there are dependencies with other objects. Applying locks to some, but not all, subordinate objects allows different users to manage different aspects of the catalog. For example, Product and Category managers responsible for product information can have high-level locks on catalog groups and catalog entries. Keeping locks off catalog group and catalog entry subordinate objects allows a Merchandising Manager to manage their content areas in the sales catalog.
Object and subordinate object locking and sub-locking also applies to extended site store overrides. Data can be overridden and changed by users of the extended site store independent of the users that manage the asset store.
Note: We can copy a locked object or subordinate object.
Catalog object
When updating information that pertains 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:
- CatalogIdentifier: The identifier or name of the catalog.
- CatalogAttributes: The attributes of the catalog.
- CatalogDescription: The description of the catalog.
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 subordinate object 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 entry becomes read-only to other users in other workspaces, task groups, or tasks based on the locking policy.
CatalogGroup object
When updating information that pertains 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:
- CatalogGroupIdentifier: The identifier or name of the category.
- CatalogGroupAttributes: The attributes of the category.
- CatalogGroupDescription: The description of the category.
- CatalogGroupAttachment: The images and file attachments of the category.
A subordinate object level lock is acquired on the following properties:
- ParentCatalogGroupIdentifier: The parent identifier of the category.
- CatalogGroupNavigationalRelationship: The parent-child category relationship.
- CatalogGroupAssociation: The merchandising associations of the category.
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 subordinate object locks defined for navigational relationships within the catalog group and the merchandising association. Thus, when you update catalog group properties 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 subordinate object such as the merchandising association.
Updates to a subordinate object acquire individual locks specific to the change, but would not lock other subordinate object 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 that pertains to catalog entry objects (products, SKUs, bundles, and kits) in a workspace, be aware of the scope of object locks. A CatalogEntry object high-level lock is acquired on the following properties:
- CatalogEntryIdentifier: The identifier or name of the catalog entry.
- CatalogEntryAttributes: The defining or descriptive attributes of the catalog entry.
- CatalogEntryDescription: The description of the catalog entry.
- ParentCatalogEntryIdentifier: The parent identifier of the catalog entry.
- CatalogEntryAttachment: The images and file attachments of the catalog entry.
- List Price: The list price of the catalog entry.
- Kit Component
A subordinate object level lock is acquired on the following properties:
- ParentCatalogGroupIdentifier: The identifier of the parent category.
- CatalogEntryNavigationalRelationship: The parent-child relationship between categories and catalog entries.
- CatalogEntryAssociation: The merchandising association between catalog entries.
- Offer Price: The offer price of the catalog entry.
- Fulfillment Properties
- Description/Override: This noun part is used to override the shared catalog entry description for an extended site store.
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 subordinate object locks defined for navigational relationships, merchandising association, description overrides, 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 catalog entry becomes read-only to other users in other workspaces, task groups, or tasks based on the locking policy.
Related concepts
Workspaces locking policies
Workspaces object locking
Related tasks
Changing workspaces locking policy
Related reference
Considerations when selecting a locking policy