Difficulty: novice
Content
Learning Objectives
After reading this article you will be able to:
Recognize baseline functionalities
Inherit from parent baseline
The basic principle of Workplace is that all baseline configuration comes from a parent (baseline) layer.
Because of this setup structure, a client can use all the configuration that is available in the baseline. So without having to customize anything on client level a Workplace environment could be setup.
Where do we find inheritance
Before reading: The upcoming topics are informative (for now). For your first implementation you will probably only use baseline functionalities.
Below we’ll show you how to distinguish between baseline and client specific configuration, but also how to recognize from which baseline for example an certain a page is inherited.
Inheritance is used throughout the whole Workplace environment. In this article we outline on what levels we use inheritance and how to recognize these. This should help explain why some fields/pages are editable while others aren’t. Examples of configuration item that are inherited are:
menu structures
categories
workflows
pages
functions
fields
access rights
user groups
profiles
So a baseline enables you to faster and more efficient easy set up an environment. After the initial setup, client specific alterations can be added later. Below some examples are given of inherited configuration items.
Categories
Inherited (often called ‘standard’) categories are shown in grey. When a client specific category is added, this will show up in a different color.
Baseline categories have predefined pages, fields and often a workflow.
Pages
By default a lot of (baseline) pages are available. Each page can inherit fields from the page above. When there are multiple pages with the same name, the lowest page in the hierarchy is used in the environment. Whenever a client specific field is added, this will show up on the list with the client layer.
Fields
There are default object fields for each object. These are inherited from the root layer.
Some objects in Workplace have categories. For objects with categories, custom object fields can be created. The fields that are added on a baseline have a prefix that refers to this specific baseline. By looking at the prefix we can distinguish what baseline these fields originate from. If there is no prefix, you’re looking at a root-field.
How can you lookup what (custom) fields an object has?
To find object fields we can navigate to the menu option: Configuration > Objects > find the object you want to see the fields from > press the “fields” tab
For custom object fields we can also go to the menu option: Configuration > Objects> click the categories icon (the map at the top right corner) > press on a category folder
Each page has it’s own page fields. When these page fields are inherited from a baseline page they cannot be edited in the page definition. In this case all fields will be grayed out.
Workflows
The Workflow for requests for example, is also inherited from a baseline. These baseline workflow(s) (processes) are not editable. This can easily be recognized because the fields are grayed out.
Scripts
Via Axxerion scripting, custom logic is added to the baseline of your Workplace environment. Scripts are also inherited from higher baseline(s).
By looking at the script reference you can see what layer this script is inherited from:
FMB- the Facility Management baseline;
GOB - the Go Baseline.
To be clear: baseline configuration can never be changed unless using an overwrite (in which case the functionality it is no longer considered baseline). We’ll tell you more on overwrites in the articles to come. This is not relevant for now.
Summary
Search