New KOBI documentation is available: https://adeo-ccdp.gitbook.io/kobi/

This section is used to manage experiences configurations.

Access

Experiences admin

Experiences administration is accessible from the “Administration” tab in the header.
Experiences is the fifth and last tab of the Administration Screen.

Experiences administration is done site by site, check which Site you are working on in the header.

List

Experiences list

On this screen you will see the list of existing experiences.
From there you can create new experiences, access existing ones, edit them, or delete them (providing you’re in the allowed user list or admin).

Creating an experience

Click on + Add an experience to create a new Experience, this will open the Experience creation form.

This form is very similar to the Site creation since an Experience is an override of a Site configuration.

General

Experiences general

This first step requires

  • a label : My team experience or my demo experience for examples
  • a description : what this experience does
The URLs block will be filled once domains are set up.

Domains

Experiences domains

Since an Experience is a custom Site configuration accessible from a different domain, you have to set them up. This screen is very similar to the Site’s domains but you will reuse the site’s tenants and locales.

In order for your experience to be accessible on the configured domain, this domains must exist and point to the Gluer service. You may require the KOBI team to set this up.

Applications

Experiences applications

The main goal of Experiences is to benefit the whole default Site configuration, but being able to override some applications you’re working on. Here again the screen is very similar to the Site’s applications.

By default the override is disabled and you will see all the configured applications for the site. If you enable this config (toggle on the upper-right corner), the right tab will be wiped and you can set up the application you want to override.

Your experience’s applications will be the aggregation of the default Site configuration + the applications you’ve set up in the Experience.

When configuring an application, you can select the version of your choice.

Backend routing rules

Experiences backend rules

Here again this section is the same as the Site’s. It is disabled by defaut, meaning that you are using the Site’s default backend rules. You can off course override this configuration thanks to the upper-right corner toggle.

Since Backends applications are referenced by names, you may override Backend applications without changing the backend routing rules configuration.

Devices and browsers

Experiences devices and browsers

Once again, same screen ad the Site’s, disabled by default, enabling it will overrides the devices and browsers detection.

Security

Experiences security

The last step, here again the form is same as the Site’s, override may be used to tests authentication features, report to the security documentation.

Access the experience

Experiences access

Once created, you should see your Experience URL, you can click on it to access your environment. Everything should be the same as the default Site configuration, except for the configurations you have overrode.

Authorization

Experiences authorizations

Experience configurations features a list of members that have edit rights on this experiences. After creation you should be the only one in this list. This means you are the only one (besides ADMINS) that can edit or delete this experience. Anyone can access it through its URL, but no one else can edit it.

You can use the search input to add members to work with you on this Experience.
The “allow all users” button will clear the member’s list, if the list is empty, anyone can edit/delete.

Usage

Once created your experience will appear in the header, next to the site selection. Make sure to select your experience.