...
Next to the objects, the external app also consists of a trust relation. A trust relation is used to configure the authentication needed to access the Workplace Management environment via the external app. The type of authentication is configured in the trust relation as and is automatically determined by the external app type. A authentication type can be a username/password, two-way SSL certificate, a secret key, etc. Depending on the authentication type, the username/password or key needs to be shared with the external system to be able to access the external app.
...
Additional configuration on the external app depends on the external app type. More on the different types in the next chapter.
2. Types
When a an external app is created, the category determines the external app type. The external app type determines which external system the external app is exposed to. By default the following categories/types are available:
...
Next to the above general external app configuration, each type has addition specific configuration. In the next chapters, the different types and additional configuration is and options are described for each type.
2.1 Workplace Experience
The external app type 'Workplace Experience' is used to expose the Workplace Management environment to Workplace Experience touchpoints such as the Workplace App, Go, Room displays, Kiosks and Floor displays. Workplace Experience can fetch the relevant user data, reservation data and reservable object data. Reservations and/or visitors created via a Workplace Experience touchpoint are created in Workplace Management via the external app.
The Workplace Experience external app is by default created by Customer Support when setting up the new Workplace Management environment for the customer.
2.1.1 Linking objects
The Workplace Experience external app also consist consists of several includes, which are used to link all relevant masterdata master data objects applicable for the Workplace Experience touchpoints. The Buildings, Areas, Assets (Equipment), Catering items (Services), Cost centers and System users can be linked via the corresponding includes and will be exposed to the Workplace Experience touchpoints. Objects not linked to the external app, will not be available/visible in the Workplace Experience touchpoints.
...
If a user opens a floorplan in the Workplace App for example, the application will show the user all available and not available (reservable) objects. Objects being not available can be due to several reasons:
...
The application needs to check each of the above, to determine if a reservable object is available. A lot of reservable objects on a floorplan means the above checks need to be executed for all reservable objects on the floorplan.
...
The cache configuration linked to the external app is also an important additional configuration for Workplace Experience. The applicable cache configuration (version) is automatically added to the external app by default. A cache configuration consists of several filters and reports which can be used by the external system to fetch data. For each filter or report it is determined, if the fetched data needs to be cached or not.
...
Next to cached data, other data can not be cached. Data which can change and always needs to always be up-to-date, cannot be cached. For example, if a user looks at a floorplan from the Workplace App, the user should see up-to-date reservation data to determine which workplaces or meeting rooms are available to reserve.
...
In the external app, it can be specified per category and building if the user needs to check-in the reservation, when it is about to start. Determine whether More information about the check-in is required, check-in can be done via scan, when the option to check-in becomes available before the start of the meeting and until what time after the start of the reservation, the user can check-insettings can be found in the module activation additional settings.
...
2.1.5 Workflow interaction
...
It is possible to create a ticket via the Workplace App. In the external app, the default request category and the default problem type can be specified. Requests created from the Workplace App will automatically get the applicable category and the problem type is automatically assigned resulting in the request ready to be picked up by the relevant service teamMore information about ticketing from the Workplace app can be found via the module activation.
...
2.2 Analytics
By activating the Analytics integration via the module activation, the external app is automatically created and configured correctly. There are no additional configuration options for the external app for Analytics.
...
The calendar integration external app is by default created and configuration to a certain extend via the module activation. Additional (manual) configuration is described below.
...
The mappings to establish the calendar integration between Workplace and Exchange/Google Workspace are created and partly pre-configured via the calendar integration module activation. The client_id and client_secret still needs to be filled in. More information about obtaining the client_id and client secret can be found in the /wiki/spaces/KB/pages/362545217 for the calendar integration.
...
The event log on the calendar integration external app is an overview of all events send and received from the calendar integration. This overview can be used for debugging purposes.
...
TODO:
Configuration by module activation
Created by CS or via module activation
4. Configuration of the External App
...