Commit record on timer

[sal88]

Hi all

 

I've just had this request come through. I'm quite sure this is something that is beyond the call of duty, but thought I'd check to see if anyone has any suggestions:

 

Often users modify a field but remain in that field, they do not commit the record by clicking the blank space on the layout. Obviously this means that that record is locked so no one else can modify it. The suggestion has been to have an automated timer commit script.

 

Off the top of my head this would probably not solve the problem if the record cannot be validated because of other fields that need to be populated (which would happen around half the time I'd say).

 

My instinctual position is that if there's one thing we're allowed to request from the end user it's that they don't loiter around in fields! 

 

 

Any thoughts welcome.


Thanks

[Kris M]

This is both a user training issue AND a development issue because any scripts that change data in batches needs to detect for record lock and perform its actions transactionally

[comment]

  On 2/19/2015 at 12:13 PM, sal88 said:

The suggestion has been to have an automated timer commit script.

 

Technically, it's possible. Whether it's advisable is a different question - and it cannot be answered without being familiar with your client's workflow.

 

 

A few point that you may consider:

 

1. You can disconnect idle users - there's a setting for that in Privileges;

 

2. Reverting the record might be more sensible than committing it - esp. if it is a new record;

 

3. Speaking of that, how likely is it that another user will complain about a new record (whose existence he/she is not aware of) being locked?

[sal88]

Thanks for the pointers guys! I'll experiment with the different solutions to see which works best (starting with user education).

 

Cheers