Skip to main content

System

Operational features and system core definitions can be set in the System pages: integrations, translations, licences, logs, and settings.

Integrations​

Bloom Enterprise has integration tools to allow you to connect it with external applications. Each integration tool has a different configuration and requires information from the external application side.

By default, all integrations are unregistered. After setting up an integration accurately, the integration status will change to registered.

To open the Integrations page, go to System > Integrations.

Email​

This integration must be active to allow reports, notifications, and messages to be sent by email.

To successfully configure this integration, you only need a valid email address, and then:

  1. Click on the ‘Edit’ button of the Email integration.
  2. Type the email server information in the ‘SMTP hostname’, ‘Port’, and ‘Email’ fields.
  3. Type the sender’s name in the respective field – this is the name that will be displayed as the email sender.
  4. In case your email server requires authentication, enable the ‘Use authentication’ option and fill the credentials (‘Username’ and ‘Password’).
  5. Enable the ‘Use STARTTLS’ option if the used protocol uses the STARTTLS command to send emails.
  6. Click on the ‘Register’ button.
  7. The integration status will change to ‘Registered’.

SMS​

This integration must be active to allow notifications, and messages to be sent by SMS.

To set the SMS integration, first, you need to set up the SMS provider:

  • MessageBird;
  • Kannel;
  • Vodafone SMS Broadcast;
  • Sinch;
warning

If you choose Kannel, you will need to install an external software and configure it (refer to the Kannel documentation for more information);

warning

in case you opt for the Vodafone SMS Broadcast, you will require a contract with Vodafone entity;

warning

if you choose MessageBird or Sinch you need to create an account (with prepaid SMS) and set your account to work with Bloom system.

For the MessageBird provider
  1. Login in your MessageBird account and go to Developers > API access (REST API).
  2. Click on the ‘Add access key’ button – a pop-up will open.
  3. Type the API name and select the ‘Live’ option – a new item will appear in the list.
  4. Click on the ‘Show key’ button and copy it - you will need it to configure the SMS integration.
For the Sinch provider
  1. Login to your Sinch account.
  2. In the ‘API Token’ field, click on the ‘Show Token’ button and copy it - you will need it to configure the SMS integration.
  3. Copy the ‘Username’ field as well - you will need it to configure the SMS integration.

Once you have finished setting up your provider

  1. Select the SMS provider.
  2. Type the sender’s name in the respective field - this is the name that will be displayed as the SMS sender.
  3. Select the country code you will use.
  4. Then:
    • If you are setting a MessageBird provider, type the access key you created at the MessageBird side, in the ‘Access key’ field;
    • If you are setting a Kannel provider, type the required information in the ‘Host’, ‘Port’, ‘Username’, ‘Password’, and ‘SMS Center’ fields – this information is available at the Kannel side;
    • If you are setting a Vodafone SMS Broadcast provider, type the required information in the ‘Vodafone WSDL URL’, ‘API authentication MSISDN’, and ‘API authentication password’ fields – this information is available at the Vodafone side;
    • If you are setting a Sinch provider, type the required information in the ‘API token’, and ‘Username’ fields.
  5. Click on the ‘Register’ button.
  6. The integration status will change to ‘Registered’.

Active Directory / LDAP​

The Active Directory service is used to validate users in Bloom software. To set the Active Directory integration, first you need to set up the Active Directory service and get the server information to register in the integration. Then:

  1. Click on the ‘Edit’ button of the Active Directory integration.
  2. Enable the ‘Enable Active Directory authentication’ option if you wish to validate the system user’s credentials through the Active Directory service.
  3. Check the ‘Allow local authentication’ option if you wish to allow the users to log in locally if the Active Directory authentication fails.
  4. Choose how the authentication will work: ‘Independent servers’ (the users choose the server where they want to authenticate, in the login page), or ‘Sequential servers’ (the server selection option does not appear at the login page and the authentication process will iterate through each server to validate the credentials).
  5. Click on the ‘Add server’ button – a new item will be listed in the ‘Servers’ tab.
  6. Fill the information accurately regarding the Active Directory server – use the tips for a better understanding of the required fields.
  7. Open the ‘Roles mapping’ tab.
  8. Click on the ‘Add mapping’ button – a new item will be listed.
  9. Type the memberOf attribute in the respective field. Select the Bloom role you wish to map to this attribute, in the ‘Select role to map to attribute’ dropdown.
  10. Repeat the last two steps for all roles you wish to map.
  11. Click on the ‘Save’ button.
  12. The integration status will change to ‘Registered’.
tip

If you wish to delete a server or a mapping, go to the respective tab and click on the ‘Delete’ button. You can also edit previously created servers (by clicking on the ‘Expand’ button) and mappings.

Report export​

This integration allows to configure a daily export to a FTP/SFTP or SSH directory with a report of the tickets of previous day in CSV format.

  1. Click on the ‘Edit’ button of the Report Export integration.
  2. Choose the ‘Export type’.
  3. Set the ‘Host’, ‘Port’, ‘User’, ‘Password’, and ‘Destination path’ fields.
  4. Set at which time of the day the report will be exported.
  5. Click on the ‘Register’ button.
  6. The integration status will change to ‘Registered’.

ReCAPTCHA v3​

When you decide to use the E-Ticket feature, you have to first create an account at the Google reCAPTCHA website.

Once you are inside the reCAPTCHA configuration, fill in all the fields:

  1. Label – choose any name to your reCAPTCHA.
  2. reCAPTCHA type – choose the v3 option.
  3. Domains – use your Bloom Enterprise URL (localhost) without the ‘https://’ prefix.
  4. Accept the reCAPTCHA terms and click on ‘Send’.
  5. After that, a new page will open with the keys to use inside the reCAPTCHA integration page at the system’s backoffice.
  6. Copy both keys and past them at the respective fields inside the integration. The ‘Secure host’ must be the same domain that was registered at the Google reCAPTCHA registration website.

Only after the reCAPTCHA registration, the E-Ticket option can be activated.

Translations​

Within this page it is possible to translate into several languages the contents available on the devices seen by the visitors. By adding frontoffice languages, you will be able to translate the part of the system used by the visitors to any language, even if it is not available in the system’s backoffice languages.

In this section it is possible to translate common resources (like locations, services, and schedules), and appointments scheduling flows.

To open the Translations page, go to System > Translations.

Managing Translations​

Adding a language​

  1. Click on the ‘Add language’ button – a new page will open.
  2. Select the language you wish to add in the ‘Language’ dropdown.
  3. Type the language name in the ‘Display name’ field.
  4. In case the language you selected has more than one flag, choose one of the available flags.
  5. Save changes.

Translating the contents​

Once you create the languages, you need to translate the contents manually:

  1. Click on the ‘Edit’ button of the language you wish to translate.
  2. Click on the ‘Edit’ button of the contents type you wish to translate – the respective contents page will open.
  3. For each content on the left, type the respective translation on the right.
  4. Save changes
  5. Repeat steps 2, 3 and 4 for all pages.

Editing a language​

To change a previously created language, click on the respective ‘Edit’ button and update its configurations. Save changes.

Deleting a user​

You can delete a single language by clicking on its ‘Delete’ button or delete several ones by using the ‘Bulk delete’ action. If the languages you wish to delete are already assigned to locations and devices, they will be removed and all translated contents will be lost. This action is irreversible.

Advanced features​

Percentage of translated contents per language​

To help you identify the languages that require further translations, the system displays the percentage of translated contents, per language, in the languages list.

Contents identification in the contents translation page​

A label is displayed next to each content requiring translation to identify its type.

Licences​

Each Bloom Enterprise server has a unique licensing file that sets the creation limit of each resource.

It is composed by the installation ID, that is unique and does not change, and a licence ID, that is updated every time the licence file suffers changes.

The licensing file will, then, determine the:

  • maximum number of locations you can create – to all those locations the queueing module is automatically activated since it is a mandatory module;
  • maximum number of locations in which you can enable the appointments module;
  • maximum number of locations in which you can enable the e-ticket feature;
  • maximum number of Extender devices you can add;
  • maximum number of Concierge devices you can add;
  • maximum number of Tablet Kiosk devices you can add.
tip

Extender, Concierge, Tablet Kiosk - Does not depend on the number of locations. You can have a licence that allows the creation of up to 10 devices and add 3 devices to one location and 7 to another location, for example.

Important

The name of the file can be changed, as long as its extension (.bloom) is not changed.

Whenever you purchase an expansion to the limitations of the current licence, Q-Better will require the licence that is on the system to generate the updated licence. Therefore, you will need to download the licence file from the backoffice and, after you receive the updated file from Q-Better, you need to submit it again.

To open the Licences page, go to System > Licences.

licence file download​

To download the licence file:

  1. Click on the button ‘Download licence file’.
  2. Save the file and send it to Q-Better team.

licence file upload​

To upload the licence file:

  1. Click on the button ‘+ Select the file’.
  2. Select the licence file Q-Better sent you.
  3. Click on the button ‘Upload’.
  4. Check if the licence file was correctly applied by validating the licence ID (provided by Q-Better when the file is sent) and maximum limit of each resource.

Logs​

Logs are records of every event and user action in the system. This page is divided into two tabs: Actions (backoffice actions made by the users), and Events (occurrences of system errors, warnings, and information).

After setting all the desired filter, generate the logs report by clicking on the ‘Apply Filters’ button. All information available in the Logs pages can be download to a CSV file, by clicking on the ‘Download logs’ button.

To open the Logs page, go to System > Logs.

Actions​

Includes detailed information about the users' activity in the system within a specific period. Some examples of this activity include the users' login in the system, changes made in the system resources, assets, generated reports, among others. Each log item includes the date and time and the user that acted at that time.

Events​

Includes detailed information about the system behaviour, within a specific period, categorized with a level of severity:

  • Debug – information only relevant when debugging the system;
  • Info – non-critical events that contain information relevant for the user;
  • Notice – events that may require special attention;
  • Warning – events with the potential to become system errors;
  • Error – errors in the system that may become critical;
  • Critical – critical situations detected that may affect the system usage;
  • Alert – an event that must be handled immediately to avoid system failure;
  • Emergency – urgent situation.
Example

Some examples of this activity include the system boot, SMS and email sending events, among others. Each logs item includes the date and time and the severity level of the event.

Settings​

The Settings page contains general system configurations.

To open the Settings page, go to System > Settings.

System language​

Select the system’s backoffice language in the ‘System language’ dropdown. Save changes.

Average Waiting Time Calculation (AWT)​

Specify the number of hours that will be accounted for the average waiting time calculation (between 1 and 24 hours). For instance, if you choose 6 hours, the system will calculate the average waiting time in the last 6 hours and plot this information when using the KPI metric, this option enhances the data comparison.

Devices’ Default Settings​

For each device type, select the device whose settings will be used as default when new devices of the same type are added to the system.