#027 - Record locking concepts in Valence NAB apps

[Iwona]

SUMMARY: In this week's session we demonstrated how to set up a file maintenance app that uses back-end RPG toolkit procedures (vvUtility_lockRec and vvUtility_lock, vvUtility_unlock and vvUtility_isLocked) to ensure two users don't attempt to update the same record simultaneously.

URL: https://youtu.be/mqUZeDuSK_c

DD27.png

TIMESTAMPS AND FEATURES COVERED:

00:40 - Creating an application with a Form widget and record locking
01:30 - Creating a Form widget as a pop-up
01:50 - Record Locking of a customer information in a Form widget
02:25 - Creating app variable - Customer ID - Lock Customer
04:25 - File Editor - VVLOCKS
05:10 - Button Template Program - Lock Customer
07:00 - Valence API docs - Valence RPG Toolkit - vvUtility - method: lock
08:40 - Releasing Record Lock
11:00 - Attaching a Save Button behavior to the Customer Form
12:00 - Unlock Customer - test
13:00 - Lock customer - test
14:40 - lockCustomerB with details on who is locking the customer
16:40 - Creating a Lock that allows user to view the record but doesn't allow them to Save, disableSave
19:00 - disabling fields in NAB behaviors when disableSave is true
21:00 - Setting up a Program that will remove the lock upon closing o the application
23:00 - Locks stay active in case of machine shutdown without logging out e.g. by power loss