- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2026 06:40 AM - edited 02-10-2026 06:42 AM
hi,@Dr Atul G- LNG,
Thank you for clarifying the fundamental concept. Your point about not changing variables post-submission to maintain fulfillment efficiency makes perfect sense.
Based on your advice, I am now even more convinced that we should keep RITM variables as an "Immutable Audit Trail" (Request History) and use a separate "Generic Ledger Table" to store the "Current Active State" of the service/asset.
This way, we can respect the standard request process you mentioned, while still allowing the operational teams to maintain up-to-date data in the Ledger without touching the original RITM variables.
Thank you for helping me align our architecture with ServiceNow best practices!