Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

Difficulty: novice

Content

Learning Objectives

After reading this article you will be able to:

  • Know what categories are used for

  • Understand the effect of categories on Workflows and Pages


Have you already read Categories and fields ?

Why do categories exist?

Almost all objects in Workplace have categories. But why do categories exist?

The category in which an instance (for example an asset) is created determines a variety of things, such as:

  • page layout (fields, order, etc.) of the instance page;

  • applicable template;

  • access to the object;

In this article only the page layout are discussed. For the purpose of learning the basics this is sufficient. In later articles categories are discussed in further detail.

The category determines the page layout

The same goes for instance pages:

Depending on the category of the object we can show/hide category specific fields. For example, fields like License plate/Mileage we only use for assets in the category: car. We can make sure these are only visible on the car instance page, but not on any other pages, so that end users only see fields/functions important to those objects. The page can also be changed on the category page.

Summary

Exercise

  • N/A

Search

  • No labels