Version 3.0.74.2 was released not as another major functional release. It is a narrow fix for a specific situation: during automatic updates from 3.0.73.1 to 3.0.74.1, an error could occur in certain information databases where record-level access restrictions are used.
The main practical question here is not "what's new," but "is it necessary to install 3.0.74.2 on our database."
What Happened
The built-in description of 3.0.74.2 states that it fixes the automatic update error to version 3.0.74.1 in databases with record-level access restrictions. No other user changes have been established based on available confirmed data.
The correction of the update process should not be interpreted as disabling access restrictions, removing protection, or expanding user rights. There is no data on the complete disabling of record-level access restrictions.
Comparison of 3.0.74.1 and 3.0.74.2
| Situation | 3.0.74.1 | 3.0.74.2 |
|---|---|---|
| Release Purpose | Functional transition from 3.0.73.1 | Correction of the auto-update process |
| Databases with record-level access restrictions | An error could occur during auto-update in certain databases | The update process error has been fixed |
| Database already successfully updated to 3.0.74.1 | Works on the installed version | According to the built-in description, it is not necessary to install 3.0.74.2 just for this fix |
Who Should Use 3.0.74.2
The release is intended for scenarios where a database with record-level access restrictions is being updated from 3.0.73.1 and there is a risk of encountering the specified error, or if a previous attempt to update to 3.0.74.1 was unsuccessful.
If the database has already been successfully updated from 3.0.73.1 to 3.0.74.1, the built-in release description clearly states that updating to 3.0.74.2 is not required. This statement specifically pertains to the corrected auto-update error and is not a general recommendation regarding the organization's update policy.
What to Do If the Update Has Already Failed
Do not continue working in a partially updated information database and do not attempt to install the fix over a state that has not been verified by the administrator.
Safe sequence of actions:
- Stop user work with the problematic database.
- Record the error message and the stage at which the update stopped.
- Follow the standard recovery and update procedure adopted for this database.
- If necessary, restore the database from a backup.
- Repeat the update to 3.0.74.2 first on a copy of the database.
- Check the launch, user access, and main operational tasks.
- After successful verification, plan to update the working database.
What to Check After the Update
The check should be related not to invented menu items, but to the real conditions of your database:
- The database starts without update errors;
- Users log in with their usual accounts;
- Active access restrictions continue to be checked in the organization's working scenarios;
- Critical operations are performed on the test copy as expected.
Based on available data, no conclusions can be drawn about new features of the electronic document management system (EDMS), interface changes, legislation, rates, accounts, or documents. Separate evidence is needed for such claims.
Frequently Asked Questions
What does version 3.0.74.2 fix?
It fixes the automatic update error to 3.0.74.1 that could occur in certain databases with record-level access restrictions.
Is it necessary to update to 3.0.74.2 if 3.0.74.1 is already installed?
If the transition from 3.0.73.1 to 3.0.74.1 was successful, the built-in description states that updating to 3.0.74.2 solely for this fix is not required.
Does the fix mean that access restrictions are disabled?
No. The correction of the update process should not be interpreted as a complete disabling of restrictions or an expansion of user rights. There is no such data.
Can the update be restarted over the database after an error?
Without checking the state of the database — no. It is necessary to follow the standard administrator procedure, restore the backup if necessary, and repeat the update to 3.0.74.2 on a copy of the database.
Are there new features or legislative changes in 3.0.74.2?
Based on available confirmed data, no such changes have been established. The release is described as a narrow fix for the auto-update error.