Difficulty: novice
Content
| Table of Contents | ||||
|---|---|---|---|---|
|
Learning Objectives
After reading this article, you’ll 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 a reservation) is created determines a variety of things, such as:
what workflow (version) is used;
page layout (fields, order, etc.)of the instance page;
applicable template;
acces to the object;
In this article only the workflow and 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 workflows that is used
The object Reservation for example has multiple categories, see the screenshot for examples of reservation categories. Different categories can use different workflows because not all reservations follow the same steps.
A workplace reservation, where we only need to reserve a workplace is fairly simple. We select a room, check it’s availability and book it.
Other FMB reservation categories might include reserving catering, or specific assets like beamers, laptops, or speakers. In these reservations we could also assign tasks to users like giving out or taking back the laptop/speaker.
So depending on the Reservation category the process of making a reservation might differ. This is done so that users don’t see fields/functions that are not being used in specific cases. The Workflow used for a category can be found as follows:
Navigate to the Object, this can be done in two ways:
In the Navigation menu, click: Configuration > Objects > search for the object > open the object, or
Clicking for example on the menu option ‘Reservations’ in the NavigationMenu
Click the folder button on the top right corner of your screen to get an overview of all categories beloning to this object.
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
| Rw ui textbox macro |
|---|
|
Exercise
- N/A
Search
| Live Search |
|---|