Release Notes for 2021.11
Available on: 23 December 2021
Supported Browsers and OS
Supported OS:
Ubuntu 18.04, 20.04
Red Hat Enterprise Linux 8
Supported Browsers:
Apple Safari
Google Chrome
Microsoft Edge
Mozilla Firefox
Supported Screen Resolutions:
FullHD (1920x1080) or higher, with browser zoom level at 100%
Release Component Versions
Component | Version |
---|---|
Pliant | 2021.11.339 |
addon-ansible | 1.9.0 |
addon-mqws | 1.3.0 |
addon-puppeteer | 1.13.0 |
addon-textfsm | 1.4.0 |
addon-themes | 1.32.0 |
addon-trigger | 1.33.0 |
pliant-api-radius | 1.3.0 |
pliant-api | 1.102.1 |
pliant-app-gateway | 1.9.1 |
pliant-compiler | 1.20.0 |
pliant-db-migration | 1.28.0 |
pliant-front | 1.132.8 |
pliant-integrations | 2.65.2 |
pliant-proxy | 1.22.2 |
pliant-scheduler | 1.12.0 |
pliant-versioning | 1.17.0 |
pliant-worker-nodejs-config | 1.16.0 |
pliant-worker-nodejs-remote | 1.27.0 |
pliant-worker-nodejs | 1.83.0 |
Key features and improvements
API Gateway
A whole new portal allows you to deploy any Pliant flow as an API endpoint. With the new portal you can:
Create multiple APIs, each with its own settings
Have multiple stages for each API, such as Dev, QA, Staging, Prod, or anything of your choice
Have a different endpoint for each API and Stage, with GET, POST, PUT, DELETE and PATCH supported
Choose whether to use the latest or current version of the flow in case any changes are made later
Set authentication type (choose between anonymous, everyone in Pliant, or yourself only)
Set any worker group to run the flow with
Run in real-time or with logs
Select for the statistics to be part of the result or not
Set timeouts for messages and responses
Return custom status error code
Apply most of these settings individually per API, stage, and endpoint
A completely new SwitchCase block
If you need to check many conditions for a single variable, there is no need to put countless If-Then-Else blocks anymore. A completely new Switch block allows you to add as many conditions as you need, and a default behavior if your expression does not match any of these conditions.
Redesigned login page with custom logo support
The Pliant login page has an entirely new look. You can now add your own logo on the login page as part of any theme. To achieve this, the Theme Customizer was redesigned and improved, too.
Redesigned execution logs in the Workflow Editor
There is a new execution pane in the Workflow Editor, and each execution is now shown there:
Each execution is shown in a separate tab.
You can now see each run with its number and timestamp.
A convenient status bar shows what happens with the flow after you press the Run button.
If a flow execution fails, you can navigate to the erroneous block with a single click.
Better handling of missing, invalid, and expired licenses
Pliant displays a more descriptive error message if there is a problem with your license limitations. Additionally, more opportunities for license limitations are added:
Maximum flow size
Maximum number of active workflows
Maximum number of flows per user
Maximum number of jobs per user
Improved cut/copy/paste of any group of blocks
While in the clipboard, cut or copied content is stored as an image representing a flow thumbnail.
Support of anyOf schema
JSON Schema includes a few keywords for combining schemas together. You can now freely use the anyOf keyword, which allows you to create several subschemas and validate content against any of them (boolean concept OR).
Other UI/UX Improvements
You can now jump to the top and bottom of the flow using the Home and End buttons. For Mac users, these are Fn + Left Arrow and Fn + Right Arrow.
Search boxes now have an “X” button to clear the search
Flow name displayed in confirmation dialog for starting flows
Improved dragging of action blocks and scrolling within the Workflow Editor
Added and improved labels, buttons, information, tooltips, and error messages in different components
Under the hood
Pliant installation got even easier with the full overlay packages and capability for multi-node installation
When flows are committed to Git, they are pretty printed and show up in Git the same way they look in the JSON viewer of the Workflow Editor.
Improved memory management in workers
JWT tokens enhanced to store external credentials and support the future Authentication Integration Capability (AIC)
Pendo’s Content Security Policy added
Authentication creation API has a new allowUpdate flag that determines whether to overwrite the authentication if it already exists