9 | Global Settings "Cloud" Tab

This article outlines the Components within the 'Cloud Tab' and the uses within BackOffice operations. This Tab contains all Cloud, Bepoz Online, and myBepoz configurations necessary for Organization-wide implementation: Cloud Venue Database, Bepoz Online, and my Bepoz.

This article outlines the Components within the 'Cloud Tab' and the uses within BackOffice operations.

This Tab contains all Cloud, Bepoz Online, and myBepoz configurations necessary for Organization-wide implementation: Cloud Venue Database, Bepoz Online, and myBepoz.

Prerequisites

To access Global Settings, the applicable Operator Privileges will need to be enabled

Operator Maintenance 'General' Tab

System Setup: "Access Venue, Stores & Tills" Flag
System Setup: "Maintain Global Settings" Flag

Cloud Venue Database

Configuration Option	Description
Use Cloud for Venue Databases	When enabled, this flag sets the System to stop sending Databases directly to Venues and to use a Cloud Server instead The Head Office will send the Database once to the Cloud, and then tell each Venue where to pick it up from If this flag is disabled, Bepoz will work in the traditional manner, without using a Cloud Server The default Bepoz Cloud Servers may be used, or optionally set up a different Cloud Account to be used The Cloud Venue Database option will send a Full Venue Database at the time set in the below fields After the initial send, changes only are sent each hour starting at the first hourly send and ending at the last hourly send When this flag is enabled the Send Venue Database standard Job is disabled
Send Frequency	This is the frequency between the First and Last hour that the partial Database will be created and sent to the Cloud for retrieval Select from the following options: Daily Only Hourly Two Hourly Half Hourly Four Hourly
First Send Hour	Use this field to set the hour that the First partial Database is created and sent to the Cloud each day This uses the military time format, so 9 = 9 AM, 12 = noon, 18 = 6 PM, etc. Every preset time after this, based on the Send Frequency, another partial Database will be created until the Last hour is reached The partial Database will contain all changes made since the Full Venue Database was created - meaning the size will increase during the day but will hold all changes made today
Last Send Hour	Use this field to set the hour that the Last partial Database is created and sent to the Cloud each day This uses the military time format, so 9 = 9 AM, 12 = noon, 18 = 6 PM, etc.
Cloud Acct Name	Use this field to enter a Cloud Account Name to be used other than the default Bepoz Cloud Server Account
Cloud Acct Key	Use this field to enter a Cloud Account Key when using a Cloud Account other than the default Bepoz Cloud Server

MyBepoz

lag	Description	Visual/s (if Applicable)
myBepoz is Mandatory	When this flag is enabled, then when an Operator is added or an Operator Record is edited, a myBepoz User Account must be entered & requested MyBepoz ID is entered & requested for each Operator in Operator Maintenance NB: At the time of this article's publication, the myBepoz frontend is currently still in development; once this available, details on how to register and login will be provided
Update Operator with MyBepoz User Info	When this flag is enabled, the User information from MyBepoz (using the Mybepoz ID) will be used to populate certain fields in the Bepoz Operator record: First Name Last Name Email Address Mobile Number Photo Gender Date of Birth If this flag is not enabled, but MyBepoz is still being used, the MyBepoz ID will still be linked, however, the existing details for the Operator record will be retained

Bepoz Online

This section allows for automating the Bepoz Online setup and configuration
Retrieve Settings Button:

Click this button to retrieve the Organization's Secret Key, Client ID and Connection Port

Test Connection Button:

Clicking this button validates the connectivity with Bepoz Online and the Organization's Bepoz Account