...
Workplace Experience
Analytics
Calendar integration
Maintenance
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 described for each type.
...
The Workplace Experience external app also consist of several includes, which are used to link all relevant masterdata objects applicable for the Workplace Experience touchpoints. The Buildings, Areas, Assets, Catering items, 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.
...
2.1.2 Skip checks
...
The Workplace Experience external app facilitates several ways in optimizing fetching data. A lot of data being requested very often can influence the performance in the Workplace Experience touchpoints experienced by the end users. There are two configuration options which optimize the fetching of data:
Skip access checks
Cache configuration
In Workplace Management there are several configuration options which are relevant when using the reservations module:
...
If customers do not use blocked dates, specific access to reservable objects or regimes with limited availability, each of these checks can be disabled (skipped) via the settings on the external app. Skipping these checks will result in faster fetching of the relevant data and thus a better user experience.
...
2.1.3 Cache configuration
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 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 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.
...
| Info |
|---|
The cache configuration is disabled by default. The implementation consultant needs to enable the cache configuration during the module activation. |
2.1.
...
4 Check-in options
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 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-in.
...
2.1.
...
5 Workflow interaction
In the external app the workflow interaction determines which categories are used for single and recurring reservations created from the external system. By default the correct categories are automatically used and the workflow interaction on the external app should only be used, if there is a deviation from the default categories.
...
2.1.
...
6 Ticketing
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 team.
...
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.
2.3 Calendar integration
2.4 Maintenance
External app configuration per category/type (skip access check, link objects, check in, etc.)The external app type 'Calendar integration' is used to expose the Workplace Management environment to Exchange or Google Workspace. Room- and reservation data can be exchanged between Workplace Management and the calendar application in order to sync meetings created in one of the two applications.
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.
...
2.3.1 Mappings
The mappings to establish the calendar integration 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.
...
2.3.2 Linking reservable rooms
The Calendar integration external app consist of an include, which is used to link all relevant reservable rooms, which are in scope for the calendar integration. Reservables not linked to the external app, are not in scope for the calendar integration and thus will also not sync reservations/meetings created from Workplace to the external calendar application and visa versa.
...
2.3.3 Observations
Once the reservable objects are linked to the external app, the reservable resources need to be mapped to the corresponding resource from Exchange or Google Workspace. Mapping the resources is described in the configuration guide.
Once a mapping is created between a Workplace Management reservable resource and a resource from Exchange/Google Workspace, an observation is automatically created. The observation is used to
2.3.4 Events
Configuration by module activation
Created by CS or via module activation
Cache configuration
Workflow interaction
Events
4. Configuration of the External App
...