Continued support for Extending Locks?
I wanted to carve out a new thread to elaborate on a point made here: Auth / Lock Timeouts
In v6.2, subsequent calls to LockManager.lock() would extend the lock time. This is ordinarily called by Obj-Refresh-And-Lock, but could be even called directly as part of the API (since it may not be necessary, from a business perspective, to re-open item from the database to extend the lock).
With the introduction of lockCache in v6.3+, lock extension is no longer supported. I wanted to get a better sense from Product Management whether this was an oversight or an intended change. (This is filed at SR-126496 - resolved with FDBK-10369 - which is invisible to me.)
I wanted to carve out a new thread to elaborate on a point made here: Auth / Lock Timeouts
In v6.2, subsequent calls to LockManager.lock() would extend the lock time. This is ordinarily called by Obj-Refresh-And-Lock, but could be even called directly as part of the API (since it may not be necessary, from a business perspective, to re-open item from the database to extend the lock).
With the introduction of lockCache in v6.3+, lock extension is no longer supported. I wanted to get a better sense from Product Management whether this was an oversight or an intended change. (This is filed at SR-126496 - resolved with FDBK-10369 - which is invisible to me.)
BNY Mellon
US
This might be the best approach here to extend locks - Ability to auto-save open forms?