Patch level update within release 3.0.74. The electronic document management subsystem (EDM) is affected by the evidence: changes are focused on the directory UsersEDM and related common modules of electronic interaction. Accounting contour objects (chart of accounts, VAT, electronic invoice (ESF)/SNT, pricing in tenge) have not changed in this diff.
Diff summary:
- Added objects: 0
- Removed objects: 0
- Changed objects: 9
- Unchanged: 25,278
- BSL changes with line-by-line evidence: 2
Note on the country (KZ, 2026): the current VAT rate of the RK is 16%, calculations in tenge (₸). Typical accounts of the RK: 1210 (short-term receivables from customers), 6010 (revenue from sales), 7010 (cost of sales), 1330 (goods), 3130 (VAT payable). These numbers are provided as a reference context for the configuration; this update does not affect them — there are no changes to accounting objects, rates, or entries in the diff.
1. What has changed
| Object | Type of change | Content according to evidence |
|---|---|---|
Catalogs.UsersEDM |
Changed (ManagerModule) | Access restriction text (RLS) removed in the manager module — see section 2 |
CommonModules.EDMServer |
Changed (Module) | Fragment describing read/change rights by organizations removed — see section 2 |
CommonModules.ElectronicInteractionWithServices |
Changed | Content according to evidence not disclosed (no line-by-line evidence) |
CommonModules.ElectronicInteractionWithServicesLabeling |
Changed | Content according to evidence not disclosed (no line-by-line evidence) |
CommonModules.ElectronicInteractionWithServicesEDM |
Changed | Content according to evidence not disclosed (no line-by-line evidence) |
CommonTemplates.SystemChangeDescription |
Changed | Service template for system change description (typical for each release); content according to evidence not disclosed |
ConfigDumpInfo.xml |
Changed | Service configuration dump file; content according to evidence not disclosed |
Configuration.xml |
Changed | Configuration metadata (including version); content according to evidence not disclosed |
Ext.ParentConfigurations.bin |
Changed | Service information about the parent configuration/supply; content according to evidence not disclosed |
In total, there are 9 objects. Line-by-line evidence is available for only two (see below); the other seven are listed as changed, but details of the changes are absent in the provided evidence — we do not speculate.
2. Changes in the code
There are two BSL corrections in total in the evidence, both are removals of access restriction text at the record level (RLS) related to the directory UsersEDM.
2.1. Catalogs.UsersEDM.ManagerModule — line 9 → 9
- Was:
Restriction.Text = "AllowReadChange |WHERE | ValueAllowed(Organization)"; - Now: empty (restriction text removed).
Previously, the manager module of the directory set a read/change restriction on records based on the condition ValueAllowed(Organization) — that is, access to records UsersEDM was filtered by organizations allowed to the user. In 3.0.74.2, this restriction text has been removed from the manager module.
2.2. CommonModules.EDMServer.Module — line 2103 → 2103
- Was:
|Directory.UsersEDM.Read.Organizations |Directory.UsersEDM.Change.Organizations - Now: empty (fragment removed).
A fragment declaring read/change rights by the dimension/restriction "Organizations" for the directory UsersEDM has been removed from the EDMServer module. The correction is consistent with 2.1: both relate to the same access restriction by organization for the directory UsersEDM.
Conclusion on the code: both proven corrections remove the RLS access restriction "by organization" from the directory UsersEDM. The specific requirement/scenario for this change (fixing access error, unifying RLS, etc.) is not specified in the evidence — we do not speculate; we only record the fact of the removal of the restriction.
3. Impact on modifications and extensions
What to check after the update:
- Extensions overriding
Catalogs.UsersEDM.ManagerModule. If the extension overrides/complements the manager module or relies on the previous restriction text by organization — compare with the new (empty) version. Changing the size/content of the module may lead to the extension not being applied (matching error) or the extension returning the removed restriction back. - Extensions and modifications of
CommonModules.EDMServer. Line 2103 and the surrounding block of rights restrictions forUsersEDMhave been changed. Check adaptations referring to this block. - Roles and RLS settings for EDM. Since the "by organization" restriction for
UsersEDMhas been removed at the metadata/module level, check the actual visibility of records in the directoryUsersEDMfor users with a limited set of organizations — access may have expanded. Ensure this aligns with your access control model. - Three modules
ElectronicInteractionWithServices*have been changed, but without line-by-line evidence. If you have extensions/integrations on top of these modules (exchange with the ESF information system, SNT, labeling, EDM services) — perform a complete configuration comparison after the update and run the exchange in testing. - Service objects (
Configuration.xml,ConfigDumpInfo.xml,Ext.ParentConfigurations.bin,SystemChangeDescription) — typical changes of the release; they usually do not require separate adaptation, but are involved in configuration merging.
Accounting modifications (entries for 1210/6010/7010/1330/3130, VAT calculation at 16%, generation of electronic invoices (ESF)/SNT, amounts in ₸) are not affected by this patch according to the evidence — regression on them is unlikely, but if you have your own modifications in EDM, test the export/signing of documents.
4. Update and verification procedure
- Backup of the information base before the update.
- Configuration comparison (current ↔ supply 3.0.74.2). Pay special attention to the 9 objects from section 1, primarily
UsersEDMandEDMServer. - Update the configuration to 3.0.74.2. If there are your own changes in the affected objects, allow merging manually, preserving modifications and considering the removal of the restriction (section 2).
- Check extensions: ensure that all extensions have been applied (no matching errors for
UsersEDM.ManagerModuleandEDMServer). - Check access: under a user with organization restrictions, open the directory
UsersEDM, assess the visibility of records — does it align with your policy after the removal of RLS. - Functional test of EDM: exchange with services (ESF through the ESF information system, SNT, labeling) — sending/receiving, signing.
- Control run of accounting (optional): conduct sales, check entries 1210/6010/1330/7010, VAT 3130 at a rate of 16% in ₸ — as insurance, although according to the evidence, accounting has not changed.
5. FAQ
Below are answers based strictly on the provided evidence.
