Introduction

This feature is only available in version 8 and higher

A catalog is a complex object that can be used to group roles and other other entities in accordance to your needs. In addition it allows you to define who can assign and or receive the entities added to the catalog. As an example we assume we have one root tenant with two companies in our organizational tree structure. We have ITSENSE where employees work, and we have Best Run Inc., who we treat as suppliers in our example:

We then create a catalog called “Best Run”. Into that catalog we add all the tools that Best Run Inc. uses. In our case those tools are represented as the CRM, Time Tracking and HCM roles. But we do not want all Core Identities in the system to be able to use those roles. All suppliers, in this case anyone employed at Best Run Inc., should be able to assign and receive those tools. But ITSENSE employees should only be able to assign those tools to anyone who is eligable to receive it, but they are not able to receive the tools themself. To achieve this we create two additional roles. The first one we call Supplier and we add the Best Run catalog to that role with both the Assign and the Receive right and map it in the organizational tree to Best Run. Inc. The second role we call Employees. Here we only add the Assign right, to achieve our use case.

Properties

Whenever you are creating of updating a catalog, you have to specify the following properties:

Property	Data Type	Mandatory	Example	Description

Property	Data Type	Example	Description
`Name`	String	Best Run	The technical name of the catalog
`Shop name`	String	Best Run Tools	The name used in the shop
`Description`	String	Contains all Best Run related tools	The technical description
`Shop description`	String	Contains all Best Run related tools	The description used in the shop
`Status`	DropDown	Active	You can choose between different states, like `In preperation` or `Active`. Only the ones in state `Active` will be shown in the shop and other places.
`Owner`	Core Identity	Peter Griffin	The owner of the catalog

Roles

Defines the entities that are contained in the catalog. In or example this would the the roles CRM, Time Tracking and HCM. For each item that you add, you can also specifiy the Is Orderable property. This property will indicate whether or not the entity will be shown in the shop or not.

Catalog to role assignment

Shows all the roles where the catalog has been assigned to, including the selected permission. So if we want to give everyone the permission to assign entities from the catalog to other people, we have to add the catalog to a role that everyone is member of. If we want to give people the permission to receive entities from the catalog, we need to add the appropriate roles with the receive permission.