...
Name (Required): Serves as the product name displayed in the shop.
Price (Optional): Can remain empty. Only float and integer attributes are available for price selection.
...
Category Image
The category image is displayed on the landing page when the shop catalog opens. You can choose an avatar from one of the product avatars used within the category. If all products in the selected category lack an avatar image, a default stylized image will be displayed.
...
Category Details
In Category Details, you can customize options specific to each category:
Name and Iconicon: These are fetched from Assets but can be changed if needed for any purpose.
Limit to One Item Selectionone item selection: Restrict the selection to only one item per category if required.
No Price Textprice text: Customize the text displayed for items without a price (e.g., "Free," "No Price," or leave it blank to show nothing). This is relevant when no price is defined for the assets, ensuring users see consistent messaging.
...
In the Product Settings section, you can configure optional settings that enhance how products are displayed and managed within a category. These options help provide a better user experience and ensure accurate information is shown.
In Stockstock: Configures an attribute to automatically update stock status, showing information like "Out of Stock," "Pre-order," or "Only 4 left." Provides users with real-time inventory updates.
Recommended Productsproducts: Displays related products in the product details view and cart, offering suggestions for complementary items and enhancing the shopping experience.
More details about both features on dedicated pages.
| Cp content card macro | ||
|---|---|---|
|
Advanced Settings
Advanced settings provides additional customization options to accommodate advanced use cases and scenarios.
Object schema
...
Included object type* → Select an object type to import as a catalog category.
AQL filter → Optional AQL filter to further narrow down the asset selection. e.g owner = currentUser()
...
and object type: These are used for informational purposes and cannot be edited here. They are defined during the catalog creation process, where assets are synced with the catalog.
Custom field to map to
...
: Map the category
...
to an existing Assets custom field. Multiple object types can be
...
assigned to a category. Objects from this category will be saved in
...
the specified 'Assets' custom field when a customer request is submitted.
...
Name and icon → You can rename the category name and change the icon. Default value is what is defined in Jira Assets.
No price text → Enter custom text for items without a price.
Item limit →
| Note |
|---|
Only Assets custom fields will be displayed in the dropdown. |
Default attributes
Name* → When configuring a catalog in a portal view, the 'Name' attribute is required. It is mandatory to define the 'Name' for each catalog. Without it, you cannot proceed further in the setup process.
Short Description → While the 'Short Description' is optional, it's beneficial for users. It provides a quick insight into the product without delving into the detailed view. When users hover over a product, the short description pops up, offering a glimpse of the product's highlights.
Price → The 'Price' attribute is optional in the catalog. If left undefined, users will see a label marked "No Price" when viewing the product. This ensures clarity for users when browsing products without specified pricing.
...
This is particularly useful for REST API integrations and automation.
Category-level AQL: An AQL filter can be added at the category level, giving admins the option to override the global AQL defined during catalog creation or retain it.
...