Vai al contenuto

Platform Release Note

v4.28.1 (October 28, 2019)

Login Site

The login-site has been modified to allow redirects to URLs containing query parameters

CMS v9.2.0

  1. Add a parameter to the configuration of a collection that enables the fact that every time I perform an action a confirmation message appears for each action
confirmBeforeEdit: true
  1. We have resized the page and improve the usability of the scroll We made the color of the scrollbar and its size configurable by variable:
--scrollbar-height: 6px (default è 6px)
--scrollbar-width: 6px (default è 6px)
--scrollbar-color: #000000 (default è rgba(0,0,0,0.2))

You should add this value in the custom css file.

v4.28.0 (October 18, 2019)

Breaking change v4.28.0

Export Service

This is the only breaking change for the configuration created from the console. Other breaking changes are for the console itself.

The new version of the platform need the export-service to enable the export functionality of the cms.

The export-service should be into the multitenant namespace. If you do not have already a multitenant namespace, you could create using this file and a file .secret to link to nexus. To deploy this service, you can use this deployment file and this service file. You can deploy this file with kubectl cli:

kubectl apply -f path/to/export-service.deployment.yml
kubectl apply -f path/to/export-service.service.yml

Once deployed, you must set as enabled into dev-console project on mongodb the export-service to true.



  "name": "Demo",
  "enabledServices": {
    "export-service": true

Create the configuration from the dev-console (from the website, commit the configuration to upgrade all services). This will create an headless service called export-service pointing to multitenant namespace. To view an example of the created service, click here.

Custom plugin templates

This change is already handled for console hosted from mia-platform, but must be handle by self hosted version of the console.

To facilitate subsequent developments and resolve some technical debts, we decided to move custom-plugin-templates collection to services collection and add other templates info. To enable the marketplace of services section of the console, you should move old templates to this new collection.

This is the crud configuration, and an example of service:

  "name": "Node Template",
  "archiveUrl": "",
  "description": "This is the best template to start creating a service in node integrated inside the platform",
  "type": "template",
  "supportedBy": "mia-platform",
  "image": [
      "_id": "5db0105743875a0011618815",
      "name": "36e6b6b4-36e1-4737-b65f-d1fb62bb3647.png",
      "file": "f2ca3f95-1556-446f-a098-dbc1ff219dc8.png",
      "size": 1532,
      "location": "/v2/files/download/f2ca3f95-1556-446f-a098-dbc1ff219dc8.png",
      "type": "image/png"
  "supportedByImage": [
      "_id": "5db0106143875a0011618816",
      "name": "e7c7ced2-e40e-465b-9e79-7d5c710badb2.png",
      "file": "e5ee5be6-e16d-4404-99a6-2f3ed2f91b64.png",
      "size": 139694,
      "location": "/v2/files/download/e5ee5be6-e16d-4404-99a6-2f3ed2f91b64.png",
      "type": "image/png"

API-Console backend configuration

This change is already handled for console hosted from mia-platform, but must be handle by self hosted version of the console.

To upgrade the api-console backend, you must add this environment variables:

  value: multitenant
  value: http://crud-service/api/services

and you should remove the TEMPLATES_CRUD_BASE_PATH variables, unused from this release.


Logs timeout

This change is already handled for console hosted from mia-platform, but must be handle by self hosted version of the console. This is not a breaking change.

The monitoring logs could run into an issue with the stream timeout. Logs may not be a continuous data stream, so logs could run into timeout and your monitoring dashboard users should refresh very often the logs view. To fix this issue, you should remove timeout for this specific endpoint. Here there is a documentation about how to enable a continuous stream of logs in node and nginx services. We handle this into the console kubernetes-service and the api-gateway, but there could be other infrastructure proxy (e.g. the client-proxy).

Design Section


  1. Marketplace in the Service Section

    In the services area we have introduced the marketplace. In this section you can find:

    • Mia templates, or the templates created from your company;
    • Example to create microservices;
    • Mia Plugins to implement some microservices of Mia's ecosystem microservice.
  2. Group expressions for the Backoffice APIs

    Now is possible to set up group expressions for the Backoffice APIs on the Endpoints Management page. This way you can show unique access privileges based on the groups created on the CMS.

  3. To speed up data loading we have introduced a new default index: createdAt = DESCENDANT

  4. When you create an endpoints you can start with /-

  5. Fullscreen mode when you are writing in the Editor.


  • We have sanitized the logs

  • We have made the refresh me more visible when a pod breaks down

API Portal v1.6.0


  • download for file

  • possibility to expand all the response and to copy the elements

Deploy Area


  • History page now fetch info in polling (2s)


  • Add feedback on button click. Now it is not possible to hit multiple times and start multiple deploy

  • Fix positive feedback on api error if previous deploy successful

  • Fix completedAt data to In progress if pipeline is in running

Back-and Developers Console


  • Management of readiness and probeness routes in Google Cloud

  • Management of backoffice ACL inheritance for endpoint and routes

  • 2 new env variables to interpolate in v1-adapter: EXPORT_SERVICE_URL and EXPORT_SERVICE_NDJSON_URL These variables are needed in v1-adapter in order to use new export-service with CMS


AC-1220: Change validation regex in Constants / basePath


  • Dependencies update
  • api-portal to 1.6.4
  • cms-backend to 1.2.0
  • crud-service to 2.0.1
  • session-manager to 4.4.0
  • v1-adapter to 2.2.0


  • Fixed ECONNREFUSED error by expecting the templateId in the request and contacting the CRUD service to get the template info

  • Fixed templateUrl CRUD retrieval using value property

Core Services

  1. New Export Service: This micro-service allows to export a data source to multiple formats. Input data source format must be a JSON lines. Supported output formats are:

    • JSON
    • CSV
    • HTML
    • XLSX
  2. Session Manager v4.4.0:

    implement check-up route

v4.27.0 (September 5, 2019)

Developers Console v1.8.0


New navigation flow of the monitoring area

The user will now be faced with the display of all the pods with the essential information to understand the general state of the system.

Once clicked the pod can choose which container to view the logs on. We have also integrated memory and cpu information.

In this view the last 100 logs are shown. Morover it is now possible to perform the following operations:

  • download of all logs
  • filtering of visible logs
  • stop of the scroll
  • clear of the display

New Import from JSON functionality when you create a new collection


  • Design CMS - Checkboxes in the property area do not save values
  • The cmslookup interface must appear even if the field is of type objectid

Headless CMS v9.1.1


Now you can see in the table the values saved in the lookups and multilookups with the correct formatting

v4.26.0 (August 8, 2019)

Developers Console - Design - v1.7.0


  • New Navigation Flow

    • add fallback page check if loaded project is valid
    • add fallback page check if branchId is valid
    • add default branchId on load design area
  • New Projects Container

    • add alphabetical sort for project
    • fix random color
  • New Login Page


  • Reactord v1.8.1
  • Decorators label and url has been updated to API PRE/POST


  • Checkbox in CRUD config table NOT saving information properly


  • Removed the creationTimestamp annotation from all yaml files generated. It was redundant with the commit timestamp and was a major problem for the Merge requests in the configuration project.

API Portal v.1.6.0


The following filters have been added:

  • by category
  • by tag
  • by method

The possibility of searching within the API has also been added


  • change error handling and fix subswagger URL

Monitoring & Kubernetes Service v.1.1.0


  • Add new query params for api /projects/:projectId/environments/:environmentName/pods /:podName/containers/:containerName/logs

  • Now you can set the accessToken for a cluster directly within the cluster configurations of the console project. If is not set in the db the value is read from the ENV variables as before.

  • Follow Functionality on Monitoring Dashboard - now see only the last 100 logs

  • Button for enable/disable autoscroll on new logs


  • removed milliseconds from countdown when delete a pod
  • corrected typo error when delete a pod

v4.25.0 (July 24, 2019)

Developers Console v1.6.0


  • support for underscore in endpoint basePath and route
  • support for collection name with dash


  • update v1-adapter to 2.1.2
  • update swagger-aggregator to 1.3.0

Swagger Aggregator v1.3.0


  • api /swagger/subswaggers/ to retrieve the list of available subswaggers

V1 Adapter 2.1.2


  • resolved key override problem when merging objects into _q in crudProxy.

v4.24.0 (July 8,2019)

Breaking Change

CRUD Service v2.0.0

Implement nullable flag. Before this, the nullable flag is ignored. The default behavuoir is to convert null into falsy value for the field type type. For example, for an integer null value is converted to 0, for a string to '' (empty string).


Both the handlers of /-/check-up and /-/healthz route check the connection to Mongo.


  • New Home Page! We have released the new homepage from which you can easily access the different sections of the developer portal

  • From now on it is possible to change the name of an analytic

  • It's also possible to set the visibility level of the repository when creating a project

Doctor Service: new service!

This microservice allows to check the healthiness of the services within a project.

The API exposed by the doctor service is:

  • GET /: it respondes with status code 200 if all the services are up; 503 if at least one is down. Furthermore, in the body of the response you can find additional information about the called services.

  • GET /${tag}: it respondes with status code 200 if all the services tagged with tag are up; 503 if at least one is down. Furthermore, in the body of the response you can find additional information about the called services.

/-/check-up route it's been added in the following service:

swagger aggregator: 1.2.0 mongodb reader: 1.2.0 crud service: 2.0.0 microservice gateway: 5.1.0 file service: 1.2.0 cms backend: 1.1.0 v1-adapter: 2.1.0 notifications-service: 1.1.0 notifications-manager: 1.0.0

v4.23.0 (June 27,2019)


  • In the launcher, all different documentation portals for each environment will now be available from the menu. They will appear based on the hostnames configured in the project creation phase.

  • added 'is production environment' flag in creation project phase

API Portal v1.3.0


  • updated api-explorer
  • shows the body when status code is 401


  • response headers are shown in a more readable way

API Gateway v4.1.0


  • add client-key header support
  • add mia_client_key cookie support


  • update nginx to 1.17.0


  • deprecate http header secret support, replaced by client-key header or mia_client_key cookie

Session Manager v4.3.0


  • set session cookie to secure if ORIGINAL_PROTOCOL_HEADER is set to https

CMS Backend v1.1.0


  • /-/check-up handler
  • /-/healthz handler
  • status routes tests
  • add hook to set secret cookie, setting secure if ORIGINAL_PROTOCOL_HEADER is set to https. Skip hook if BACKOFFICE_HEADER_KEY is not set to 'true'


  • Update @mia-platform/lc39 2.1.2 -> 2.2.0
  • Update eslint 5.16.0 -> 6.0.0
  • Update mongodb 3.2.5 -> 3.2.7
  • Update tap 14.1.7 -> 14.2.5

v4.22.1 (June 26,2019)

CMS v9.1.0


  • Following the update of the crud to v1.2.0 a limit of possible choices was introduced in a lookup of 200 instead of the previous 500

  • Handle the abscence of makeitapp-baas-secret-cookie

v4.22.0 (June 25,2019)

Breaking Change

Add the env variable: CRUD_LIMIT_CONSTRAINT_ENABLED to use the v.1.2.0 of the CRUD Service



Mia has released the new Metrics dashboard to monitor its applications. From the new application you will be able to view your configured Kibana dashboards.

To add the dashboards you should go to Mongo and within projects, for each environments of the desired projects insert the key "dashboards" with value an array of objects with keys: "id", "label" and "url"

an example follows

"dashboards": [
        "id": "the-id",
        "label": "My Dashboard",
        "url": "https: // / ......"


To add the link follow this procedure : go to Kibana, choose the dashboard, press share - permalink - snapshot - copy url. Once the url has been copied, the following parameter must be added: embed = true

Save to Mongo and you will see your dashboards on the Developer Console



  • the possibility of writing the names of the CRUDs in uppercase has also been added
  • alert message when write collection with upper case
  • alert message when write endpoint route with upper case



  • Tag "All APIS" in sidebar

CRUD v1.2.0


  • Support for the CRUD_LIMIT_CONSTRAINT_ENABLED env variables to enable constraints on minimum, maximum and default values. New limits are: maximum 200, minimum 1 and default 25

v4.21.0 (June 18,2019)


Mia has released the first version of the Developers Console. The Developers Console is a tool that allows you to manage the entire life cycle of a software product.


The launcher allows you to follow your development flow and access the different Developer Console sections.

The sections you can access are the following:

  • Design: In the Design area you can design your own APIs according to established guidelines. Create Microservices starting from Templates with configurable standards for you: log, security, readiness, probeness and documentation. All generated configurations are GIT centric.

  • Deploy: In the Deploy area you can release your services with a click that activates the automatic pipelines and you can visualize the history of your releases

  • Monitoring: In the Monitoring section it is possible to debug and monitor your own microservices.

  • Documentation: In the Documentation Portal users find all the documentation of their own APIs and microservices centralized and automatically generated.


The Monitoring Infrastructure section is the Developers Console area dedicated to the control and monitoring of its infrastructure.

The area is divided by the number of environments existing in that specific project. And it is possible to change the environment to be monitored via a tab in the top menu.

Within each individual environment you can view all the available pods with specific logs. In addition to viewing the logs, you can refresh the log by clicking "Refresh" and restart the pod by clicking on the "Delete Pod" button.

When the POD is deleted, it is actually erased and pulled onto a new pod. The user will see the logs of the new pod that are generated.


The History page is the second area of ​​the Deploy section. In this tab you can view all the deployments that have taken place.

In the history table I see the following information:

  • The status: if the deployment was successful or if it failed
  • The environment in which the deployment took place
  • The deployed version
  • The type of deployment
  • Who carried out the deployment
  • How long did the deployment last?
  • How long ago it was done
  • The git link to view the past deployment log.



  • If I create a field and create another one, the application splits

  • In the delete area I see the correct text to insert

  • Disable the ability to change the name of a crud property

  • possibility to insert the . in the name of an index



  • The basepaths are no longer shown in the left bar, but the tags
  • Multipart management


  • The name of the project is dynamic


CRUD v1.1.0


Support for patching array items. The $set command works properly on both primitive and RawObject item types, by using array.$.replace and array.$.merge as keys in the $set command object. This feature involves the following CRUD operations:

  • Patch by ID
  • Patch many
  • Patch bulk

array.$.replace Replace entirely the query-matching array item with the content passed as value.

array.$.merge Edits only the specified fields of the query-matching array item with the content passed as value.

Swagger Aggregator v1.1.0


  • The Swagger now manages the conflict between equal routes
    • Throw (default): returns an error in case of conflict - it is used for backward compatibility;
    • First: if I configure it, the first to arrive wins (the swagger aggregator gets an ordered list so files takes precedence over the crud)
  • Evolutionary to the feature of the subswagger: tagName which if present forces the API with that tag into a single subswagger.

Files Service v1.1.0


  • google-storage-api: Add GoogleStorage API as storage
  • additional-properties: Add additional properties in order to attach some props on upload
  • prefix-or-hostname: Add PATH_PREFIX for relative urls
  • swagger-additional-properties: Add swagger definition for additional properties

v4.20.0 (May 28, 2019)


API Console v1.1.0

This version must be used with backend v1.1.0


We have released the new documentation portal, called API Portal, created entirely by Mia-platform. To support the new API Portal, each project must activate the api-portal among its services. To activate, you should set "api-portal": true into enabledServices object in api-console projects collection into mongo.

API Portal

Breaking Change

Once the new api-portal is activated, it will no longer be possible to reach the old route /documentations/swagger/ The documentation will be available only from the new route: /documentations/api-portal/

New service management The service section were divided into two types: services and proxies

The services will no longer be managed using the Git URL and Git Revision, but using the name of the docker image.

New Custom Service

Furthermore, if it is necessary to write advanced configurations it is possible to write the advanced service and deployment files directly from the API console and add all the necessary configmaps files.

Advanced Section

New type of proxies: cross-projects

With the introduction of this new service it is possible to link to services created in another project, but present within our infrastructure. For security reasons it will be possible to link to the namespaces to which you have access.

Cross Projects

Revision table

We have restyled our table component, improving user experience and interactions with the component. It is more responsive, more compact, more readable, the delete is present on every single line, it is possible to resize the columns, and the addition of the elements has been moved downwards

New Table


  • we added the placeholders to all the empty sections
  • In the CMS area the default delete is always active, which allows to delete an element from db from the CMS
  • we added in the header the link to the project git
  • we added the ability to add a series to an analytic being edited


  • The configured lookups did not save the values
  • The advanced section did not load the files correctly
  • When creating a service, the recommended default name will no longer be the name of the group path, but the name of the namespace. To give an example before the name was: gruph-path/test-name now is: project/test-name.
  • Various graphic fixes


Updating fo Core Microservices

In all core microservices the routes of /healthz and /ready have been implemented. The microservices in node have been updated to version 2 of fastify.

The versions supported by the API console in v.1.1.0 are the following

acl-services: 1.0.2
cms-backend: 1.0.2
credential-service: 1.0.0
crud-service: 1.0.4
microservice-gateway: 5.0.3
mongodb-reader: 1.0.0
session manager: 4.2.2
swagger-aggregator: 1.0.5
user-service: 1.0.0
v1-adapter: 2.0.0
files-service: 1.0.2
mail-notification-service: 1.0.2
notifications-service: 1.0.0
token-service: 1.0.8


MailChimp Plugin This microservices allows to manage the users registration to Mailchimp lists. It provides methods to get the groups and to get, add, update or delete the users from a specific list as a user or prospect.

Notification Manager This microservice allows to easily and safely set the status (read/unread) of one or more notifications belonging to the requesting user. It also allows to retrive the notifications of a user, hiding the information that relates to the notifications but not to the user (e.g. the list of users who has read a notification).

V1 Adapter


  • We have fixed the fact that from the export of the CMS if I selected the label the id was exported anyway
  • Error handling in export pipes The "error" event, launched by a pipe in the event of an error, was not handled. we have created an error handler in exportsHttpInterface, which is passed to crudProxy and associated with the management of the error of

  • Management of objects in the queryString In the case of objects within the query parameter of getExport, this was passed to (which makes a call to the crud) was not managed.

Mongo DB Reader


  • Added path parameter to format input function

v4.19.3 (May 22, 2019)


CMS v9.0.2


The export with filters was paginated and exported only the elements present on the first page, with this fix it will be possible to export correctly all the filtered elements.

v4.19.2 (May 6,2019)


API Console v1.0.2


We have modified the limit of characters that could be inserted in the field Name of the table. Previously they were 32 now there are no character limits.

v4.19.1 (May 3,2019)


CMS v9.0.1


With the release of the new version of Google Chrome n.74 the scroll was broken. We quickly restored the correct display of the CMS

v4.19.0 (April 18, 2019)


API Console v1.0.0

This version must be used with backend v1.0.0

Breaking Change:

You should add two variables to enable push notifications for the new platform on v1Adapter or to use notification service:


You can value the variables above even with an empty string if you do not care about the functionality


Note that if the configuration project among its scripts has one called the variables must be added with a prefix MIA_ for all environments and DEV_ PREPROD_ or CLOUD_ for values ​​on a particular environment MIA_ is taken as a fallback value


  • New Header! You can find a new style in our header. Now you can view the photo of your user connected to Git and directly access the Mia-Platform Documentation and your Git project in the header.

  • New Sub-header. We have improved the display of the save area. If you have some changes unsaved it's more visible. You can also see when it's done the last commit.

  • If you click on your user, you can view your name, a new Info page and the logout section.

  • On the Info page you can view the Mia-Platform version number and the list of all the Mia core services version number that you are using.

  • In the Project Creation section it is now possible to select which core Mia services to activate. We have also given the possibility to change the name of the gitlab project or to create a subgroup.

  • In the Secret Section we have added the possibility to create random secret and copying them into your table.

  • The Custom Java Plugin has been added to Mia's Plugins

  • In the Custom Services it is now possible to configure the memory and CPU limits and set the probes


  • In the Git group drop-down menu you can now view all your paged groups

  • In the Creation of the project we made some fixes to the Environment Tab

  • We have fixed some particular cases in which the flags inside the endpoint section broke

  • We added the multilookup in the interfacetype of the cms linked to an array

  • we have fixed the validation of names on Custom Services


  • Mia has developed: lc39, a Command line utility that will launch a Fastify instance configured for serving a Node.js service on Mia-Platform. With this lanucher all the Node.js service will expose two fixed routes for heltinessProbe and for readinessProbe. In addiction is integrated the fastify-swagger module for exposing the service documentation. This Service has been imported in: ACL Service, CMS Backend, Swagger Aggregator, CRUD Service, Session Manager and Mail Service. Soon will be implemented in all the Mia services.

  • Swagger Aggregator v1.0.2: Swagger is now available with service down. The service down wiil not be shown.

  • Notification Service v0.6.1: it is possible to send push notifications by tag (if there is a collection tag with the tags configured)


CMS v9.0.0


  • It is possible to send push notifications from CMS using the new notification service (without legacy baas below) and can send notifications by tag (if there is a collection tag with the tags configured)


  • We have updated the dependencies of the project

  • Escape of regexes in the search to search for special characters

  • We have fixed the permanently delete from CMS

v4.18.0 (March 11, 2019)

API Console front-end - v0.16.0

This version must be used with backend v0.18.x


  • Advanced section where you can edit the configuration extension


  • now interfaceType in cms section are conditioned by crud property type

  • migrate route section in endpoint to new layout with antd


  • various fix in cms page

API Console Back-end - v0.18.0


  • advanced file edit plugin


  • various changes in api-gateway configuration:

  • debug mode, enabled with correct header sent, better route security (now query parameter are not matched in proxy name maps)

  • api-gateway version set to v4.0.0 minor/patches updates to all services improved app_dataentry proxy name mapping for better user flow update LICENSE


  • increase max path for fastify

CMS -v8.0.0

Performance Improved:

To improve performance, on download the resources are cleared of properties field (set to empty array) and all resources are saved into an external object (file src/app/storage.js). The retrieve of data from storage is cached with an lru to increase further the performance.

CRUD - v0.21.2

Fix: In case of upsert, if the document is not found a new one is inserted on the database. This document did not correctly set the updaterId and the updatedAt

Now invoking /upsert-one on a document not present in the database, a document is inserted with the updaterId and the updatedAt not null

Custom Plugin Node v0.7.0 * The getServiceProxy andgetDirectServiceProxy methods are also available on the Service instance and not just on theRequest instance. This implies that it will be possible to use these methods not only in route handlers, but also in the asynchronous function in which plugins are generally registered in fastify.

  • The get,post, put,patch, delete methods used to query the other endpoints of the platform, accept a new field in theoptions object. The name of the field is allowedStatusCodes; its value is an array of integers indicating the status codes allowed for the queried endpoint response. If the response status code is not included in the array values, the promise will be rejected by the custom plugin. If the field is omitted, all status codes will be accepted.

  • At startup, the custom-plugin verifies that the format of Mia's five headers comply with the RFC format.

v4.17.0 (Jan 16, 2019)


  • We have re-established the service area with the introduction of the possibility to add custom templates

  • We resitiate the deployment area and the header of the application

  • We have enabled the ability to write complex queries to filter the individual properties in the CMS

v4.16.0 (Dec 18, 2018)

  • Evolutions in the CMS configuration area:
  • you can highlight fields in the table by setting a query, background color and text color. This will allow the user of the CMS to highlight the most significant data.
  • we have also released the possibility of configuring notifications in the cms menu. Just activate the notifications and choose the query on the data you want to view. In this way a badge will appear next to the page where you have activated the notifications that will count the elements present in that collection based on your query.

  • We have set cancellation of the deductions also as regards the cancellation of the decorators within the Pre and Post Hook areas.

  • We have restyled the site's header to allow the user a better awareness of the project and of the branch in which he is working.

  • you can start creating a project from the home page. Thanks to this new feature, a project will be created on empty GitLab and will be added to the API API DB.

Evolution in the import of CMS. - v7.0.16

From today, if a file with existing ids is imported, the data are not duplicated but updated. If the id does not exist, a new data is created instead.


The Import Service works only with string and number.

v4.15.0 (Nov 14, 2018)

Breaking change api-console-configuration v0.3.0

We have released the following updates:

  • new version of api-console-configuration that has changed from v0.2.0 to v0.3.0. In this new configuration the following new features have been added:
  • we support the latest version of CRUD with the addition of two new routes: PATCH / and POST / upsert-one;
  • we have made it possible to edit the name of the category and the page in the CMS.

  • we have also enabled the cancellation of the analytics and made a fix on the filters.

v4.14.0 (Oct 31, 2018)

With version 0.14 we have released two updates:

  • conflict between two people working on the same branch has been resolved. If two people work on the same branch, the second person trying to commit is now blocked. In fact, he receives an error message to commit. The developer can however in the save page change the branch to be released and create a branch from his commit. In this way he can view his configurations on a new branch.

  • Two new interface types ** were created to support objects and arrays in the CMS section:

  • rawobject
  • rawarray With these interfaces you can directly edit the object and the array in json format.

CMS - v7.0.14

We have released the following features:

  • management of new rawObject and rawArray interfaces
  • change of labels in Public and Delete actions
  • fix to the management of the icons
  • ACL on groups that can access the CMS. To this link is how to configure this extension of the CMS.

v4.13.0 (Oct 23, 2018)

In this version we have released the update to the session manager and the new acl expression syntax and we have made fixes on the configuration of the analytics.

v4.12.0 (Oct 10, 2018)

Analytics Configurations

With version 0.12.0 it will be possible to configure the analytics from API Console. To this link the documentation on how you can configure them.

The possibility of setting up an acl for groups accessing the pages of the CMS has also been released. In this way, some pages can only be viewed by some user groups.

CMS - v7.0.11

In this version of the CMS you can select the icons from font-awesome up to version v5.3.1, which is the latest version supported (here is the [link] ( / icons? d = gallery) for the icons).


If you choose icons that were already used in the previous version, you will continue to display the old icons in the CMS. This is because priority is given to backward compatibility.

v4.11.0 (Sept 30, 2018)

CMS v7.0.4

In this version new CMS customizations have been released.

It will be possible to define the following css variables:

  • color brand gradient 1 = allows you to customize the color of the text in the menu sidebar
  • color badge - bg notification = allows you to customize color background of notifications badges
  • color badge - text notification = allows you to customize the color of the notification badge text

Also from this version the CMS font will be in Proxima-new

CMS v7.0.0 - Breaking Change (for Cards) With version 7, 3 important features have been released:

1) new card structure with the possibility of configuring different types of widgets and having a fully customizable structure. You can read the Documentation on how to configure the new cards [here] (

2) the highlight function has evolved. With this version it is possible to highlight the CMS lines by writing a query and the user can also configure the colors to highlight the line (text and background color). To this link an example of a highlight.

3) the possibility of having notifications in the menu has been added. Read to this link the documentation to see an example.

CMS v6.1.0

With version 6.1.0 we have released new features in the CMS export area. In fact, from this version it will be possible:

  1. Choose whether to export the label or id: when you export a file you will see a case of your properties with the id in another with the label. This feature allows you to have more readable files if the ids are not clear.
  2. Choose the delimiter: you can choose whether to export a file with delimiter la, or il; . This feature allows those who use excel to have an immediate conversion from .csv to excel