How does Maximo Manage determine when a record has been updated by another user?

Question

Options

• ALooks for new entry in audit table.
• BCompares the rowstamp attribute on the existing record.
• CCompares the changeby attribute on the existing record.
• DCompares the changedate attribute on the existing record.

• A
  16% (8)
• B
  69% (34)
• C
  10% (5)
• D
  4% (2)

Explanation

Maximo Manage uses rowstamp - a system-generated, database-level timestamp or version counter - to detect concurrent edits. When you open a record, Maximo captures its rowstamp; before saving, it compares the stored rowstamp against the current one in the database. If another user saved the record in the meantime, the rowstamp will have changed, and Maximo rejects your save with an "updated by another user" error.

Why the distractors are wrong:

• A - Maximo doesn't query an audit table for concurrency checks; audit tables are for change history and reporting, not real-time conflict detection.
• C - changeby stores who last changed the record, not when, and can be duplicated across saves by the same user.
• D - changedate records the timestamp of the last change, but timestamps can have resolution issues (two saves within the same second look identical), making them unreliable for strict concurrency control.

Memory tip: Think "rowstamp = row's fingerprint." Every write changes the fingerprint, so Maximo can instantly tell if the row has been touched since you loaded it - no matter who did it or how fast it happened.

No community discussion yet for this question.