System Settings
You need to restart Orchestra after changing these settings.
Orchestra Synchronization Settings
The following settings are available in this section:
• Username - default is calendar.
• Password
• Disable Orchestra service synchronization - this setting will prevent Service name and duration to be updated from Orchestra when the server is restarted or the Fetch button is clicked in the Services tab. If the Service does not exist in the Calendar, it will be synchronised from Orchestra. By default, Service synchronization is enabled.
• Unique customer identifier field - from the drop-down list, select one of the following: Card Number; Custom field 1-5.
Online Booking settings
The following settings are available in this section:
• Reservation Expiry Time - the default value is 600 seconds.
• Unique customer identifier field - from the drop-down list select one of the following: Public ID; Email Address; Phone Number; Identification Number; External ID.
• Pre-populate appointment data on startup - If set to true, the Calendar backend will, on start-up, attempt to load cacheable data for Appointments and Blocking Appointments. The data loaded will be defined by which Appointment profiles and which Services are available on each Branch. This pre-fetch is done to prevent the potentially long initial load times the first time e.g. “get available dates for Branch and Service” is called. Default: false.
• Enable custom slot length - If this check box is checked, the custom slot length feature is enabled, which means that there is a possibility to supply a pre-calculated slot time, instead of letting Orchestra calculate the time. If this check box is checked, the two fields below are enabled. Default: false.
• Minimum slot length in minutes - Default: 1 minute.
• Maximum slot length in minutes - Default: 480 minutes.
• Calculate slots after capacity blocks - If checked, calculation of available time slots is done after capacity blocks, i.e. if there is a capacity block partly or wholly blocking a time slot interval, the next available time will be calculated at the end of the capacity block instead of at the start of the next time slot interval. For example, if there exists a schedule with opening hours from 08:00-15:00 and with a capacity block from 12:00-13:00, and slot interval and service duration is 2 hours, the available times will be 08:00, 10:00 and 13:00. If the setting is disabled, on the other hand, the available times will be 08:00 and 10:00 since the time slot interval from 12:00-14:00 is blocked by the capacity block. Default: false.
High Availability settings
The appointment cache, blocking appointment cache and resource cache of subsystem Calendar Backend can be configured to be periodically refreshed on the High Availability node that is in the cold (passive) state. This is to prepare that node to be ready to take over as hot (active) node.
Both nodes are cold from start-up of Orchestra. The node that is used for Calendar bookings will become hot.
The following settings are found here:
• Pre-populate appointment periodically - Enable periodic cache refresh. Default disabled.
• Periodical appointment data pre-population interval - Change the interval for periodical appointment data pre-population. Default 60 minutes.
Appointment removal settings
Here, you can configure the following:
• Delete appointments older than number of days - here you enter the number of days after which the Appointments should be deleted from the qp_calendar database. The default value is 90 days.
Appointment locks settings
Here, you can configure the following:
• Maximum number of locks for each user - here you enter a number between 1 and 10 for how many locks the same person may have, in parallel. Default is 1.
• Number of minutes before a lock times out - enter the wanted number of minutes before the lock is automatically timed out (the Appointment is no longer locked. Default is 10. (Minimum 1, maximum 120).
This feature is currently only available via the Calendar backend.
Audit settings
Here, you can configure the following:
• Audit blocking appointments - when this check box is checked, it will be logged in the Calendar audit functionality, when so called Blocking Appointments are created or edited. Blocking Appointments are used to block the possibility to book an Appointment for a certain Resource, during a certain point in time. By default this is logged.
Browser settings
Here, you can configure the following:
• Use the HttpOnly cookie flag - Cookies with HTTP only flag set to true indicates that the cookie shall only be accessed from server side and not application running in the browser.
Orchestra needs to be restarted after this setting has been enabled.
• Use the Secure cookie flag - A secure flag set to true on a cookie indicates that the cookie must be sent over a secure communication, such as HTTPS.
Orchestra needs to be restarted after this setting has been enabled.
When done, click Save changes.