Key concepts

To use IBM® Product Master, you need to understand the application key concepts.

For more information on some key concepts, click the links at the end.

Access Control Group (ACGs): Access Control Groups provide a way to control access to the users. An ACG allows or restricts access to different parts of the systems like view catalogs, view items in the catalogs, edit items, delete items, and so on. ACGs are assigned to Roles, which in-turn provide access to users that have these roles.
Attribute value: An attribute value is the data that is captured against an attribute on an item or category.
Attributes (or attribute names): An attribute is the definition of a field, allowing data to be collected on an item or category. An attribute has a type, the validations, and other metadata used in the capture of data.
Categories: Categories are used both for browsing and organizing products. A category must be created within a hierarchy. When a hierarchy is applied to a catalog, each item in the catalog can be associated to one or more of the categories within that hierarchy. Every hierarchy must have exactly one root category. Every category can have zero or more categories within it, known as subcategories.
Collaboration Areas: Collaboration areas are runtime manifestation of the workflows. You can define collaboration areas for a hierarchy or a catalog, based on the workflow definition. When defined, items from a catalog or categories from a hierarchy can be checked-out under the workflows for reviews and approvals by various people in the organization.
Company: A Company is the topmost container in the IBM Product Master. All the Product Information Management (PIM) operations are done under a company. You can create multiple companies in an application.
Custom Tools: Enables the users to add their own custom screens. These custom screens can be invoked using the system menus.
Data model: A representation of business and data requirements, designed by using various and flexible business objects such as Catalogs, Items, or Lookup Tables.
Document Store (docstore): A store of documents that are required by the system. Any custom scripts, Java code, or data files can be kept here, and system can access docstore to get these documents.
Dynamic Selections: Dynamic selections also select a set of items, but the selection criteria is driven by a WebSphere Query Language (WQL). The result set can vary based on the criteria that are provided in the query.
Entry Preview: A type of extension point that allows you to create a sample view of a current item set that can then be run from the data entry screens. For example, you can write a script to view how an item displays when you use an XML format.
Environment import-export: Environment import-export is backup and restore functionality in the IBM Product Master that helps in cloning of a running system. For example, a test system can be exported to a production box and all entities are cloned on the production system.
Extension Points: If users want to extend any out-of-the-box functionality, they can provide their own functionality using the extension points. These extension points can be written by using the Java APIs or scripting language and can be hooked to the system so that those are run at certain invocation points in the system.
Items: Items represent products and services, for example, stock-keeping units (SKUs), global trade item numbers (GTINs), market offers, or any other objects as defined by the business. You can perform edits by using the stand-alone or advanced content authoring screens. From either screen, items can be added or edited.
Location attributes: Allow the IBM Product Master to maintain item and location-specific information.
Java APIs: Java-based APIs can be run from any extension points. Java APIs expose the complete system functionality.
Post Processing: This is an extension point that is run when items or categories are being saved. Post processing extension point is invoked before saving of the item but after processing operation is completed.
Post Save: This is an extension point that is run after items or categories are saved.
Pre-Processing: This is an extension point that is run when items or categories are being saved. Preprocessing extension point is invoked before saving of the item and before any processing for save starts.
Reports job: Reports are asynchronous jobs that can be used for doing various operations as jobs.
Role: A Role entity represents the role that is being played by different set of users. For example, a role can be Admin role, Approver role, or Reviewer role. Multiple users can have the same role.
Selections: Selections are used to select a subset of items. You can either predefine these or select the items at run time. Items that are selected from a selection can be used for various purposes like running exports, reports or simply display on the screens.
Static Selections: Static selections are a type of selection that has the predefined criteria for selection of items. For example, all items under set of categories are selected.
Sub Spec: Sub Spec is a portion of the spec that can be contained within a main Spec and can be reused by several other Specs.
Views: A set of attribute collections, by using which user can control what they want to see on screen. Users can select the view that they want to work with so that they see limited information on the screens.
Workflow: Workflows define the business flow. Steps are defined to perform certain business logic and these steps are connected to establish the flow. Workflows define the metadata for the Collaboration areas and runtime behavior of these collaboration areas are controlled by the definition of workflows.
WebSphere Query Language (WQL): IBM Product Master provides its own SQL like query language that is called WQL, using which users can directly access all the internal entities or objects.