Parameter:
NSF_DocumentLockingEnabledShort description: Global switch for document locking at the NSF level – in addition to the DB property Allow document locking.
Profile
Parameter | NSF_DocumentLockingEnabled |
Category | Performance / Memory |
Component | Server |
Available since | 9.0.1 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | notes.ini only (counterpart: DB property Allow document locking) |
Possible values | 0 = off (default), 1 = enabled |
Description
Document locking allows a document to be explicitly locked while it is being edited – other users see the document as “locked by user X”. This avoids editing conflicts (replication / save conflicts), for example in heavily used workflow databases.
NSF_DocumentLockingEnabled=1 enables the feature server-wide. In addition, the DB property Allow document locking must be enabled per database.Example configuration
NSF_DocumentLockingEnabled=1
Notes & pitfalls
- The notes.ini activation alone does nothing – the DB property must also be set.
- Internally uses the domain's Master Lock server (see domain configuration).
- In cluster environments, check lock replication.
- With many short-lived locks, monitor the performance impact.
- The change takes effect after a server restart.