I agree...
We have had the same difficulty.
In our situation we had a CMDB for which we needed rollback capability
for updating CI/Child records.
For each table field we built a transaction storage form that stored
all the Child Record transactions until the
Parent record was committed. Once t
As I understand it, Remedy doesn't provide a check on who is looking/editing
a record. The only check Remedy does is a last modified time check. We are
running into this same issue when multiple people edit the same record. We
plan to implement a read/read-write locking feature in our own system
Depending on the nature of the data, you could perhaps use the table field as
your temporary storage (I.e. Set field local action to place your various
values into the currently selected row in the table) and do a table walk to
send the table values back to the actual child entry's records when
3 matches
Mail list logo
