Grid Console Releases

Update login screen theme

Grid Billing initial progress (Grid billing will be rolled-out to public in August 2021. We will announce it soon)

Azure Marketplace Integration Fixes

Main console UI improvements

Non-IoT edge devices “Last seen” relative time

Non-IoT edge devices monitoring

Improved console Sidebar

1. Before

   

2. After

   

Installation Groups

1. My Installations - by default, all your existing installations are under “My Installations”

   

2. How to create or change an installation’s group

   1. Select an Installation you want to transfer

   2. Go to Settings tab and click “Add to group” dropdown

      

   3. There you can select a group, or create a new one

Installing New Apps

1. To install new app, click “Apps” on the sidebar Menu below the Organization name

   

2. Create new or select existing installation group

   

IoT Apps

• We’re very excited to share IoT Apps in public, as of now, IoT Apps is in Special Access

• Once all the necessary parts are shipped to production, we will provide documentation on how to build your own IoT Apps on top of the Grid

• Following are the updates for IoT Apps in this release

  • Disconnect device from IoT App installation

  • Device association to multiple IoT Apps

  • Device set-up for IoT App installation

  • Device connect for IoT App installation

Device Modules permissions is fixed.

1. BEFORE

   

2. NOW

   

Multi-language form widget

• Apps with default multi-language form field values, but not saved, should now be fixed

Downgrade default downloadable GridOS for Intel NUC devices from v0.8.1 to v0.7.6 due to unstable behaviors, during New Device Setup

Internal bugfixes

Introducing the New Improved Device Setup Flow

1. How do I create or register a new device into Ombori Grid?

   1. Go to the the installation where you want to connect your device.

   2. Go to Devices tab

   3. Click Connect a device button

   4. Initially, as mentioned in our previous releases, you can connect your existing device to an installation, through the new flow.

      

   5. Click Setup a New Device button

   6. You should able to see the new device registration form, with instructions on the left section.

      

   7. Follow the instructions. At the end of the flow, you will be navigated to your new device’s page.

2. List of supported hardwares/platforms
   We’re proud to announce that we support multiple hardware types, and platforms. There will be more in the coming days, but as of today, following are the supported ones:

   1. Intel NUC (GridOS - IoT Edge)

   2. Samsung Tizen TV

   3. Android Device (Ombori Grid Screen)- Special Preview (You need to contact Ombori to have special access. We will make it available to general public in few weeks)

   4. Windows 10 (Ombori Grid Screen)

   5. macOS (Ombori Grid Screen)

   6. Generic browser

      

   7. [NEXT FEW WEEKS] - Raspberry Pi 4

Farewell, Managed browsers tab
As mentioned in our 20201-05-06 release, we are retiring Managed browsers tab, in favor of a combined Managed browsers and Compute devices tab, called Devices

1. What does it mean for you?
   - You will no longer see Managed browsers tab on any of your Organization’s Page

   

2. What about my existing Managed browsers, like for Tizen and other custom Managed browsers?
   - No worries, all Managed browsers are combined with Grid Compute devices. For Tizen and other managed browsers with non-grid integrated devices, you will also see it as a device under Devices tab. If you click on the device thumbnail, you will be navigated to device page. There you will see a “Screen” tab, where you can configure your existing device.

   

Improved App Install Flow

1. On App Install from the Apps Library (Marketplace), Ombori Grid will create an initial build with initial settings.

2. Additionally, you will be redirected to the created Installation → Devices tab

Bug Fixes

• Search by Device serial, in Devices tab

• Installation → Content form fixes
  

Make sure you refresh your http://console.omborigrid.com page session.

Device Management
***We are retiring Managed browsers tab next week May 17, 2021, in favor of a single tab called Devices, which represents all different devices in the platform (Tizen, IoT Edge, Windows, Android, or Generic browsers on your desktop computers).

1. Installation → Devices tab + Device page

   • Renamed Compute devices to Devices tab

   • Devices tab shows list of Tizen, Windows, GridOS (IoT Edge), and Generic browsers as devices, that are connected to the specific installation.

     

   • If a Managed browser is running on a GridOS (IoT Edge) device, Managed browser and GridOS Device are combined in a single device, with a new “Screen” tab in device page. Settings tab is retained.

     

   • If a Managed browser is running on a non-GridOS (IoT Edge) device, Managed browser is shown as a device, with a “Screen” tab in device page. So instead of going to managed browser tab to update the environment of your device from prod to QA, for example, make use of the new Screen tab.

     

2. Installation → Devices → Connect a device feature

   • You can move/connect existing devices to an installation, within your organization, through “Connect a device” button

     

   • When adding a new device, the old form is retained. (Although we are also improving our new device set-up flow and UI next week)

     

3. Organization page → Library → Devices

   • We are also retiring Library → Managed browsers tab next week, in favor of the Devices tab

   • Renamed Compute devices to Devices tab

   • Devices tab shows list of Tizen, Windows, GridOS (IoT Edge), and Generic browsers as devices, under your organization.

     

4. Creating new IoT Edge Device

   • Once you create new IoT Edge device, it will show a new tab called “Modules” in the device page. There, you can configure the Modules that should run on your device:

     

IOT Apps

• We’re excited to share more details of IoT Apps in our marketplace, and custom IoT Apps development, soon

• For now, we’re slowly putting essential parts in production. We will publicly share more details as soon as we have everything in place.

• Updates:

  • Deployment flow

Sub-organizations Management (Library → Organizations)
a. Adding New Organization
- New:
* Slug is removed from the form fields, and is system generated on creation
* “Queue regions” property is replaced by a generic property “Data residency”. Previous “Queue regions” value is carried over as Data residency value.
* Removed Country, “Queue enabled”, “Custom overview dashboard”, “Is partner organization”, and “Parent organization ID” form fields
* By default, Virtual Queues will be visible to all organizations with valid “Data residency” value
* Data residency can be set to “EU”, “US”, “UAE”, or “AU”
* Data residency literally means the region where the data is stored and where the cloud services are running, under the organization. It is relevant to choose correct value to have efficient response time between the client devices and the server, specially for Virtual Queues. If the organization has stores in multiple regions, create separate sub-partner organizations, and assign distinct region for each.

- BEFORE:

b. Editing an existing sub-partner organization
- New:
* Removed the ability to change slug (We will support it soon)
* Removed Country, “Queue enabled”, “Custom overview dashboard”, “Is partner organization”, and “Parent organization ID” form fields as they were unnecessary.

- BEFORE:

c. Deleting an Organization
- New:
* Removed the ability to delete an organization (We will support it soon)

- BEFORE:

Sub-organizations Management (Installations → Virtual Queues)
a. As stated in item 1.a, Virtual queues tab is automatically visible according to Data residency. If the Organization does not have Virtual queues tab enabled, contact your partner, or contact Ombori.

Installations (Library → Installations)
a. Adding New Installations
- New:
* Renamed “Apps” to “Installations”
* Removed “Add Installation” button
* If you need to create an installation, go to Library → Apps, and click install on the App you want to install.

- BEFORE:

b. Deleting Installations
* When installation type is screen, prevent it to be deleted when there are associated devices (or Managed browsers) under it. You need to transfer the device or remove it, before you can delete the installation.
* When installation type is mobile, prevent it to be deleted when there are associated mobile endpoints. You need to delete mobile endpoints first, to delete the mobile installation.
* Removed “Add Installation” button
* If you need to create an installation, go to Library → Apps, and click install on the App you want to install.

Apps Library (Library → Apps)
- New:
* “Name” or “Slug” is removed from the form fields. Slug is now system generated on install
* “Display name is renamed” to “Name”

- BEFORE:

Installation Page
a. Settings tab
- New:
* “Name” or “Slug” is removed from the form fields. Slug is visible below the installation page title. Slug is not editable at the moment. (It will be supported soon)
* “Display name is renamed” to “Name”
* “Type” and “Provider” fields are removed from the form as those are unnecessary

- BEFORE:

New Modules
a. missing module can be removed from configuration

b. module migration warning is shown when settings are saved for the 1st time

c. Ability to rollback migrated device

Mobile Endpoints
- Ability to specify ui:widget: "mobileEndpointPicker" in meta-schema and show mobile endpoints picker in the installation content form

Rules:
a. Ability to pick a mobile endpoint for every organization's environment

b. Ability to manually input mobile endpoint URL

Installation Tabs
- Installation settings release and provider fields/picker fixes
- Ability to show correct installation tabs on installation type change.

Rules:

a. Windows -> show Compute devices, but NOT Managed browsers

b. WPA -> show Compute devices AND Managed browsers

c. Mobile WPA -> show only Mobile endpoints, and NOT Compute devices and Managed browsers

Managed Browsers
- Ability to move managed browsers
WARNING: Moving a managed browser does not move the associate Edge device. This is useful for Tizen managed browsers. Meanwhile, moving a device, currently also moves the associated managed browser. In the following weeks, we will be introducing Headless Devices. We will keep you posted and write separate page in this space for detailed information.
Example:

Apps Library
- Disallow duplicate app package name in organization level

Organization Files

- Files and folders under a folder should not be visible in root directory

Modules Migration
- Ability to migrate Edge device to new modules flow (Device → Modules tab)
- not accessible outside Ombori at the moment
- we will announce new Modules flow soon

Permissions fixes
- Make Library -> Overview default view on organization page if exists
- if organization Overview is not available for the organization, the first installation under the organization will be the default view
- Made possible to add a “Statistics Viewer” only user (create a custom User Role)

Device restart bug fix

Queue create/update form email list fixes(Login via email)
- In queue form Login via email field, users under parent/partner organization are visible in queues in Sub-partner organizations
- In queue form Login via email field, sysadmin can add sysadmins, and users under specific org and its parent org

Organizations
a. Disallow duplicate organization names globally
b. Enforce organization name in kebab-case

Installations
a. Disallow duplicate installation names globally
b. Enforce installation name in kebab-case

Modules
a. Modules tab in Edge type devices
b. Basic device module add and save operations

Apps Library and Mobile endpoints
a. Ability to create Screen, Mobile or Module app in Apps Library
a. Ability to install “Mobile” app type in apps library