ISAC Platform Server 20.10

Features

Translate Node

Previously, there is no way to translate the Query Node result to a particular locale.

To translate the Query Node result, we have introduced Translate Node which translates Query Node output to a particular resource string. Translate Node then fetches the resource details from the resource table based on resourceId and locale string.

Example of Translate Node

CODE

 "translation": {
                    "connectors": [
                        {
                            "exitPortType": "NextStep",
                            "nodeId": "end"
                        }
                    ],
                    "name": "translation",
                    "description": "End",
                    "inputVarMap": {
                        "catalogData": "data",

                        "locale": "locale",
                        "defaultLocale": "defaultLocale"
                    },
                    "outputVarMap": {
                        "unassignedTask": "data"
                    },
                    "nodeType": "TRANSLATE"
                },

Implementation Details :

Translate Node - Design
[ZPS-684] - Ability to provide locale to query node in workflows

Dynamic Configs in Network Node

Solution Admin can now configure the dynamic networkId and externalSystemId inside the Network Node.

CODE

{
  "workflowContext": {
    "networkId": "googleDistanceMatrixAPI",
    "externalSystemId":"googleCredential"
  },
  "start": {
    "connectors": [
      {
        "exitPortType": "NextStep",
        "nodeId": "networkNode"
      }
    ],
    "name": "start",
    "description": "Start",
    "nodeType": "START"
  },
  "networkNode": {
    "inputVarMap": {
      "networkId": "networkId",
      "externalSystemId":"externalSystemId"
    },
    "connectors": [
      {
        "exitPortType": "NextStep",
        "nodeId": "end"
      }
    ],
    "name": "networkNode",
    "id": "networkNode",
    "description": "Network",
    "nodeType": "NETWORK"
  },
  "end": {
    "name": "end",
    "id": "end",
    "description": "End",
    "nodeType": "END"
  },
  "workflowNodes": [
    "start",
    "networkNode",
    "end"
  ]
}

Implementation Details

[ZPS-958] - Ability to provide dynamic network id / external system config in the network node

System Admin Enhancements

System Admin is a role type that has access to a system org to create new organizations in that server.

In this release, this role can now also:

Add a new Solution Admin user for an organization within the same server via API.
Invite/Re-invite Solution Admin user for an organization within the same server via API.

This ensures that if a new org has a Solution Admin that cannot log into the org, the System Admin can help with this.

Implementation Details

[ZPS-861] - Allow System Admin to add a new user for an Organization
[ZPS-862] - Allow System Admin to Invite/Re-invite user for an Organization
[ZPS-877] - EntityConfig cache to be updated (system/insert configs)

Sandbox file size limit

To improve the performance of creating sandbox, we introduced a file size limit on sandbox actions.

For the same sandbox, there can be multiple files for the same model.

Previously, the system creates one file for each model irrespective of checking the number of records and file size.

With the file size limited:

After iterating all the records and none of the conditions is true, it still creates one file for that model.
When the number of records exceeds 1k or the file size exceeds more than 5 MB, the system creates a new file.

Implementation Details

[ZPS-898] - Sandbox - put file size limit on S3 uploaded files on Sandbox actions
Sandbox multiple files support

SMS limit Org Config

New org config to set a max spending limit for SMSes sent by the org for 2FA notifications.

Example: Configuring a max spend

If this config is not added, the default value from the platform will be $0.02.

CODE

{
  "columns": [
    "configKey",
    "encrypted",
    "valueType",
    "configScope",
    "configValue"
  ],
  "data": [
    {  
      "configKey": "maxPrice",
      "encrypted": false,
      "valueType": "String",
      "configScope": "SMS",
      "configValue": "0.08",
      "recver":1,
      "modelName": "EntityConfig"
    }
  ]
}

Implementation Details : [ZPS-1073] - Org entity configuration for max limit of spend on SMS

Enhancements for SSO/Auth0 integration

These enhancements were done to support SSO and Auth0 integration.

Impact to users is illustrated in ISAC Frontend 20.10 Release Notes

[ZPS-1137] - Default workflow for permissions at system level for SSO users
[ZPS-1138] - Update Validation API
[ZPS-1139] - Display error for incorrect Org name
[ZPS-1136] - Add a new flag in groups
[ZPS-1159] - Providing flag for changePasswordAllowed
[ZPS-1165] - Providing logoutUrl in validateAuthResponse
[ZPS-1139] - Display error for incorrect Org name

Fixes

[ZPS-576] - Automatically addition of the model indexes by the system
[ZPS-752] - Inserting data to "time" fieldType is not getting reflected in response
[ZPS-753] - XML External Entity Injection [XXE Injection] in handleXMLResponse(HttpResponse response).
[ZPS-793] - Pull & update is checking lockedByUser for an object
[ZPS-800] - Sandbox : Reset Env status API is setting the status to failed but the next action set the sandbox to installed status. Now, user does not have access to sandbox as the invitation process is not completed
[ZPS-824] - TCS : System Error - Unable to access the sandboxes (tcs1207, cdvdemo)
[ZPS-829] - Variables are not replaced with actual values in the error message - sandbox reset status API.
[ZPS-845] - versionControl : merge to master - error_message: Record already updated by another thread!
[ZPS-872] - "admin/webnotification/deleteBulkNotification" api is not clearing all the notifications which is incorrect.
[ZPS-874] - data truncation - {"data":[],"errorTitle":"System Error","errorMessage":"Unterminated string at 31 [character 32 line 1]","status":false}
[ZPS-879] - installation_status value is committing before the installation completes.
[ZPS-893] - sandbox : getEnvstatus is failing (User is not able to perform any actions from frontEnd) . Also, Archive is failing because of same error.
[ZPS-894] - Expired web notifications are not deleted though the timer event provided by the system is running as expected
[ZPS-941] - havingClause in the query is not constructed in right way.
[ZPS-1062] - Model : Query/ read on tiny Integer fieldType is retrieving "True/false" as a response which is invalid
[ZPS-1086] - BVCONST - Sandbox creation failed
[ZPS-1131] - JSONArray fields are getting updated with data in the multirecord upsert functionality
[ZPS-1132] - Multirecord upsert issue: Duplication of data
[ZPS-1152] - deleteBulkNotification shouldn't be inside a transaction
[ZPS-1207] - Auth0:Error message is not proper when user enter invalid org name in the orgname screen
[ZPS-1037] - Update the translation in the DB for pf_delete_selected_group
[ZPS-1104] - Update Japanese translations in the DB
[ZPS-1179] - Japanese Localization: "Week" and "Month" to be translated
[ZPS-1160] - System config for accessing S3 buckets based on role
[ZPS-669] - Blocking to access the orgs if some of the configs/dependent objects are incorrectly configured - Pt 1