Skip to main content
Skip table of contents

ISAC 3.4

These release notes include details of the New Features, Product Improvements that are added as part of the 3.4 release. In Zinier, we follow a push upgrade process for releases where the latest versions are all released simultaneously.

Beta Release Date: to

General Availability Release Date: 1 pm to 6 pm IST


Watch the recording and the slides of the Demo Release here:


Studio Z

All studio Z Features are available to all org when the release is live, no configuration is needed.

Mobile Page Builder Form Views

What Problem does it Solve?

Today, users can drag and drop components on the mobile page builder to create pages, but configuring components requires coding.

How does it Solve it?

Users can configure widgets on a mobile page without the need to write code using a simple form view.

New Form Views:

  • Video/Photo Input

  • Video/Photo Check

  • Video/Photo Comment

  • Collapsible/Fixed Container


Enhanced Mobile Workflow Builder

What Problem does it Solve?

The mobile workflow builder can be complex to navigate, making it difficult to use.

How does it Solve it?

This feature guides the user step by step through the process of configuring the nodes and the pages to be displayed for a technician during the execution of a page.



Third-Party AI Models

What Problem does it Solve?

Studio-Z currently supports only training binary classification AI models. There is a long time to maturity to support different AI model types on the platform. Therefore it is important to allow bringing in AI models that are trained outside the Zinier platform to support a wider variety of ML use cases.

How does it Solve it?

Enabling the Zinier platform to deploy AI models trained outside Zinier helps the AI team to leverage mature state-of-the-art external platforms, tools, and frameworks such as AWS Sagemaker, Tensorflow, Pytorch, etc. to train AI models. These AI models can be deployed as AI services and seamlessly integrated with workflows.

(info) NOTE: To use the AI services capability for any of the customers, the first step is to acquire the right datasets for AI model development. The AI team will assist in identifying the datasets for AI model development. Once the AI models are developed by the AI team, they can be deployed as AI services and cosumed by the solutions team for particular AI use cases. Please contact @a user @a user for any questions.


Scheduler As a Service

What Problem does it Solve?

The current infrastructure leads to a greater load on the Server whenever a Scheduler is invoked, leading to the system appearing slow, and possible downtime. With more customers and implementations using the Schedulers, the risk involved increases.

How does it Solve it?

Rearchitecting the scheduler as a service that utilizes an alternate on-demand infrastructure, thereby reducing the impact on the main Zinier App Server, effectively reducing the chances for downtime.


The following entity config should be added to the org to use the Scheduler as a Service:

JSON
{
"configScope": "scheduler",
"configKey":"schedulerAsService",
"valueType":"boolean",
"value":true
}


Web

Draw Polygon Shapes on a Map

What Problem does it Solve?

The current map component in the Zinier web interface web does not allow you to select multiple items, this can lead to more work for the back office.

How does it Solve it?
Allows a user to draw shapes around data points on a map in order to select multiple items on a map which reduces manual actions by a back-office employee. This feature has to be configured in a solution and is as of the time of this release not yet available in FSE.

Example use case
Select multiple tasks on a map that can be dispatched at the same time.


Web & Mobile App

Actionable Notifications

What Problem does it Solve?

Notifications in the Zinier applications are read-only. Users have to figure out how to take action based on a notification, which can result in inefficiencies.

How does it Solve it?

Enhanced Notifications features allow solution developers to configure an action for a notification.

Technical Details

  • Web and Mobile

    • Navigate to an external URL that opens in the device's native browser(for example Safari, Chrome, Firefox Etc.

  • Web

    • Allows for 2 buttons

    • Open a Mainpage or Specific Task Side panel

  • Mobile

    • Allows for 1 button

    • Two types

      • Navigate to a task

      • Open External URL


Mobile App

Autosave Task Data

What Problem does it Solve?

Technicians can experience app crashes due to memory/device limitations. Crashes can lead to loss of data which results in rework.

How does it Solve it?
All data on the main and subpages are stored in the mobile device and synced back to the server within 3 min when connected to the internet.

Technical Details

  • Main page:

    • No configuration is required, the data on the main page gets automatically saved in the local storage of the user's device.

  • Subpages

    • The data in the subpages will be saved automatically when the user moves out of the page depending on a configuration set at the component level, isAutoSave.

    • isAutoSave accepts boolean values : true/false

    • The default value for isAutoSave is false

    • When isAutoSave is set to true the data in the subpages get automatically saved when the user moves out of the page

    • Leave page alert for a subpage will get overridden with the Autosave configuration. If isAutoSave is true then the alert will not be shown and the data will get saved

Sample json:

CODE
 {
          "allowDelete": 0,
          "endColumn": 11,
          "hidden": true,
          "indexName": "index1",
          "isAutoSave": true,👈🏼
          "editable": 1,
          "index": 5,
          "title": "Single select offline only2",
          "type": "datagrid",
          "required": 1,
          "editRowPageId": "L52LFK68XP",
          "startColumn": 0,
          "addRowPageId": "L52LFK68XP",
          "disableAdd": 0,
          "id": "selectDataGrid2",
          "value": "@pageContext.selectDataGrid2"
        }


Improved Task List Beta

What Problem does it Solve?

The task list currently does not display info about submitted tasks nor the syncing status, often leading to confusion for technicians.

How does it Solve it?

An improved task list that can show more details about each task, sync status, and more in order to enable better coordination between the front and back office and give more clarity to the app user.

Technical Details

  • The task is not available on an org unless configured, the new Task List can be enabled using an org config

  • The scope for the ISAC 3.4 release contains the following:

    • New Task Card Design

    • Task Status

    • Up to 4 configurable fields

    • Sync Status

  • This is a Beta release, an improved version with additional features is targeted for the ISAC 3.5 release such as tabs for open and completed tasks, sync animations, and more…




JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.