Full Changelog 4.0.0
Released 2026-05-06 · 45 issues · 2 fixes
The complete record: every commit in the release, grouped by type, including work that never reaches a customer-facing note. The external changelog is the readable summary of the same release.
Jira References
-
DEV-1007 - B: Provision Portal > Replace device page > Implementation
-
DEV-1089 - Provision Portal Java GUI > Clean DB > Try to log in > Log in not performed
-
DEV-1098 - Provision Portal Java GUI > Login screen > Incorrect version displayed
-
DEV-1171 - Provision Portal Java API > Oracle > High CPU usage
-
DEV-1198 - Provision Portal Java API > Oracle > REST / SOAP > POST/provision/from-xml-file-data > Invoke method > All statuses stored into "status" DB table
-
DEV-1204 - Provision Portal Java API > REST / SOAP > Provisioning > Logs are absent
-
DEV-1208 - Provision Portal Java API > REST / SOAP > POST/replace-cpe > Invoke method > Response with "4230" status code received
-
DEV-1332 - Provision Portal Java API > Swagger / Log file > Add build and version info
-
DEV-1426 - Provision Portal Java API > Oracle > Datа in "prov" DB > The "created" field contains an incorrect time
-
DEV-1432 - Provision Portal Java API > Oracle > REST / SOAP > Provision data with service or param from "params.xml" > POST/replace-cpe > Provision data erased
-
DEV-1440 - Provision Portal Java GUI > View log > Debug log > Open file > An error occurred
-
DEV-1466 - Provision Portal Java GUI > Single device > Provisioning parameters > All checkboxes deselected > Reprovision with "Null" value stored into "prov" DB table
-
DEV-1559 - Provision Portal Java API > REST / SOAP > POST/provision/from-request-data > User info > Deleteprevious = 1 > User info deleted from "Prov" DB
-
DEV-1561 - Provision Portal Java GUI > Single device > Add object with instance !=0 > Add object task created
-
DEV-1563 - Provision Portal Java API > REST / SOAP > POST/provision/from-request-data > "isFaultVisible" = "true" > Reprovision with 2460 status > Empty "Fault" tag is received
-
DEV-1571 - Provision Portal Java API > Oracle > REST / SOAP > POST/provision/from-request-data > Device offline > Invoke method > An error occurred
-
DEV-1574 - Provision Portal Java API > REST / SOAP > POST/provision/from-request-data > Provision data with object instance !=0 and sub-object > Provision procedure is not performed
-
DEV-1580 - Provision Portal Java GUI > Single device > Provisioning objects > Object with sub-object > Submit > "1790" status code received
-
DEV-1666 - Provision Portal Java API > REST / SOAP > POST/provision/from-request-data > Parameter with "" value > "" value sent to device
-
DEV-1678 - Provision Portal Java API > REST / SOAP > POST/provision/from-request-data > Invoke request > "#end DB" tag after "171" status in "DebugLog_DD.MM.YYYY.txt" file
-
DEV-1679 - Provision Portal Java API > SOAP > ProvisioningForDevice > Irellevant "fri:" namespace prefix is present
-
DEV-1689 - Provision Portal Java API > REST / SOAP > POST/provision/from-request-data > "isFaultVisible" = "true" > Add object on non-existing instance > 246 status > "Fault" tag with fault parameters received
-
DEV-1695 - Provision Portal Java API > REST / SOAP > POST/provision/from-request-data > Response more than 30 sec > An error occurred
-
DEV-1700 - Provision Portal Java API > REST / SOAP > POST /from-xml-file-data > Invoke request > Response received at the end of the provisioning procedure
-
DEV-1750 - Provision Portal Java API > Implement automatic deployment change log on doc portal
-
DEV-1761 - Provision Portal Java API > Functional changes
-
DEV-1762 - Provision Portal Java API > "isFaultVisible" = "true" > GetStatus > "Fault" tag is absent
-
DEV-177 - Grafana > Dashboards > API metrics > Provision-api > API methods breakdown by response time threshold over the last 24h > RemoveServices > Incorrect response time is present
-
DEV-1784 - Provision Portal Java API > Oracle > PROV DB table > Any device with serial in lowercase letters > Device serial stored in capital letters
-
DEV-1788 - Provision Portal Java API > Preprovision service with reboot = 1, reprovision = 1 > "1011 - new device arrive" event > Reboot task not generated
-
DEV-1789 - Provision Portal Java API > Preprovision object with instance !=0 > "1011 - new device arrive" event > Add object task generated
-
DEV-1813 - Provision Portal Java API > Oracle > "1011 - new device arrive" event > An error occurred
-
DEV-1818 - Provision Portal Java API > REST / SOAP > POST /from-xml-file-data > Incorrect file name > Invoke request > Incorrect response received
-
DEV-1819 - Provision Portal Java API > Oracle > POST/provision/get-provision-values > Invoke request > An error occurred
-
DEV-218 - Grafana > Dashboards > API metrics > API methods breakdown by response time threshold per model over the last 24h > Default value is shown instead of modelname
-
DEV-417 - Provision Portal Java API > SOAP > Load WSDL > Error loading WSDL
-
DEV-447 - Provision API > Datа in "prov" DB > The "created" field contains an incorrect time
-
DEV-455 - Provision Portal Java API > REST > POST/statuses > Invoke method > Irrelevant tags present in response
-
DEV-560 - B:Provision Portal > Login page > Implementation
-
DEV-599 - B:Provision Portal > Single page > Implementation
-
DEV-906 - B:Provision Portal > Get status page > Implementation
-
DEV-930 - B: Provision Portal > View log page > Implementation
-
DEV-932 - B: Provision Portal > User management page > Implementation
-
DEV-948 - B: Provision Portal >Multiple devices page > Implementation
-
DEV-994 - B: Provision Portal > Deactivate service page > Implementation
Bug Fixes
-
Use DB-specific ESCAPE literal for LIKE queries on Oracle
Oracle rejects
ESCAPE '\'with ORA-01425 (escape char must be a single character). Restore the DbType conditional from the C# original (VParameter.cs:144-151): single-backslash escape for Oracle, doubled for MySQL/MSSQL. Drop the unused findByNameLike method that had the same hardcoded escape. -
Hide null Name field in REST GetStatus fault response
Match C# original and SOAP behavior: omit "Name" from JSON when name_id is not resolved from cpe_parameter_name table.
Documentation
-
Update antora version to 4.0.0
-
Doc portal config update
-
Update antora version to 4.0.1 (dev)
-
Add changelog for release 4.0.0