Revised cache key organization

To ensure a smooth transition to the 4.0 release, it’s crucial to clear the cache before upgrading to v4.0. Use the following endpoint and request body for cache clearing:

Ensure that this operation is carried out by a user with an admin role.

Endpoint:

POST {{baseUrlAdmin}}/api/internal/cache/clear

Body:
{
    "cacheNames": [
        "flowx:core:cache"
    ]
}

This endpoint is designed to purge Redis caches selectively. It will exclusively delete caches that are specified in the admin microservice properties under the property key: “application.redis.clearable-caches”.

Clear Cache 4.0

Access rights for Theme Management

To utilize the new theme management feature, make sure the following access rights are configured for the CMS microservice:

ModuleScopeRole default valueMicroservice
manage-themesimportROLE_THEMES_IMPORTContent Management
importROLE_THEMES_EDITContent Management
importROLE_THEMES_ADMINContent Management
manage-themesreadROLE_THEMES_READContent Management
readROLE_THEMES_EDITContent Management
readROLE_THEMES_ADMINContent Management
readROLE_THEMES_IMPORTContent Management
manage-themeseditROLE_THEMES_EDITContent Management
editROLE_THEMES_ADMINContent Management
manage-themesadminROLE_THEMES_ADMINContent Management

FlowX CMS access rights

Learn more

Logging

To streamline logging and enhance readability, you can now disable health endpoint calls cluttering the logs of various deployed FlowX microservices using the following environment variables:

  • LOGGING_LEVEL_WEB: INFO (default)
  • LOGGING_LEVEL_ORG_SPRINGFRAMEWORK_WEB: INFO (default)

If logs lack detail, consider setting the value to ‘DEBUG’.