Record locking in a system like this creates the risk that a user may open a record and then walk away from his machine without closing.  That means that another user may not have access to that job while it is locked.  Since the case where one user may inadvertantly overwrite the data saved by a previous user is not expected to occur very often, no record locking was established.  There are now some users who have so many schedulers that this is occurring more frequently.
To address this, we have implemented what is referred to as 'Optimistic Record Locking'.  It is optimistic in the sense that it is not expected to be required very often, but is there when needed.  In this case, the record is not actually locked, but an integer which is a column in the request table is incremented each time a save takes place.  When you open the record on your screen, you get that value.  If someone else opens the record and saves before you attempt to save, your number will no longer match and should then attempt to save, you will receive an alert (shown below) that the record has changed since you opened it.  You will need to reopen the record and make your changes again before saving.  In this way, you will see the changes that were made when you had the record open and you will not unknowingly overwrite them.