The simplest thing to do is... write your novel in notepad. When you're finished, open the SR paste it on the notes and save it. Badabing badaboom... in and out. If somebody beat you to it... you still got the notepad.
What you're asking is not simple because in computing... it's a physical law that only one process can access one data location at a time. The multitasking feature so overly advertised is achieved by shifting process through cpu's idle time. The effect is similar to how neon light appear to emits continuous light while actually it's strobing.
That's why in critical system, database works in a "all or nothing" mode. You can imagine if what happens to you happens to Bank's ATM machines.
I say simply dissallow people to edit SR that has been open somewhere else. They can view but editing should completely be lock by the system.
Uniti... you might want to consider solving this problem non-technically i.e. restructure your organization and process.
SysAid provide built-in mechanism to prevent simultaneous access to sr such as assigning admin, routing, escalating... and so on.
This is what I apply in my site. Even though it is possible to edit the field when an admin gets a pop up of this message he/she must leave that SR alone immediately cause it means somebody else is working on it. I don't like too many people working on the same problem either.
It is possible for group of admin to be forced to work on same sr, but only the assigned admin updates the SR. The colaboration is done through the messaging (read:e-mail) in that very sr.
But it's your call of course...
This message was edited 1 time. Last update was at Dec. 17, 2008 09:34 PM