Hello,
I have a question regarding the use of Item Source and its intended use case.
The Wiki currently presents this as a function to be used by ITOM/ITAM to allow for documenting the last audit. However, to actually use this seems unclear to me.
Is the intended use solely to act as a registry of audits performed on the item?
Such as :
| Source Reference | Source System | Last Audit Date | Modified By |
|---|---|---|---|
| Transaction ID 31234 | SCOM | 2024-12-31 | ZZ_SCOM_IMPORT |
| Transaction ID 41254 | SCOM | 2025-01-31 | ZZ_SCOM_IMPORT |
An alternative use case which I’m trying to verify the viability of is the use of “Item Source” as an alternative or extra ETM bonding. The reason for this is the ability to see the bonding from within the assyst application, and to use Last Audit Date as tracker for then the item was updated by an integration, and to be able to track this entirely seperate from the item modify date.
The Along the lines of something like this:
| Source Reference (External id (used as bonding)) | Source System | Last Audit Date | Modified By (Integration user performing the update to the item) |
|---|---|---|---|
| GUID: 5780ca50-4b3c-48cc-9c40-dd1a57e7f044 | ETM Document Library Gateway | 2025-01-31 | ZZ_ETM |
| SN: 20230715-001-123 | Workspace One MDM ETM Gateway | 2025-01-17 | [ZZ_ETM_CMDB-Gateway] ZZ_ETM |
However, I haven't seen any similar examples, and I’m wondering if this kind of use is outside the intended scope of the feature, and if such use is likely to cause issues down the line.
Thank you very much for your time.
Best regards,
Richard
