...
The operation mode of the external app determines on which server the external app is accessible. The operation modes Production, Backup, Test and Development are available and refer to the server of the Workplace Management environment (axpr, axbk, axts, etc. (Clusters and Servers)). If the operation mode is set to Production, then the external app will not be accessible via the backup or test server for the external system, for example.
| Note |
|---|
If the operation mode is empty, the external app is accessible on all servers (as soon as the external app is synced to all servers, which is daily for the backup and every 6-8 weeks for the test server), however this should be avoided at all times, as this can lead to issues, like testing on a backup or test server resulting in sending out data to the (production server of the) external system linked to the external app, if the operation mode is not specified. |
1.4 Commission
The commission of the external app determines if the external app is active or not or in which direction the external app is accessible. The commission options are Active, Deactivated, Incoming allowed and Outgoing allowed. By default the external app commission should be active. If an external app is no longer used, then the commission can be set to Deactivated and the external app will no longer be accessible, even with the secret key used by the external system. If for some reason the external app should only go uni-directional, then this can be determined via the commission Incoming allowed or Outgoing allowed, but this will be considered as non-default configuration (deviating from the default/customization).
...
Access to reservable object: Only via custom access set on reservable objects, it is possible to configure that only users from a particular system group are allowed to reserve the object
Blocked dates: Reservable objects are blocked during a specified period. For more info, see: Reservable objects
Regime: Regimes are linked to reservable objects with a limited availability (only reservable between 08:00 AM and 05:00 PM). For more information on regimes, see: Managing regimes
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 (apart from already being reserved or not being reservable at all):
No access to the object
Object is already reserved
Object is not reservable at all
Blocked date apply to the object within the period
Regime with limited availability linked to object
...
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:
Skip access check when searching for reservables
Skip blocked date check when searching for reservables
Skip regime check when searching for reservables
...
| Info |
|---|
By default, these skip checks are enabled! Only disable them if the customer needs a specific check and be aware of enabling this for tenants with large floorplans or reservable objects in general, as these checks will have an impact on the performance when searching for reservable objects and loading floorplans via the Workplace Experience touchpoints. N.B: Skipping these checks only applies to the Workplace Experience touchpoints and not when using Workplace management for creating or managing reservations. |
...
2.1.2.1 Skipping access checking for specific objects
If access to certain reservable resources (e.g. certain meeting rooms) is restricted (via custom access set on those objects) and therefore the general setting 'Skip access check when searching for reservables' is not enabled, it is still possible to only check the access to certain reservable resources, instead of every resource tagged to the external app. Skipping the access check for all other reservable resources (for which it is not relevant) will still result in faster fetching of the relevant data and thus a better user experience in Workplace Experience.
This will make it possible to only have the system check if a user has access to a certain reservable resource (when searching for available resources via the Workplace Experience touchpoints) for specific resources (e.g. only for meeting rooms that are restricted to SMT members)
By default, every reservable object (Area, asset, Catalog item) that is added to the Workplace Experience external app, will have the access check disabled. To enable this check, open the tagged object and enable the check:
...
If the access for specific reservable resources should be checked, make sure to disable the general 'Skip access check when searching for reservables', otherwise all access checks will be skipped.
| Info |
|---|
By default, 'Disable access checking' is enabled for every reservable object tagged to the Workplace Experience external app! N.B: Skipping the access check for specific reservable resources only applies to the Workplace Experience touchpoints and not when using Workplace management for creating or managing reservations. |
2.1.3 Cache configuration
...