Release notes for https://console.omborigrid.com
| Expand |
|---|
| title | 2021-05-06 - Device Management & IoT Apps |
|---|
|
Make sure you refresh your http://console.omborigrid.com page session. Device Management
***We are retiring Managed browsers tab next week May 11, 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). 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. 
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) 
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.
IOT Apps We’re excited to share a 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:
|
| Expand |
|---|
| title | 2021-04-26 - General Improvements |
|---|
|
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: 
|
| Expand |
|---|
|
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
|
...