Skip to main content

2022.0.3 to 2022.1.0

1. Changes to XML Handling in JDito: Removal of Inline XML (E4X) Support​

What changed​

From ADITO version 2022.1.0 onward, inline XML (E4X) syntax is no longer supported in JDito. This change aligns JDito syntax with the ECMA Script 6 standard.

Why it matters​

E4X syntax allowed inline XML definitions and attribute access using the @ operator, which is incompatible with TypeScript and modern JavaScript standards. Removing E4X improves compatibility and avoids conflicts, especially in environments using TypeScript such as Cypress tests.

  • Replace all inline XML (E4X) syntax with ES6-compliant XML handling using the XML constructor.
  • Change attribute access from the @ operator to array-style access using brackets (["attribute"]).

Example usage​

Old E4X syntax:

var xml =   <xml>
                <tag1 attrigbute="false"> tag1 content </tag1>
                <tag2> tag2 content </tag2>
            </xml>;
var tagAttribute = xml.tag1.@attribute;

New ES6-compliant syntax:

var xml = new XML("<xml> \
                    <tag1 attribute='false'> tag1 content </tag1> \
                    <tag2> tag2 content </tag2> \
                </xml>");
var tagContent = xml.tag1;
var tagAttribute = xml.tag1["attribute"];

Note: Accessing attributes via @ is no longer possible. Use bracket notation instead.

2. Changes Necessary to Run Flowable: Environment Variable and Service Updates​

What changed​

Starting from version 2022.0.0, updates to the Flowable service and its environment variables are required. The Flowable service pod’s environment variables must be modified or created as part of system configuration.

Why it matters​

Proper configuration of Flowable service and environment variables ensures compatibility and correct operation of the Flowable engine within ADITO.

  • Update Flowable to the system’s version.
  • Update the Flowable-Service to version 1.1.9.
  • Have the ADITO IT department create or update the following environment variables on the Flowable Engine system:
    • ADITO_URL=https://<LINK TO YOUR SYSTEM>
    • MICRONAUT_SERVER_PORT=8081
    • MICRONAUT_SSL_PORT=8444
    • FLOWABLE_USER=<taken from your SSP system → tab CONFIG MAPS>
    • FLOWABLE_PASSWORD=<taken from your SSP system → tab CONFIG MAPS>
  • Update the Flowable Engine service URL in ADITO Designer to: http://<host>:8081
  • Configure the Flowable Engine user and password to match the environment variables.
  • Restart the system after completing these steps.

Note: Text in <> denotes placeholders to be replaced with actual values.

3. Changes to clientid: Transition from Integer to UUID​

What changed​

ADITO now uses UUIDs instead of integers to identify logged-in clients. This affects the value returned by $sys.clientid when accessed via vars.get("$sys.clientid").

Why it matters​

Code that compares $sys.clientid to numeric values or expects integer IDs will fail or behave incorrectly.

  • Review all project code that uses $sys.clientid.
  • Update comparisons and processing logic to handle string UUIDs instead of integers.

Warning​

Failing to update your code accordingly may cause runtime errors or incorrect behavior.

4. Fixing Data_alias Missing After Project Upgrade​

What changed​

After upgrading a project, alias configurations may appear greyed out if the system database version has changed or if the database contains a different server ID than the project’s system.

Why it matters​

Greyed-out alias configurations prevent normal editing and usage, potentially disrupting project functionality.

  • Right-click the greyed-out alias configurations.
  • Select "Apply" instead of "Create".
  • The Designer will load all available configurations and allow you to select the appropriate one.

5. Setting the Size of Document Preview: Performance Optimization​

What changed​

From version 2022.1.0 onward, you can configure the size of the document preview to avoid rendering the entire file, improving performance.

Why it matters​

Large documents can slow down rendering and reduce system responsiveness.

  • Adjust the blobPreviewSize property within the Database node of your project preferences to control the preview size.

BlobPreviewSize_Preferences

Figure: Setting the blobPreviewSize property in project preferences