The name "UsersEDOC" may create the impression that new electronic document management features have appeared in the release. The confirmed changes indicate otherwise: in 3.0.74.2, a section of the access control mechanism affecting database updates has been corrected.
For accountants, this is not a new working scenario or a new form. The practical significance of the correction manifests during database updates with record-level security (RLS) restrictions.
What Happened
The built-in description of changes in 3.0.74.2 states that an auto-update error to 3.0.74.1 in databases with RLS has been fixed. The user significance of the confirmed change: a section of the access control mechanism affecting the update has been corrected.
No new features of electronic document management, interface changes, or new user actions have been announced.
In 3.0.74.1 and 3.0.74.2
| Question | 3.0.74.1 | 3.0.74.2 |
|---|---|---|
| Database update with RLS | An error could occur in certain databases during auto-update to 3.0.74.1 | The section of the access control mechanism affecting the update has been corrected |
| Working with electronic document management | No new features have been announced as part of the correction | No new features have been announced as part of the correction |
| Is the release necessary? | Depends on the outcome of the transition | After a successful transition from 3.0.73.1 to 3.0.74.1, release 3.0.74.2 is not required |
Who and What to Do
If the database with RLS could not update normally to 3.0.74.1, stop user activity and determine the state of the database. You cannot simply install 3.0.74.2 over a database in an unknown state. Follow the standard administrator procedure: if necessary, restore a backup and repeat the update to 3.0.74.2.
If the transition from 3.0.73.1 to 3.0.74.1 was successful, it is not necessary to update just for this correction.
What Will the Accountant Notice
There is no need to look for a new command, form, or setting. The correction relates to the update process. After the standard completion, the administrator checks the database launch and user access, and then allows work to continue. It is not permissible to work in a partially updated database.
There is no data on the complete disabling of RLS; the update correction cannot be interpreted as the removal of access restrictions.
Frequently Asked Questions
Have New EDO Features Appeared?
No confirmations of new features. The release description pertains to the update correction.
What Has Been Fixed for the User?
A section of the access control mechanism that could interfere with updating the database to 3.0.74.1 when using RLS.
Is It Necessary to Change the Order of Work?
No new order has been announced. Work cannot begin if the update has not completed normally.
What to Do After an Unsuccessful Update?
Stop users, determine the state of the database, if necessary, restore a backup and repeat the standard update to 3.0.74.2.
Does the Fix Mean Disabling RLS?
There are no grounds to believe so. The correction cannot be interpreted as a complete disabling of access restrictions.