Skip to main content
Skip table of contents

ISAC Platform Server 20.9

What’s New

Retrieve Seed Models from Sandbox Org

Solution Admins can now generate and import a data bundle which includes the required seed data for a solution to work.

To support this functionality, a new request API, “{{host}}/admin/sandbox/getSandboxSeedModels” retrieves seed models from the sandbox org where the user can choose multiple models to get. Only deployed and seed models are part of {{host}}/admin/sandbox/getSandboxSeedModels response. The records overwrite any existing seed data records in production.

Implementation:

  • [ZPS-97] - API for getting seed models from sandbox org

  • [ZPS-179] - API for getting seed models data from sandbox org

  • [ZPS-658] - getSandboxSeedModels api response to have the records which are not in Draft status

Select Data for Data Bundle

Users can now select only the data they want to save in a data bundle.

When users select Prepare For Import, only selected data are imported as part of the data bundle. For existing records in Production, records are automatically overridden with the new records. Duplicate and unselected records are not imported.

Implementation: [ZPS-180] - Modify Prepare for import api to accept seed data selected by the user

Sendbird Integration for User Communication

Sendbird is a customizable messaging SDK and chat API that enables developers to quickly build in-app messaging for mobile, web, and user applications.

With Sendbird’s integration into Zinier, the following is now available:

  • New API which gives user details and Sendbird application ID in response (when Sendbird is enabled)

  • Token and key for encrypting and decrypting. Key can be org specific

  • Batch API to create the Sendbird username for all the existing users or create the Sendbird users when the user details are fetched.

Solution Admin/Developers can choose to enable/disable Sendbird (Config API available) and read this, and register the users on SendBird

For details, see Sendbird Integration.

Implementation: [ZPS-925] - Sendbird integration for in-app user communication

Localization Support in System Models' Fields

Required model fields in these system models now support localization:

  • ZProject

  • ZProcess

  • ZPage

  • ZProcessInstance

  • ZProcessInstanceArchive

  • SyncBuffer

  • SyncBufferArchive

  • AimlRecs

Implementation: [ZPS-741] - Batch1 - System model fields to apply localization on required model fields.

New API to Refresh Cache

System Admins can now refresh the cache in resource, model, and EntityConfig with the new API, refreshCache.
API: {{host}}/admin/cache/refreshCache
Request body:- {"data":[{"pattern":"Any String Value Followed by * "}]}

System Admin can only refresh the cache if Redis is enabled in the system and if Redis don't find any key with the specified pattern.

These patterns are used to maintain keys in the cache:

  • Entity config: orgName|ModelName|PrimaryKey1|Primarykey2|…..Primarykey N

  • Resource cache: OrgName|Locale|target

Implementation: [ZPS-742] - API to refresh the cache

Improvements

General Sandbox Enhancements

Description

Implementation

Updated sandbox objects are now reflected in the production.

[ZPS-406] - Imp | Sandbox: Updated sandbox objects are not getting populated in Sandbox Org

Ensure that there is a backward compatibility Issue on Sandbox Refresh (Implementation:

[ZPS-786] - Backward Compatibility Issue: Getting System error on Sandbox Refresh)

The JSON data is now read and loaded in batches or smaller chunks instead of as a whole for Create and Reset.

[ZPS-617] - Sandbox 1.0 Enhancements | File Chunks

New Sandbox Types

Introduced two Sandbox types, Dev and Test to ensure that only the changes from a rightly tagged (Dev) sandbox are being merged back to the production/parent org. All the existing sandbox by default become ‘Dev’ Sandbox type. A Sandbox Type cannot be changed after creation.

Features include:

  • New sandbox create and update requests contain a mandatory attribute ‘Sandbox type’.

  • Each Sandbox Type can have a list of actions associated with it. These actions can only be added or modified by a Superuser

  • Only the changes from a Dev Sandbox type are allowed to merge back to a production or a parent org while the changes from the Test Sandbox type cannot.

Table: Mapping of the Sandbox Type and Action should be predefined.

Action

Dev Sandbox

Test Sandbox

Create

Yes

Yes

Import

Yes

No

Reset

Yes

Yes

Refresh

Yes

No

Discard

Yes

Yes

Archive

Yes

Yes

Edit App Version and Store Release Notes

Solution admins can now input the App Version of a solution bundle manually and include release notes.

The app version of the solution bundle is editable only when the bundle is still in draft. For existing bundles, it displays the current version number of the solution bundle.

On the Add New or Edit (Move to draft) of a solution bundle, solution admins can now go to App Version Label and enter an alphanumeric string as input.

Both the Release Notes and App Version fields are optional and can be null.

The new App Version Label field has the following validations:

  • Restrict text length to 50 characters

  • Restrict special characters except for ‘.’ and ‘_’ and ‘-’

  • No starting or ending with ‘.’ and ‘_’ and ‘-’

  • Min length is 1 character, max length 50

  • Alphanumeric characters are allowed

  • No space - needs to be one no-space string

Error messages for the specific validations must follow below:

  • Restrict text length to 50 characters. Min length is 1 character, max length 50 - App Version Label is too long. Maximum 50 characters allowed.

  • Restrict special characters except for ‘.’ and ‘_’ and ‘-’ - No special characters except for ‘.','_' and '-' is allowed

  • No starting or ending with ‘.’ and ‘_’ and ‘-’ - App Version Label cannot start or end with ‘.','_' and '-'

  • No space - needs to be one no-space string - No spaces allowed

Implementation: [ZPS-413] - Solution Bundle - Make App Version editable, store release notes

Model Error and Exception Handling

The exception handling for models includes these scenarios :

  • Create and update a model’s flows.

  • Publish and deploy the model with invalid inputs.

  • Display correct error display witherror code on passing Invalid / No inputs for Model Link and Model link fields

Implementation: [ZPS-483] - Model design flow error and exception handling

Changed Datatype for appMinVersion

The dataType for the appMinVersion field in solutionDependency table has now been changed to accept float values.

The change was done to align this field’s dataType with the solution table > solutionVersion field.

Implementation: [ZPS-547] - Need to change the dataType for `app_min_version` field in solutionDependency table.

Security Config

Security configs are moved to the system level. Solution Admin can add or edit the security config.

The {{host}}/system/read API has been updated to only read from EntityConfig, SamlServer, and OauthServer and if the fields are encrypted give the decrypted value.

Implementation: [ZPS-609] - Auth0 | Security Configs at System Level

Check that API Responses Have Unique Codes

Check that API responses have unique codes that both the web and mobile can consume instead of mapping with text values.

Implementation [ZPS-625] - Ensure status codes are returned in the response for web and mobile to consume instead of mapping with text values

Update EntityConfig cache

For all sandbox operations; when data is copied, the entityConfigs data must be moved to the cache manually.

A new system/insert API can now insert org specific entityConfigs. These configs also to be cached.

  • During a create, refresh, or reset; the cache is updated with a new or modified entity config value from prod to sb.

  • Import updates the cache with new/modified entity config value from sb to prod

Implementation: [ZPS-743] - EntityConfig cache to be updated (sandbox + configs & system/insert configs)

Validate Empty Array in Query

When an empty array is passed in a query/read, the system now throws an error with an error message.

Implementation: [ZPS-644] - Validate empty array during query read

Bug Fixes

  • [ZPS-624] - sandbox : Update the modified time only if the status is changed

  • [ZPS-643] - Error while marking encrypted as True for entityConfigs.

  • [ZPS-718] - “About Zinier” and the associated popup is not getting localised for "locale": "ja"

  • [ZPS-758] - API user and App Store user activation, cannot have both successfully and error message at same time

  • [ZPS-771] - bufferSync tasks are not processing successfully.

  • [ZPS-772] - Sandbox: import failed with Invalid node definition: End

  • [ZPS-817] - All nodes of Model Event WF are not getting triggered

  • [ZPS-850] - Special characters like ò are not showing up in the email

  • [ZPS-878] - Updating ConfigValues in EntityConfig is not getting reflected in Cache

  • [ZPS-938] - Text length too long for linkOrder. Allowed text length is 3.

JavaScript errors detected

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

If this problem persists, please contact our support.