Categories

The categories are containers of products (store items) and are also used for navigation.

It is possible to set Actions on the category level, and all products in the category will inherit the actions (can be overridden).

Categories can also be added as Sub categories to make navigation and grouping of products easier.

Add a category

To add a new category, click the Add category button on the front page or in a category view.

When adding a new category from within an existing container, there is also an option to add a new Root category. Adding a Category within an existing category will create a child category, and a Root category will create a new main category.

picture 0

Add a title, short description and description.

picture 1

The Use Compact View option can be set if the products in the category should be displayed as a list or as tiles.

An example with compact view enabled:

picture 2

The display mode can be set by the user as well, see above.

An example with compact view disabled:

picture 3

Category image

Read more about image uploads, selection and manipulation here.

In the Images tab, you can upload one or more images to the category.

A category can have a Thumbnail image and a Banner image. One image can have both roles.

Use the Thumbnail and Banner selection buttons on the images to define the image roles.

picture 4

The banner image is placed above the product list in the category view:

picture 9

The thumbnail image can be displayed on the slides on the front page of the Catalog:

picture 11

Read more about image uploads, selection and manipulation here.

Category actions

Read more about the action system here.

Actions can be defined on a category level. This allows managers to set actions, like input forms, approver and submit actions that will be inherited by all products that are placed in the category.

Each product will inherit the actions from the category level and can include more product-specific actions.

The category actions can also be ignored by a product.

In the following example, we will see three actions defined on the category level:

  1. Approval step
  2. Email to service desk
  3. Email to the user

picture 5

Then, in the product actions tab, we see that the product inherits the actions from the parent category.

In this example, there are two more actions for the specific product. These actions will be displayed/triggered before the category actions.

Click the Disable inheritance checkbox if the category actions should be ignored.

picture 6

Read more about the action system here.