New in 5.1.3

• Fix for Googlepicker. It did not open if it was used in an Integration Wizard (bug introduced in 5.1.1).

• Modifiers are now applied in static calls - source (in the flow design phase). An example:

Consider a component with a dynamic input port inspector. The inspector definition is returned by calling the SourceWithModifiers component and sending it a few parameters. The entityType parameter is taken from properties and passed to the input in port of the source component. Based on the value of the user provided property entityType, the SourceWithModifiers component returns different input fields of the inspector. Now assume that the entityType value is defined with a variable and even a modifier can be applied to it.

In this example, the entityType is taken from the flow’s custom fields (and a modifier JSONPath is applied to it). In the previous versions of Appmixer the value propagated to the source component (SourceWithModifiers in this case) was not resolved, i.e. the potential variables and modifiers applied to the propagated parameter where not correctly evaluated when they reached the source component (SourceWithModifiers).

New in 5.1.2

• Fix for manifest markers in the component.json (https://docs.appmixer.com/appmixer/component-definition/manifest/marker).

• Fix for checking the component’s output port message size. The output port message size is limited to 15MB, in certain cases, an input message for the component and its size was incorrectly covered in the limit, too.

• Fixed bug in the context.loadOutputSchemaProperties() introduced in 5.1.1

• Fixed a bug in clearing node cache before requiring component’s codes into memory.

• Fix for UI/SDK code freeze in case of a large number of links/connectors in certain scenarios.

• PUT /flows/{flowId} API endpoint was optimized and significantly improved performance (especially with large flows) by avoiding variables scopes check with each update.

New in 5.1.1

• Possibility to secure the create user (POST /user) API endpoint. This helps prevent external API calls (possibly malicious) from creating users without any authentication. Newly, a user scope can be defined using the API_USER_CREATE_SCOPE system variable which will be required when calling the POST /user endpoint. Typically, an “admin” scope is set so that only admin users can create new user accounts. See https://docs.appmixer.com/appmixer/tutorials/appmixer-virtual-users for more information.

• New connector context function context.loadOutputSchemaProperties(), which is now used by the Each connector (Controls module version 1.4.4). This fixes a few issues:

  • When Each connector was used in a loop in the flow, it could cause a crash of an Appmixer engine.

  • Add variable discovery for nested props:

  Given the following output schema, when applying Each on "main" it does show the properties of the items in the next step (the next connected connector) in the flow, but applying Each on "sub.subitems" does not display the properties nor Index/Value, as if it doesn't recognize it as an array at all.

   "outPorts": [
        {
            "name": "out",
            "schema": {
                "type": "object",
                "properties": {
                    "main": {
                        "type": "array",
                        "items": {
                            "type": "object",
                            "properties": {
                                "prop": { 
                                    "type": "string", "title": "prop" 
                                }
                            }
                        }
                    },
                    "sub": {
                        "title": "Sub",
                        "type": "object",
                        "properties": {
                            "subitems": {
                                "type": "array",
                                "items": {
                                    "type": "object",
                                    "properties": {
                                        "subprop": { 
                                            "type": "string", 
                                            "title": "subprop" 
                                        }
                                    }
                                }
                            }
                        }
                    }
                }
            }
        }
    ]

• Fixed a bug where the Appmixer SDK was slow with a large connector definition.

• Fixed a regression in the DELETE /files API endpoint (bug introduced in 5.1.0).

• Fixed a problem with a wrong connector token that was cached. If connector A used another auxiliary connector B in the component.json (typically connector A needs a list of dynamic items to be displayed in the UI and it uses a different connector to populate such a list) and the scope of the tokens for connector A and B - defined in the component.json - was different, then the engine could store the token for B in cache for the connector A. When such a flow was started, it resulted in an error, the cached token for B did not work when the connector A was called with a new message.

• Fixed a bug in the Integration Wizard, creating an account did not work if the authentication file (auth.js) was on the module ([vendor]/[service]/[module]/auth.js) level and not the service ([vendor]/[service]/auth.js) level.

New in 5.1.0

• Appmixer is now fully compatible with AWS managed services - tested with OpenSearch 2.7, DocumentDB 4.0.0, Amazon MQ 3.8.34, Amazon ElastiCache 6.2.6 and logstash 7.6.12 with OpenSearch plugin

• Optional token (API keys, OAuth tokens, …) encryption (self-managed Appmixer only). https://docs.appmixer.com/appmixer/v/5.1/appmixer-self-managed/configuration#token-encryption

• User files (files created in flows, or through the /files API) can be stored in MinIO/S3 storage (self-managed Appmixer only). https://docs.appmixer.com/appmixer/v/5.1/appmixer-self-managed/system-plugins#minio-s3

• Configurable public files route. https://docs.appmixer.com/appmixer/v/5.1/appmixer-backoffice/system-configurationhttps://docs.appmixer.com/appmixer/v/5.1/appmixer-backoffice/public-files

• Added DB index to fs.files.metadata.fileType.

• APPMIXER_API_URL configuration support suffix. In the previous version, it was not possible to set the URL to https://acme.com/suffix, the suffix was removed.

• OneDrive and GDrive picker fixes (did not work properly, when connected account was changed).

• New context.job.lock() function in the component plugin contex (used in the latest Task module 1.0.2, instead of context.lock()).