Gemsstock Sprint 26: Feature Freeze 11.3

Reguël Wermelinger

Topics:

Variable Editor
Inscription: completion of types
New ‘Form’ Dialog Wizard
SOAP-Client Codegen
Engine Migration Wizard
Statistic API: can workOn

Lukas Giger

1 - Variables Editor

The first of many next generation config editors has been integrated into the VSCode extension. Now, you can edit your variables.yaml file through a handy user interface.

Audience

Process developers

Value

Add, edit and delete variables
Search for variables by name and value

Discussion

Feedback

Next steps

Integrate editor into the old designer (Eclipse)
Introduce communication with the engine for functionalities like validation, encrypting/decrypting passwords, etc.
Allow directly editing the file if metadata file is chosen
Apply latest UI design

Screenshots / Code

Elio Di Puma

2 - Inscription: completion of Types

In this sprint we were able to extend completion support inside the monaco editor for types/classes🙌
Additionally, we streamlined differend tabs across multiple elements.

Audience

Process Developers

Value

Completion of Types: Now, you can add classes inside the monaco editor much easier and faster. Simply type a class name in the Monaco editor, select the correct class from the completion list, and it will be added into your code. Additionally, the corresponding import for the class is automatically included.
Streamline Tabs: The names of various tabs and their order etc. have been slightly adjusted to create a more uniform and consistent inscription view.

Discussion

Feedback?

Screenshots / Code

Reguël Wermelinger

3 - New 'Form' Dialog Wizard

Form based Dialogs are now easy to create for everyone.

Audience

Process Developers, Pre-sales

Value

Existing 'New Dialog Wizard' allows to create Form based dialogs with the Designer (Eclipse+Web)
Project-Migration enables existing projects to use Form-Dialogs

Next steps

The Form Dialog Editor is still an Alpha, giving Leading Edge users first insights into the ongoing development
We invest into covering more use-cases with it toward LTS12

Screenshots / Code

Reguël Wermelinger

4 - SOAP Client Codegeneration

Re-usable custom SOAP Webservice code-generation settings.

Audience

Process Developers

Value

A new option in the Client-Codegen wizard supports 'underscore' names in types. Making manual WSDL patches obsolete for services containing them.
Namespace-Mappings are here to prevent package-name collisions with your existing project environment, we now store the chosen mappings of the generator dialog, in order to re-use them on sub-sequent regeneration runs.
Now you can also define namespaces for WSDL schema imports, that do not declare a 'targetNamespace'

Discussion

are there other scenarios that require manual patching of WSDL files, which CXF could handle?

Screenshots / Code

Alexander Suter

5 - Engine Migration Wizard

Migration Wizard takes over the complete control of an Axon Ivy Engine migration. There are up-front checks before the migration starts.

It checks the validity of the path
It checks if it can connect to the system database

We differentiate between a STANDARD migration and an IN-PLACE migration:

Standard Migration: The new Axon Ivy Engine is placed at a new location. Copy configuration and data files before the migration.
IN-Place Migration: The Axon Ivy Engine is placed at the same directory as the old one. If it's an in-place migration you can decide if you want to write the new configuration files at another place - this is important for read-only configuration scenario (Kubernetes).

Each system database migration step is now a single migration task.

Therefore, is no longer possible to only convert the system database.

The button in the engine cockpit no longer exists - Use Migration Wizard
The Engine Config Cli command to only convert the system database no longer exists- Use the migrate-engine CLI Command
The autoConvert property in ivy.yaml no longer exists. - There is at the moment not alternative.

Audience

Axon Ivy Engine Operators

Value

Simplified Engine Migrations

Discussion

Do you need an autoConvert configuration?
Do you miss something else?

Next steps

Upload the new license before migration
Disable applications before migration
Handle application directory and data directory
Handle dropins
Handle patches
Handle custom error pages
Project Conversion not on startup, instead a button in the Engine Cockpit. Useless waiting time.
Convert ivy.yaml and app.yaml to latest version
Add a button for in-place migration, that users don't have to guess
Guide user to migration wizard

Related Issues

https://1ivy.atlassian.net/browse/XIVY-13760

Screenshots / Code

Reto Weiss

6 - Statistic API; isInvolved/canWorkOn-Filter

Filter case statistics to show only cases I'm involved in or I can work on.

Audience

Portal Developer
Process Developer

Value

Filter case statistics to show only cases I'm involved
Filter case statistics to show only cases I can work on
Filter case statistics by tasks fields and tasks custom fields

Discussion

Next steps

Performance improvements

Screenshots / Code

/api/workflow/cases/stats?agg=businessState&filter=isInvolved
/api/workflow/cases/stats?agg=businessState&filter=tasks.canWorkOn
/api/workflow/cases/stats?agg=businessState&filter=tasks.priority:EXCEPTION
/api/workflow/cases/stats?agg=businessState&filter=tasks.customFields.customer:XYZ

Reguël Wermelinger

Noteworthy

Shortened passwords in Yaml Files > Base64 encoded
Validate ambiguous variables in the workspace
Roles are validated at runtime (Engine-Cockpit)
Custom Frontend-Proxy properties support
Enhanced Session counting