Skip to content

3.0.2

Key updates September 2026

CXBOX (Demo)

Added: Authorization - "Sign in again" popup

When the session has expired (401) or the user has no roles (403), the user now sees a clear popup with the buttons Sign in again and Sign out. If the identity provider (OIDC/Keycloak) still has the user's session, signing in again does not ask for a password and returns the user to the same screen.

Session has expired

A popup is shown, every widget stays as it was.
CXBOX-1384_401_after.png

Widgets were left empty and nothing explained what happened.
CXBOX-1384_401_before.png

The user has no roles

The popup names the reason.
CXBOX-1384_403_after.png

An empty "Error" popup without any text.
CXBOX-1384_403_before.png

A user without roles signs in

The popup is shown on the start page: Sign out lets the user sign in as someone else.
CXBOX-1384_login_without_roles_after.png

The application stayed on the loading spinner forever.
CXBOX-1384_login_without_roles_before.png

Info

See the Keycloak authorization documentation: the behavior of the buttons, the settings (AUTH_ERROR_MODE and others) and how to bring the changes to an existing project.

Fixed: Authorization - session lost in several tabs

Before - identity providers with refresh token rotation (Keycloak Revoke Refresh Token, Auth0, Okta and others) allow to renew the session with a token only once. If the application was open in several tabs, or the user pressed F5 at the moment of renewal, the same token was sent twice. The provider took it for theft and closed the session: the user saw 401 errors and empty widgets, and only clearing the browser cache helped.

After - the application sends each token once for all tabs of the browser, also after F5. If a renewal failed, the session is continued through the identity provider without a password; in the worst case the user sees the new Sign in again popup.

Info

See Keycloak authorization - token renewal: how it works, what the user sees in each case, the recommended settings of the identity provider. Return to the old behavior with the constant USER_MANAGER = original.

Fixed: Authorization - returned roles stay inactive

Before - when a user lost all roles in the identity provider, the roles were deactivated in the application. When the roles were returned in the identity provider, they stayed inactive, and the user could not work.

After - returned roles are activated again at the next login.

Added: Mass signing and encryption

Mass signing and encrypting is a mass operation that signs and encrypts the files of all selected rows with CryptoPro in one go. All types of Signing and encrypting are available: signing, encrypting, signing and encrypting, encrypting and signing. The user sees the progress of the rows (done / total) and can stop the processing.

This function is available for widgets:

  • List
  • GroupingHierarchy

Info

See the Mass operations - signing and encrypting documentation.

Added: CryptoPro - large files and clear errors

Signing and encryption with CryptoPro now work with large files, both in the signing popup and in mass operations.

Before - the whole file was given to the CryptoPro plugin at once. The plugin handles files of only 10-60 MB depending on the computer; on a larger file it could hang without an error, and the browser extension had to be restarted.

After:

  • a detached signature and encryption work with a file of any size: the file is processed in parts;
  • an attached signature (the file inside the signature) works up to 30 MB. A larger file is rejected at once with a clear message that shows the file size and the limit. The limit can be removed with the setting REACT_APP_CRYPTOPRO_ATTACHED_ASSEMBLY;
  • when the plugin fails, the user sees a short title, advice what to do and the details: PIN dialog cancelled, certificate expired, plugin not found or outdated, file too large and others;
  • a signature that the plugin returned empty is no longer shown as "signed".

Fixed: CryptoPro popup closes before signing ends

After - the user presses the button to sign or encrypt, the popup stays open and the button shows a spinner until CryptoPro has finished and the result is uploaded. The popup cannot be closed meanwhile, so the user cannot leave the form and lose the result.

Before - the popup closed at once, signing went on in the background without any sign of progress. With a long signing the user did not know if it was going on and could leave the form in the middle of it.

The search of the certificates in CryptoPro has also become faster.

CXBOX-1390-after-1-signing.png

CXBOX-1390-before-1-signing.png

Added: Error popup - "Copy details"

Every error popup now has a Copy details row. One click copies everything the support team needs to find the request in the server log: session id, screen and view, request, status, time of the request and the answer of the server. The arrow shows the same details right in the popup, so a screenshot is enough to start the investigation.

The details row is always visible.
CXBOX-1384_error_popup_after.png

The same error: an empty popup, nothing to copy or to show on a screenshot.
CXBOX-1384_error_popup_before.png

CXBOX-1384_system_error_after_details.png

Only the response body was available under "Details".
CXBOX-1384_system_error_before.png

Technical details: what is copied
  • Copy details copies the details as JSON: session id (the same value is written to the SIEM log as session: ...), current screen, view and browser URL, request method and URL, HTTP status, request start and finish time, response headers and body. The last lines say what the token renewal stands on in this browser (webLocks, indexedDb) and the three authorization constants it runs with.
  • The arrow expands the same details on screen: session id, start and finish time, error code and request. Opening the details copies them as well.

Example of the copied JSON:

{
  "sessionId": "3C1F67AF784230E3EB5DB594EA3B27EC",
  "clientId": 1789057000000,
  "login": "DEMO",
  "location": "http://localhost:3000/#/screen/meeting",
  "screen": "meeting",
  "view": "meetinglist",
  "statusCode": 403,
  "statusText": "Forbidden",
  "method": "GET",
  "url": "http://localhost:3000/api/v1/data/meeting/meetingStats?_page=1&_limit=5",
  "startedAt": "2026-09-10T18:26:00.410Z",
  "finishedAt": "2026-09-10T18:26:00.757Z",
  "responseHeaders": { "www-authenticate": "Bearer error=\"insufficient_scope\"" },
  "responseBody": null,
  "userAgent": "Mozilla/5.0 ...",
  "webLocks": true,
  "indexedDb": true,
  "userManager": "rotationSafe",
  "authErrorMode": "soft",
  "signInCallbackDetection": "oidcResponse"
}

Added: Dev panel - runtime errors

Warning

Not merged into main yet: cxbox-demo #731, needs the core from cxbox #148 (see Meta validation).

Before - when a widget was not shown on a view (for example, it has a type the core does not know), the developer saw an empty place and had to look for the reason in the server log and in the browser console.

After - the dev panel has a new indicator Runtime errors with the number of errors and warnings of the current view. A click opens the list of problems of the backend (meta validation) and of the frontend (errors of the browser), and in Debug mode the widget with a problem gets a colored frame.

CXBOX-1110-after.png

CXBOX-1110-before.png

Technical details: what the list shows and how to turn it on

The Runtime errors indicator is next to Refresh meta and Debug mode. It shows the number of errors (red) and warnings (yellow) of the current view. A click opens a list:

  • Backend - problems found by the meta validation of the core. Each problem shows the check, the widget or the view it belongs to, and the text, for example Type "MyCustomList" (bc "client") is unknown to FieldExtractor beans, fields are hidden. The name of the widget can be copied.
  • Failed validators - checks that failed themselves: their problems are unknown, see the server log.
  • Frontend - console.error and console.warn, uncaught errors and unhandled promise rejections of the browser. The same messages are counted, not repeated.

Only the problems of the current view are shown. Frontend messages are cleared when the user goes to another view and at logout.

In Debug mode the widget with a problem gets a red (error) or yellow (warning) frame, and the screen/view label of the debug panel is colored the same way when the view itself has problems.

Turn the dev panel and the meta validation on in application.yml (in cxbox-demo they are on by default):

cxbox:
  meta:
    dev-panel-enabled: ${DEV_PANEL_ENABLED:true}
    validation:
      enabled: ${META_VALIDATION_ENABLED:true}
      log-level: ${META_VALIDATION_LOG_LEVEL:error}

The results are given to the frontend in LoginServiceImpl:

.devPanelEnabled(metaConfigurationProperties.isDevPanelEnabled())
.metaValidation(metaHotReloadService.validateMeta())

Added: radio - vertical layout and row limit

The radio field is used to choose one of a few options, and in real projects these options are often long phrases. Before, a long value took as many rows as it needed, and one field could stretch a row of a list or a form to half of the screen.

Now you can set how the options are arranged and how much space each of them takes:

  • Display Mode - the options are in a row (horizontal, as before) or each option is on its own line (vertical).
  • Value height - the number of rows of each value, separately for view and edit mode. A cut value ends with ..., the full text is shown in a tooltip.

CXBOX-1422-form-horizontal.png

CXBOX-1422-form-vertical.png

The value takes one row.
CXBOX-1422-list-view.png

Each option takes up to 3 rows.
CXBOX-1422-list-edit.png

Fixed: Multi-upload - drop zone when adding is not allowed

After - when adding files is not allowed (for example, the task is closed), the "Add Files" button is hidden and the drag-and-drop zone is gray and does not accept files. While the screen is loading the zone is gray too and becomes active when it is known that adding is allowed.

Before - the button was hidden, but the zone stayed active: the user could drop a file and start an upload that is not allowed.

CXBOX-1218-after.png

CXBOX-1218-before.png

Info

See Multi-upload files - Availability. Nothing has to be configured: the zone follows the availability of its action.

Fixed: File upload - error reason for each file

Warning

Not merged into main yet: branch feat/CXBOX-1038, cxbox-code-samples feat/CXBOX-1038.

After - when a file is not uploaded, the tooltip of its line in the Upload progress window shows the reason received from the server. Each file of a multi-upload gets its own text. The same works for a single file of a fileUpload field.

Before - every failed file showed the same text, "Error. File not loaded and no new row created", and it was not possible to tell why the file was not uploaded.

CXBOX-1038-after.jpg

CXBOX-1038-before.jpg

Fixed: File download - one automatic retry

Before - sometimes downloading or opening a file ended with the error 502 Bad Gateway, although the file was in place, and the second attempt worked.

After - the application repeats the request once by itself, the user gets the file and does not see the error. If the second attempt fails too, the error is shown as before.

Fixed: FormPopup - no "jumping" on forceActive fields

After - the user changes a forceActive field in a FormPopup or in the confirmation of a mass operation with a form. The form stays on screen with the typed values, and a spinner is shown over it until the data is refreshed.

Before - after each change of such a field the whole form was replaced by a loading skeleton and drawn again. The popup "jumped", the user lost the place in the form and the focus.

Technical details: how it works

The behavior is the same as on List, Form and Info: while the meta of the row is refreshed after a change of a forceActive field, the form stays on screen and a spinner is shown over it. The loading skeleton is shown only when the popup opens and there is nothing to show yet. The same works in the confirmation of a mass operation with a form.

See also FormPopup.

Fixed: showCondition by forceActive - data at once

After - the user changes a forceActive field of the parent, a child widget hidden by a showCondition becomes visible and shows its records at once.

Before - the child widget appeared empty, and the records came only after the user pressed Save.

Fixed: hint filter - search by part of the value

After - when the user enters a part of the value in the filter of a hint field, the records that contain it are shown.

Before - only records with exactly the same value were found, so a partial value showed nothing.

CXBOX-1281-after.gif

CXBOX-1281-before.gif

Added: pickList, pickTree - number of selected records

When a filter chosen in the popup of a pickList or pickTree is applied, the "..." badge shows the number of selected records.

CXBOX-252-after.png

CXBOX-252-before.png

Added: dictionary, multipleSelect - list width

The drop-down list of a dictionary and a multipleSelect field now adapts to the longest value, and a very long value is shortened with "..." and shown in a tooltip.

CXBOX-150-dictionary-after.jpg

CXBOX-150-dictionary-before.jpg

CXBOX-150-multipleselect-after.jpg

CXBOX-150-multipleselect-before.jpg

Fixed: Full text search - empty search on clear

Before - when the user cleared the full text search field, the application searched by the text "null".

After - clearing the field removes the search, and the list shows all records again.

CXBOX-325-after.png

CXBOX-325-before.png

Fixed: Tooltips and calendar richText toolbar

  • Before - the tooltip with the full value of a text field shortened by text_maxDisplayed could be cut off by the borders of the widget. After - it is shown over the widget.

CXBOX-1358-list-after.png

CXBOX-1358-list-before.png

  • Before - in the inline form of CalendarList and CalendarYearList the drop-down lists of the richText toolbar (headings, text color) were cut off by the form, and the event popup could close. After - the lists are shown over the form.

CXBOX-1358-calendar-after.png

CXBOX-1358-calendar-before.png

Fixed: AdditionalInfo - full width when hidden

When all AdditionalInfo widgets on the right are hidden by a show condition, the other widgets of the view take the whole width.

CXBOX-318-withAI.png

CXBOX-318-withoutAI.png

Fixed: Notifications - "Close all" always visible

Before - the Close all button in the top right corner was visible even when there were no notifications.

After - the button is hidden until a notification appears.

Other Changes

see cxbox-demo changelog

CXBOX 5.0.3 (Core)

Added: Drilldown filter by hint

A drilldown from a hint field can now open the target view already filtered by the value of this field. The filter works by a part of the value and ignores case, the same way as the filter of the field and the input field.

Technical details: how to add

Use the new method fb.hint(...) in the filter builder of setDrilldownWithFilter:

fields.setDrilldownWithFilter(
        MyExampleDTO_.customFieldHint, DrillDownType.INNER, "/screen/MyExample/view/MyExamplelist/", fc ->
        fc.add(
                CxboxMyExampleController.myexample,
                MyExampleDTO.class,
                fb -> fb.hint(MyExampleDTO_.customFieldHint, fields.getCurrentValue(MyExampleDTO_.customFieldHint).orElse(null))
        )
);

See also DrillDown.

Added: Mass operations - row values and failed rows

For mass signing and encryption the frontend does a part of the work itself (CryptoPro signs or encrypts the files in the browser) and sends the result of each row to the backend. The core now accepts this result:

  • Values of a row - the backend receives the ids and names of the files created for each row.
  • Rows that failed on the frontend - if the browser could not process a row (for example, it could not sign the file), the user sees this row with the reason in the result of the mass operation. The project can also react to such rows, for example write a log.
Technical details: how to read the values and the errors
  • Values of a row. MassDTO has a new map options: the frontend sends with each row, for example, the ids and names of the signature and encrypted files. They are read with mass.getOption(...). The platform keys are in MassOptionType (SIGNATURE_FILE_ID, SIGNATURE_FILE_NAME, ENCRYPTED_FILE_ID, ENCRYPTED_FILE_NAME); a project can add its own keys with an enum that implements MassOptionTypeSpecifier.
  • Rows that failed on the frontend. If the browser could not process a row, the frontend sends it with success = false and the reason in errorMessage.
    • getMassIds_() now returns only the rows that the backend has to process.
    • The new getMassErrors_() returns the rows that failed on the frontend, so the project can react to them, for example write a log.
    • The core adds these rows to the result of the action with the message from the frontend, so the user sees them in the result of the mass operation. The handler does not have to do anything; to show another message, return your own MassDTO with the id of the row.
String signatureFileId = mass.getOption(MassOptionType.SIGNATURE_FILE_ID);

See Mass operations - signing and encrypting.

Added: Meta validation - unknown widgets

Warning

Not merged into main yet: cxbox #148.

Before - when a project added its own widget type and did not register a FieldExtractor for it, the widget was shown empty and nothing explained why.

After - the core checks the meta at startup and on every meta refresh, writes such widgets to the log and, when the dev panel is on, shows them in the dev panel. A project can add its own checks.

Technical details: how the check works
  • The check runs at startup and on every meta refresh, if it is turned on. Problems are written to the log; meta loading is not stopped.
  • The built-in check WidgetFieldExtractorValidator (title Widget type without FieldExtractor) reports every widget with a bc whose type no FieldExtractor supports. The log also gets a hint: change the type to a known one or register a FieldExtractor bean for the custom type.
  • When the dev panel is on, the results are also sent to the frontend at login: MetaHotReloadService.validateMeta() returns a list of MetaValidationResult (check, title, message, views, widgets, executionFailed), and LoggedUser has the new field metaValidation. The frontend shows them in the dev panel.
  • A project can add its own checks: a Spring bean that implements MetaValidator. A check that fails itself is written to the log as a warning and does not stop the other checks.
cxbox:
  meta:
    validation:
      enabled: true     # default false: the check is off
      log-level: ERROR  # default ERROR; OFF - do not write problems to the log

CXBOX documentation

Added: Chart widgets

We have provided descriptions of the widgets Pie1D, Column2D, Line2D, DualAxes2D and RelationGraph. Examples of the charts have been added to the Filtration, Sorting and Pagination articles.

Added: Calendar widgets

We have provided descriptions of the widgets CalendarList (events of a month, a week, a day) and CalendarYearList (events of a whole day: holidays, deadlines, reports).

Added: File widgets

We have provided descriptions of the widgets CardList, CardCarouselList and FilePreview. Examples of the cards have been added to the Filtration, Pagination, Default page limit and Multi-upload articles.

Added: DashboardList and collapse

We have provided descriptions of the DashboardList widget (deprecated) and of the collapse widget group: widgets of a view are combined into a group that can be collapsed and expanded.

Added: richText and hint fields

We have provided a description of the richText field (formatting, storage, content size) and extended the hint article with the color, readonly, filtering and drilldown sections. The Placeholder sections of all field articles say that the placeholder is shown for a read-only field as well.

Added: Drilldown tooltip

We have provided a description of the drilldown tooltip: hovering over a drilldown field shows the buttons Open link in new tab and Copy link address.

Added: Filtration - filter groups

The Filtration article describes the default filter group, the priority of the filters, deleting a personal filter group and how the personal filter group works with the full text search. The filter group sections have "How does it look" and "How to add" for every widget that supports them.

Added: Pagination - page limits

The Pagination article explains the difference between availableLimitsList (options in the dropdown) and PAGE_LIMIT (the default page limit).

Fixed: StatsBlock, List, HeaderWidget

The StatsBlock, List and HeaderWidget articles describe the show condition by parent entity and the properties of the title fields. The Title Color sections of the widget articles list pickList and inlinePickList among the applicable fields.